T-cko
asked on
Windows 2008 - Network Path Not Found when using hostname
Hello,
I have two virtual (VMware) machines - both Windows 2008 (both have the same DNS, NetBIOS settings)
Machine A and Machine B are both accessing the same remote share, but the problem is, that one of those Windows 2008 servers is unable to map a network share by hostname on remote server, despite DNS resolution working correctly.
Let's say the target server is XY10.domain.net
Pinging this full name returns 100.100.100.100 correctly (the IP is only an example).
Tracert and all network traffic is flowing correctly.
However, when trying to map a specific share by using hostname \\XY10.domain.net\share\ I get error "Network path not found".
Neither manual mapping through GUI nor net commands work (same error).
But when I use \\100.100.100.100\share , the share opens up correctly.
I already checked the NetBIOS on the network card, which is turned on.
I tried using workaround, by setting the
XY10.domain.net 100.100.100.100
in hosts file, but didn't work.
Meanwhile, the other server can successfully map the share with hostname, while the first one can only map with IP. There are no connection limits on the target share.
I have two virtual (VMware) machines - both Windows 2008 (both have the same DNS, NetBIOS settings)
Machine A and Machine B are both accessing the same remote share, but the problem is, that one of those Windows 2008 servers is unable to map a network share by hostname on remote server, despite DNS resolution working correctly.
Let's say the target server is XY10.domain.net
Pinging this full name returns 100.100.100.100 correctly (the IP is only an example).
Tracert and all network traffic is flowing correctly.
However, when trying to map a specific share by using hostname \\XY10.domain.net\share\ I get error "Network path not found".
Neither manual mapping through GUI nor net commands work (same error).
But when I use \\100.100.100.100\share , the share opens up correctly.
I already checked the NetBIOS on the network card, which is turned on.
I tried using workaround, by setting the
XY10.domain.net 100.100.100.100
in hosts file, but didn't work.
Meanwhile, the other server can successfully map the share with hostname, while the first one can only map with IP. There are no connection limits on the target share.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.