FQDN in UNCs resulting in Internet Zone . . .

Posted: 12-02-2003, 01:18 AM
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

FQDN in UNCs resulting in Internet Zone . . .


Reply With Quote

Responses to "FQDN in UNCs resulting in Internet Zone . . ."

Ken Wickes [MSFT]
Guest
Posts: n/a
 
Re: FQDN in UNCs resulting in Internet Zone . . .
Posted: 12-02-2003, 07:40 PM
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.

--

Ken Wickes [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.


"Toby Ovod-Everett" <tovod-everett@alascom.att.com> wrote in message
news:ace601c3b87a$a58bf680$a601280a@phx.gbl...
> 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

Reply With Quote
 
LinkBack Thread Tools Display Modes
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
KB929777 and resulting 0x8000FFF DaveG Windows Vista Performance & Maintenance 0 03-30-2007 11:24 PM
FQDN UNC and Internet Explorer FreRange Windows XP Accessibility 0 05-26-2005 10:12 PM
UNCs in batch files Windows XP Basics 2 11-10-2003 10:59 AM
Zone Alarm - Internet Access for backWeb William Sanders Windows XP Security & Administration 1 08-29-2003 08:37 PM
Home Page problems resulting from 2C.lop Derrick Fawsitt Windows XP 0 08-07-2003 07:43 AM