SuperGumby
Thu Jul 10 08:32:45 PDT 2008
the bit about IIS is fine, should your request get as far as IIS, but it
doesn't, we are looking at a lower level than that, IP routing.
The requesting client does not ask IIS, it asks the OS for resolvable
mechanisms. Depending on OS (but we can probably disregard all but XP, Vista
or Server 2003) the order of name resolution isn't particularly involved,
but does need to be considered. 'Modern' OS's use DNS, and the DNS answer
they get is your public IP, your router then doesn't handle this 'loopback'
properly. The request never gets to IIS, hence your 'WebAdmin' login.
"Perry" <Perry@discussions.microsoft.com> wrote in message
news:3830500B-2551-40BB-B60C-166EA05967F7@microsoft.com...
> After I posted this I found some information you posted in another forum
> on
> this problem. I will look into creating a different zone in DNS. thx
>
> The part that does not make sense to me is that I created an entry in the
> IIS properties for the website identification which uses the internal IP
> and
> a different host header that would be resolvable only on the internal
> network.
>
> "SuperGumby [SBS MVP]" wrote:
>
>> it's probably the admin interface for your router. This happens due to
>> most
>> router's inability to process 'loopback' traffic, requests from inside
>> the
>> LAN to the WAN IP which you then expect to be forwarded to a server
>> inside
>> the WAN.
>>
>> It can be overcome by running what most refer incorrectly to as 'split
>> DNS',
>> creating the zone as an independent zone on your SBS and creating DNS
>> records which point to internal IPs.
>>
>> "Perry" <Perry@discussions.microsoft.com> wrote in message
>> news:EF6B4BFB-5543-4255-BD41-F7254BF99E46@microsoft.com...
>> > Running SBS 2003 SP2, IIS is setup with default website, plus one
>> > additional
>> > website that is available from the Internet. When trying to access
>> > this
>> > website internally, an authentication window pops up, saying the server
>> > xyz.com at WebAdmin requires a username and password. I am not able to
>> > get
>> > around this trying by supplying user/pw or domain/user/pw.
>> >
>> > I have added host header values in IIS for xyz and xyz.com on the
>> > internal
>> > IP address but it doesn't make a difference. The host header values
>> > setup
>> > for access externally work fine.
>> >
>> > What do I need to do to make this work?
>>
>>
>>