1

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 127.0.0.1.

That is:

  • \\127.0.0.1\ - passwordless
  • \\myhost\ - passwordless
  • \\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 myhost.mydomain.com to 127.0.0.1 in both hosts and 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.

Charles Duffy
  • 946
  • 2
  • 10
  • 19

2 Answers2

2

KB#926642 describes a solution to this, which worked for me:

Add a multi-string value to the registry under the name HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0\BackConnectionHostNames including the hostname(s) or alias(es) which aren't working.

Charles Duffy
  • 946
  • 2
  • 10
  • 19
1

Try putting myhost.mydomain.com in the IE Trusted Sites (or mydomain.com).

You may also need to ensure that IE Trusted Sites is configured to use automatic logon with current user name and password.

Greg Askew
  • 35,880
  • 5
  • 54
  • 82