Server non communications
I have a Dell Server running W 2008 R2.
It's on a LAN with 8 pcs running W7Pro and W10Pro.
If I go on ANY of the PCs and try to Map a Network Drive, I see only THREE (of the Eight PCs) but NOT the Server.
I can Ping the Server from any of the PCs and the Server responds (but wont connect).
It's obviously a setting on the Server but I don't know where to look.
Can anyone give me some pointers?
Thanks,
Biggles
It's on a LAN with 8 pcs running W7Pro and W10Pro.
If I go on ANY of the PCs and try to Map a Network Drive, I see only THREE (of the Eight PCs) but NOT the Server.
I can Ping the Server from any of the PCs and the Server responds (but wont connect).
It's obviously a setting on the Server but I don't know where to look.
Can anyone give me some pointers?
Thanks,
Biggles
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you put the server name (\\server) in file explorer on a workstation does it show up? But it doesn't show up automatically in Network.
Also do ipconfig /flushdns on a workstation where the server is not showing on the network.
try disabling the firewall on the server and check if you see it
ASKER
Thanks for your help. However if someone knows what is SMB v1 I would like to be educated. Does it run on Servers? Clients? or Both?
Just FYI, I don't know if it was the Computer Browser Service (Stopped the Restarted) or ipconfig /flushdns that did the trick.
I also did the same on the PC.
Also FYI doing the above did not immediately fix the problem. It took the whole night and I found the problem fixed in the morning.
I DID NOT reboot the Server but I DID reboot the PC after doing the above procedures.
If anyone has ideas, it would be interesting to learn new stuff.
QUESTION CLOSED
Just FYI, I don't know if it was the Computer Browser Service (Stopped the Restarted) or ipconfig /flushdns that did the trick.
I also did the same on the PC.
Also FYI doing the above did not immediately fix the problem. It took the whole night and I found the problem fixed in the morning.
I DID NOT reboot the Server but I DID reboot the PC after doing the above procedures.
If anyone has ideas, it would be interesting to learn new stuff.
QUESTION CLOSED
About SMBv1: https://en.wikipedia.org/wiki/Server_Message_Block
more about later versions: https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and (talks about the different versions and effects of disabling any of the versions)
Computer Browser Service (usually disabled on both servers and clients) - I dont think this had anything to do with it
ipconfig /flush - basically cleans out both good and bad DNS entries and refreshes them with info from a DNS server
more about later versions: https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and (talks about the different versions and effects of disabling any of the versions)
Computer Browser Service (usually disabled on both servers and clients) - I dont think this had anything to do with it
ipconfig /flush - basically cleans out both good and bad DNS entries and refreshes them with info from a DNS server
ASKER
Thanks guys. Question closed.
The server is out of support at this point