quote:

---

>
> Is the web domain listed in the Intranet zone on the browser's
> security tab? Are you using a proxy server, and/or have you done
> this:
>
> Control Panel -> Internet Options -> Connections -> LAN Settings ->
> Uncheck everything.
>
> Jeff

---

quote:

---

> If you install NetMon on a third machine unrelated to the server and client
> (i.e. not disturb the network timing between the two machines) and monitor
> their does the issue reproduce itself? This is how you want to capture the
> issue without disturbing the timing on the server/client (i.e. a third-party
> observer running NetMon should be able to take a trace of the entire thing).

---

quote:

---

> I'm not certain how the AD Server can respond faster than TCP would allow
> since its response is transported by TCP...

---

quote:

---

> Now, is the "Server not found" message the the actual error response
> returned when IE's "Show Friendly HTTP Error" is turned off (i.e. what does
> IIS ACTUALLY return for the request which you claim arrived and is served by
> IIS?). This error response contains useful information (or you can look at
> the web log file to give the HTTP Status code and Win32 error code for the
> request that returns "Server not found")

---

quote:

---

>
> If it is some sort of connection-level error, you would also find evidence
> in %SYSTEMROOT%\System32\LogFiles\HTTPERR\*
.log for that request.
>
> Please give the IIS and HTTPERR log file lines around the request that
> returns "Server not found" as well as NetMon trace.

---

quote:

---

>
> Also, since this is NTLM-related -- can you give the authentication settings
> of all the apps on the website visited by the IE browser (is it uniformly
> NTLM or contains other authentication types as well) as well as when the
> user clicks the link, is it making a POST or a GET request (i.e. is this
> posting a form?)

---

quote:

---

>
> --
> //David
> IIS
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Grizmister" <grimes73a@yahoo.com> wrote in message
> news:48db783b.0312311514.1f07433f@posting.google.com...
> This one may be for the microsoft internal development staff.
>
> PROBLEM DESCRIPTION
> This problem first manifested itself in our Windows 2000 / IIS 5.0
> environment. When an IE 6.0 user clicks on a link to display an ASP
> web page on an IIS server they _immediately_ get a "Server not found
> or DNS error" response in the browser. However, if they F5 (refresh)
> 3,4,5,6, or more times the ASP generated page eventually displays.
>
> RESEARCH TO DATE
> We traced the problem to some kind of a network timing issue with
> Windows Integrated Authentication enabled in IIS for the particular
> site. However when we enabled the NetMon packet driver to collect
> TCP/IP packets in trying to zero in on the exact problem, the problem
> became much much harder to reproduce. (The app worked as expected.)
> As soon as we disabled the NetMon driver, the problem returned. This
> behavior supports our theory that the problem was a network timing
> issue in the TCP/IP subsystem.
>
> Before we found the root of the problem, SP4 came out for Windows 2000
> Server and the problem went away. I cannot find anything in the list
> of documented fixes that points to the problem we were experiencing.
>
> However, now we are experiencing the exact same senario on our Windows
> 2003 IIS 6.0 Servers. One running SharePoint. One running a third
> party app. Both requiring Windows Integrated Authentication.
>
> No recored errors or warnings are recorded in the event logs.
> I have verified in the IIS Logs that the server received the page
> request even when the browser displays "Server not found". So we know
> the request is getting to the IIS server.
>
> ENVIRONMENT
> The servers are connected 100 Mbit Full-Duplex Switched Ethernet to a
> 1 GB backplane. The only thing I can figure from looking at the
> NetMon packets collected is that IIS is sending a request to the
> ActiveDirectory server to verify authentication and the AD server is
> responding faster than the TCP/IP sub-system is able to accept the
> result and pass it back up to IIS as valid.
>
> 2 AD Servers are Win 2000 w/ SP4
> Windows 2000 / IIS 5.0 Servers running SP4 work fine
> Windows 2000 / IIS 5.0 Servers running SP3 reproduce the error
> Windows 2003 / IIS 6.0 Servers reproduce the error
> All systems are on the same 10.x.x.x subnet.
>
> REQUEST
> I've searched msdn, technet, and usenet for hours looking for a
> similar documented experience or a fix. Nothing.
>
> Is there anyone who can provide some additional insight that yes this
> is a known problem and/or where I can go to get a fix for Win2003?

---