Cannot Connect to Mapped Drive

[Kanky]

Hi Guys,

I have been running Freenas 9.10-Stable for ages now without any issue. This morning when I arrived into the office 2 of the Win10 PC's cannot connect to the mapped drives?

When I view the network on one of the laptop, I can see 7 computers (including 'SERVER'). However the other 2 PC's cant. I hadnt changed any settings etc, so not sure why this is happening. I can still access the server through its 192.168.x.x address and view the shares. But I am at a loss at to why this would happen now?

Any ideas?

 

[anodos]

Hi Guys,

I have been running Freenas 9.10-Stable for ages now without any issue. This morning when I arrived into the office 2 of the Win10 PC's cannot connect to the mapped drives?

When I view the network on one of the laptop, I can see 7 computers (including 'SERVER'). However the other 2 PC's cant. I hadnt changed any settings etc, so not sure why this is happening. I can still access the server through its 192.168.x.x address and view the shares. But I am at a loss at to why this would happen now?

Any ideas?

I've noticed that there are a lot of intermittent problems with NetBIOS name resolution in Windows 10. Have you verified that network discovery is enabled? The simplest solution is to just map by IP-Address. Enter the "Map Network Drive" dialog and where it says "Folder", type "\\<ip address>\Share"

Alternatively, you may wish to configure DNS for your LAN.

 

[Kanky]

It has just happened with a 3rd PC and resolved within 30 minutes. A buddy of mine suggested the switch could be faulty?

Network discovery is turn on on all machines. When the problem does happen it loses other computers, not just the Server. Does this sound like a hardware issue rather than software?

 

[Mirfster]

It has just happened with a 3rd PC and resolved within 30 minutes. A buddy of mine suggested the switch could be faulty?

Network discovery is turn on on all machines. When the problem does happen it loses other computers, not just the Server. Does this sound like a hardware issue rather than software?

Wonder if there is a "Master Browser" election going on between the systems?

 

[anodos]

It has just happened with a 3rd PC and resolved within 30 minutes. A buddy of mine suggested the switch could be faulty?

Network discovery is turn on on all machines. When the problem does happen it loses other computers, not just the Server. Does this sound like a hardware issue rather than software?

Sounds like NetBIOS. It's almost certainly not your switch. You can also check to make sure that "Netbios over TCP" is enabled on your Windows 10 Clients:

1. Control Panel\Network and Internet\Network Connections
2. Right-Click on your network adapter and click on "Properties"
3. Double Click on "Internet Protocol Version 4"
4. Click on "Advanced..."
5. Click on the "WINS" tab
6. Select "Enable NetBios over TCP/IP"

You can spend some time googling "NetBIOS name resolution", "Samba", and "Windows 10". It's a fairly common problem. Lots of people doing the "monkey at the typewriter" thing and posting workarounds that are ugly, or don't work, or both. You can type "net view" on the windows 10 machine to see if it's in a "somewhat broken" state. I lean heavily toward just giving up on NetBIOS name resolution entirely (I actually disable it by GPO on my networks - burn it with fire). If you have properly functioning DNS you don't need it. Or you can use IP-addresses, which should be pretty reliable ;)