Windows client doesn't map network drives

[a4wanman]

Running Windows 10 version 1703. Servers are Windows 2016. On a certain VLAN, the drive mappings (via GPO) are not loading. Our laptop docking stations are on their own VLAN (ie VLAN 15). While docked, the laptop will not load the drive mappings. If I disconnect from the docking station and log into AD with the wireless connection (different VLAN, VLAN 400), the drive mappings load.

 

I can also connect the laptop directly to a switch port (yet a different VLAN, VLAN 100) and the drive mappings load.

 

The issue seems to be on that one particular VLAN 15. For testing, I also tried at a command prompt using: net use t: \\{server name}\{share name}. Get "network path not found". Also tried: net use t: \\{IP of server}\{share name}. This also fails.

 

Almost seems the workstation can not find the Share Name. I've tried a Windows 8.1 laptop just to see if it's related to Windows 10. Same issue with Win8.1.

 

 

Any suggestions?

 

Thanks

[Liam]

Can you ping the file server host? Sounds like a routing issue! Any acl’s?

[a4wanman]

Yes. I can ping the server by IP address and name. Doesn't appear to be a routing/DNS issue. Using same DNS servers on all subnets.

[Liam]

Hm, not something to do with conflicting drive letters? What does rsop say?

[a4wanman]

Sorry for the delayed response. Issue was due to Symantec Endpoint Protection 14 blocking the VLAN. VLAN is currently using a 172.15.x.x address. Was not having any issues until installing the Symantec EP. I've uninstalled and the laptops can now map a drive while connected to the VLAN 15. I guess Symantec EP was blocking due to being a public IP range. The real fix would be to reconfigure the ip subnet for the VLAN to be in the private ip range.

 

Thanks for the help.