On 04/03/2017 10:49 AM, Patrick O'Callaghan wrote:
I meant no specific configuration on W. The /etc/hosts file on D has existed for a long time with no alteration.
The /etc/hosts file on D won't help W resolve the name to an IP address.
C:\Users\poc>nslookup storage ... Name: storage Address: 192.168.1.65 C:\Users\poc>ping 192.168.1.65 Reply from 192.168.1.65: ... ... C:\Users\poc>ping storage Ping request could not find host storage. Please check the name and try again.
It's unclear from those snippets whether N actually replied to the ping requests. Did it?
I'm at a loss to explain how nslookup (which is DNS-only) is able to resolve the name "storage" but ping (which can use DNS and the hosts file) cannot. That's just bizarre.
I added storage to that file and rebooted W. No difference.
Does that mean that ping still can't resolve the name? Or just browsing for the share? If you still can't "ping storage" then the entry in the Windows hosts file may not be valid. Send that file, maybe.
(Just so we're clear, we're pursuing two different avenues to resolving this problem. Adding the name to the Windows hosts file should allow name resolution, and access through the NAT setup. Setting up bridged networking should allow direct access and broadcast name resolution.)
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
