S
Stamstergios
Hello,
I seem to not be able to connect to any shares on my local network immediately after the 2004 update. I get "Windows cannot access \\192.168.1.100". The share in question is a samba share on an Ubuntu Server PC which I can access just fine through my laptop (which is not yet updated to the 2004 version) and my Android Phone. I have been troubleshooting for over 6 hours today using advice from the internet. I believe I have tried almost everything: regedit,gpedit, changing global settings in smb.conf file in linux, updating to the newest driver, smb1 client support, firewall, etc.
What i have so far:
Any help is much appreciated. It has been a rather frustrating experience. Never had any problems with Windows Updates before.
Continue reading...
I seem to not be able to connect to any shares on my local network immediately after the 2004 update. I get "Windows cannot access \\192.168.1.100". The share in question is a samba share on an Ubuntu Server PC which I can access just fine through my laptop (which is not yet updated to the 2004 version) and my Android Phone. I have been troubleshooting for over 6 hours today using advice from the internet. I believe I have tried almost everything: regedit,gpedit, changing global settings in smb.conf file in linux, updating to the newest driver, smb1 client support, firewall, etc.
What i have so far:
- I can ping the server using both the hostname and IPv4
- I have checked port 445 traffic on the server and I see nothing. (when i use my phone, i do see incoming traffic)
- I cannot even access a local share, i.e. \\localhost\<share name>
- I cannot turn Network Discovery On; it reverts back to OFF
- I cannot access any other Windows 10 PCs on my LAN
Any help is much appreciated. It has been a rather frustrating experience. Never had any problems with Windows Updates before.
Continue reading...