Can't view network computers or printer to network printers

F

FirstT

Member
Joined
Sep 3, 2021
Posts
7
I'm having problems seeing computers on the network and printing to shared network printers. I can access the shared folders if I manually enter their location, but still can't install or use the printers. This seemed to happen overnight as they were working yesterday. I'm running windows 10 Pro.
 
I recently had an issue with a Win10 security update blocking shared printing from WIN7 to WIN10.
The culprit was KB5005565.
After removing that from the PC where the printer was being shared from, the issue was solved and printing resumed.
 
I uninstalled KB5005565 and that fixed the problem with not being able to print to the shared printer. I still can't see any networked PCs on the network unless I go directly to their address(i.e. \\NETWORK-PC). I've tried resetting network setting, firewall, checked subnets, workgroups and sharing settings. Everything is still set like it should be but I can't browse the networked PCs, but they can my PC on the network.
 
FirstT said:
I uninstalled KB5005565 and that fixed the problem with not being able to print to the shared printer. I still can't see any networked PCs on the network unless I go directly to their address(i.e. \\NETWORK-PC). I've tried resetting network setting, firewall, checked subnets, workgroups and sharing settings. Everything is still set like it should be but I can't browse the networked PCs, but they can my PC on the network.
Click to expand...
Good to know one of the problems got solved.

The second part, I've had the same issue with several clients and I have yet to find a fix, sry.

Best of luck.
 
You can also check if the feature SMB1.0 on the WIN10 PCs is active..

I remember reading awhile back that turning that ON fixed that issue for some users, sadly it did not work for me..
 
If the above "fixes your issue" SMB 1.0 is not secure and only should only be used as a temporary fix. Stop using SMB1 @Corrine can confirm the security issues surrounding SMB 1.0 as she is trained in Microsoft Security.

Make sure you have "all" the latest MS updates. I had read that MS has fixed some printer issues as long as you are completely up to date.
 
xrobwx71 said:
Make sure you have "all" the latest MS updates. I had read that MS has fixed some printer issues as long as you are completely up to date.
Click to expand...

Amen to that. One of the former regulars here, and elsewhere, who was a BSOD wizard, John Carrona, put it best:

There really isn't a point to checking for updates and not installing them. . . It's important to install all available updates. I've been doing this since the days of DOS, and I still don't have the confidence to pick and choose among updates. There are just too many variables involved - and most people can't evaluate the full consequences of installing/not installing updates.

I have seen so much more heartache (and devastation, in the form of systems that eventually implode) caused from keeping updates from applying than I ever have from the occasional problematic update. And the latter often gets a patch fix pretty promptly or official instructions to roll it back until a patch or replacement is made.
 
xrobwx71 said:
[re: variables] One of my favorite words in the English language.
Click to expand...

I can't say it's a favorite word, but it's certainly a concept I cherish and embrace.

Even if the following from Donald Rumsfeld was being used, illegitimately, to brush away responsibility for something he had a central role in, the actual concept itself is absolutely valid:

"As we know, there are known knowns. There are things we know we know. We also know there are known unknowns. That is to say, we know there are some things we do not know. But there are also unknown unknowns — the ones we don't know we don't know."

And, it's usually either the selectively ignored "known knowns" or the "unknown unknowns," which cannot be planned for, that really come back to proverbially bite us in the tush in the worst possible ways. There seems to be more consistent contingency planning for "known unknowns." (But, let me be clear, you can get bitten in the tush by any of the above if you do zero planning.)

And when it comes to OS maintenance, for your average user or even your average tech, there are way more "unknown unknowns" for us than there are for the people who developed, and are tasked with maintaining, any given OS. Just as it would be foolish to tell your doctor that his advice is foolish, and you'll listen to social media instead, it's equally foolish to believe you know more about what does, and does not, need doing as far as the "care and feeding" of any OS than the people who make it do.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top