R
Royg1954
Problems :
1. After update to v2004, I no longer see computers on my private network that used to be visible in Windows Explorer under (NETWORK)
2. After update to 2004, I can no longer print to a shared printer - the computer that the printer is attached to is no longer sharing the printer.
3. After update to 2004, I can no longer access shared folders on any of my 4 machines...all the share settings are reset
Seems like every time I update Windows to a newer version, I loose visibility to seeing the other computers on my network. (Private network Netgear ORBI) I also loose connection to a computer that has a shared printer. All 4 machines are on Workgroup HOMEGROUP.
I have attempted the following fixes: (Update to v 2004 and attempted fixes Implemented on all 4 machines)
1. Network and sharing center - All previous setting have been reset to default by the update (annoying that these can't be saved and transferred to the update). I reset all machines to allow discovery and file sharing without passwords.
FIX=No
2. Services checked - Function Discovery provider Host and Resource Pubs - both set the Auto (Delayed) (Note : I also tested Auto with same result)
FIX=No
3. Optional Features - SMB1.0/CIFS File Sharing Support - All Checked
FIX=No
4. Disabled (temporary) Windows Defender firewall incoming and outgoing (private network profile)
FIX=No
5. Several online scripts to fix the issue.
FIX=No
6. Brute forced connection via \\IP address in Windows Explorer AND set my Network to fixed IP addresses for all computers....and I was able to connect, and the computers showed up under NETWORK (only until the next reboot), before reboot, I added the computers to Quick access, and I can access the shares (that I reset my sharing) and I can print to the shared printer, even though the computers do not show up under NETWORK.
FIX= ? (working for now)
Very frustrating, you would expect that MS would have a top level switch that would allow access inside a private network, without going through several lower level switches and scripts that supposedly fix them... (and nothing fixes the issue)
I would also suggest a method that these setting be stored and transferred when the next Windows update occurs!
Please get this right MS!
Continue reading...
1. After update to v2004, I no longer see computers on my private network that used to be visible in Windows Explorer under (NETWORK)
2. After update to 2004, I can no longer print to a shared printer - the computer that the printer is attached to is no longer sharing the printer.
3. After update to 2004, I can no longer access shared folders on any of my 4 machines...all the share settings are reset
Seems like every time I update Windows to a newer version, I loose visibility to seeing the other computers on my network. (Private network Netgear ORBI) I also loose connection to a computer that has a shared printer. All 4 machines are on Workgroup HOMEGROUP.
I have attempted the following fixes: (Update to v 2004 and attempted fixes Implemented on all 4 machines)
1. Network and sharing center - All previous setting have been reset to default by the update (annoying that these can't be saved and transferred to the update). I reset all machines to allow discovery and file sharing without passwords.
FIX=No
2. Services checked - Function Discovery provider Host and Resource Pubs - both set the Auto (Delayed) (Note : I also tested Auto with same result)
FIX=No
3. Optional Features - SMB1.0/CIFS File Sharing Support - All Checked
FIX=No
4. Disabled (temporary) Windows Defender firewall incoming and outgoing (private network profile)
FIX=No
5. Several online scripts to fix the issue.
FIX=No
6. Brute forced connection via \\IP address in Windows Explorer AND set my Network to fixed IP addresses for all computers....and I was able to connect, and the computers showed up under NETWORK (only until the next reboot), before reboot, I added the computers to Quick access, and I can access the shares (that I reset my sharing) and I can print to the shared printer, even though the computers do not show up under NETWORK.
FIX= ? (working for now)
Very frustrating, you would expect that MS would have a top level switch that would allow access inside a private network, without going through several lower level switches and scripts that supposedly fix them... (and nothing fixes the issue)
I would also suggest a method that these setting be stored and transferred when the next Windows update occurs!
Please get this right MS!
Continue reading...