| David Wang [Msft] 2005-06-25, 8:47 pm |
| Your problem does not seem to be with IIS (after all, you ensured that W3SVC
service is running and listening on port 80 and no requests were even logged
as received by IIS).
Since the browser says "DNS error or server not found" and you know IIS is
running and listening on the port, it suggests the problem is with the
networking configuration between your browser an the web server.
The proxy server is a possibility. Also, ISP is known to block inbound port
80 access, which prevents home users from running a web server.
The key here is that you must know how your requests are being routed and
where the various filters/blockers are jumping in to block your request
along that route. Unfortunately, figuring this out is non-trivial since you
must understand networking to make sense of it all -- none of the blockers
would tell you any information because they don't want you to know. You have
to inference what is wrong -- know the network topology to understand what
SHOULD happen, and then see what actually happens -- and derive what is
causing the deviation in behavior.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Mike" <Mike@discussions.microsoft.com> wrote in message
news:732DA0EC-8823-4AF3-A995-B95B9A57CCB9@microsoft.com...
"Kristofer Gafvert [MVP]" wrote:
> Do you use a proxy server in Internet Explorer? If so, please make sure
> that you bypass it for local addresses.
Unfortunately, no Proxy is present. 
|