I have a Windows Server 2003 system on which passwordless access to local UNC paths is possible using the server's unqualified hostname or its IP address, but not via its FQDN -- even when the hosts file is used to map that FQDN directly to
\\myhost.mydomain.com\- brings up an authentication dialog
Unfortunately, I have a local application trying to resolve UNC paths including the host's FQDN.
I've tried resolving
127.0.0.1 in both
lmhosts, and calling
ping myhost.mydomain.com at the command prompt gives the appearance that this resolution has taken effect; even so, attempting to open
\\myhost.mydomain.com\ from Windows Explorer brings up a password prompt, while
\\127.0.0.1\ does not.
The system is using an OpenDirectory server (Apple's Kerberos+LDAP directory service) for authentication.