Hello David,
Here's what I know:
When the client makes a request, the name must be resolved by DNS. The IP
has been found, the job of TCP is at work to estiblish a connection. This
is working of course...
After TCP is estiblished, then we can lay out HTTP. IIS receives the HTTP
traffic and passess it through the ISAPI filters list. After each filter
has it's turn with the data then we pass off the request to the correct web
site. (Checking the web sites IP's and host headers etc...)
We will log what the result of that request was in the IIS log files for
that web site. There you will see, if you received a 200 -OK or 302- Object
moved redirect.. or some other message.
What must be happening, is somehow, someway, the resoultion of the name/ip
is being sent as an external request and DNS is picking it up. There are
ways to determine if this is happening... (have we made sure the lmhost
file isn't at fault here?) What happens if we ping thd local netbios name?
It sounds like a network config issue... All this can be proved as I've
stated, with a network trace.
Please consider posting this message in the windows server product group as
well for their input...
(all information in this post is a very high overview of what happens, but
was intended only to provided a picture of the internal operations of IIS)
Thank you,
Tony DeVere [MSFT]
Microsoft IIS
Newsgroup Support
tdevere.TakeThisOut@online.microsoft.com
"Please do not send email directly to this alias. This is our online
account name for newsgroup participation only."
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2001 Microsoft Corporation. All rights
reserved.
>> Stay informed about: URL Switches to fqdn