FQDN in UNCs resulting in Internet Zone . . .

  • Thread starter Thread starter Toby Ovod-Everett
  • Start date Start date
T

Toby Ovod-Everett

I prefer to configure my users to use FQDNs for their
drive mappings instead of NetBIOS names - this ensures
that they will still be able to access their shares should
they roam somewhere that uses different WINS servers or
behind a firewall that blocks WINS. This has proved
reasonably successful under NT, but under XP I find that
this places the UNC in the Internet Zone. This results in
lots of security pop-ups as well as preventing some files
from being opened (i.e. Access databases).

http://servername.ourdomain.com/ correctly maps to the
Intranet Zone.
http://servername/ maps to the Intranet Zone.
\\servername\sharename maps to the Intranet Zone.
\\servername.ourdomain.com\sharename maps to the
_Internet_ Zone. Doh!

I can work around this by adding file://*.ourdomain.com to
the Intranet Zone sites list under Sites->Advanced. Any
thoughts as to why Microsoft might have configured things
this way? I spent some time searching through the KB and
couldn't find anything on this, but I might have
overlooked something.

Thoughts?

--Toby Ovod-Everett
 
Intranet vs Internet is just a guess anyway, so it's not going to be
perfect. Even DNS can't really help. For me, mymachine.microsoft.com is
intranet, but www.microsoft.com is internet.
 
Back
Top