hi Jeff,
i'm having the same problem, i've followed your instructions
and this is the error i'm getting when trying to open http://localhost

HTTP 403.9 - Access Forbidden: Too many users are connected
Internet Information Services

--------------------------------------------------------------------------------

Technical Information (for support personnel)


Background:
This error can occur if the Web server is busy and cannot process your request due to heavy traffic.


More information:
Microsoft Support

Howdy Mark,

Let's start with the basics:

When did this start happening?
Did it ever work?
What changed?

What kind of network configuration do you have? Details please :)

Can you ping:
localhost - what's the ip that comes back?
netbios - what's the ip
FQDN

How many web sites do you have?

Are you using host headers?

Let's start with this, and see where we end up.

Thank you,

Tony DeVere [MSFT]
Microsoft IIS
Newsgroup Support
tdevere@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.

Tony,
I responded to a couple of subthreads yesterday, but for=20
some reason it didn't get posted. Anyway, here's the=20
scoop...

Last time I used local IIS was a few months ago, so I'm=20
not exactly sure when this broke. I'm running VS.Net for=20
an ASP.Net project on this machine and it couldn't create=20
the project using localhost. That's when I found the=20
problem. I'm running a small network w/ Win2K domain,=20
DHCP, DNS, and WINS server on the same machine. All net=20
services seem to be running fine. I can ping all=20
machines using their NetBIOS names and DHCP addresses. =20
When I ping my localhost, NetBIOS name, or DHCP-assigned=20
address, I get replies with "Reply ::1: time <1ms". =20
Seems odd that the address gets returned that way. If I=20
ping 127.0.0.1, I get replies back with the full=20
address. I have a couple of web sites on this=20
workstation. I'm not using host headers.

Additionally, I have the following information from=20
WFetch when I try to browse localhost...

[quoted text, click to view]
started....
WWWConnect::Close("localhost","80")\n
closed source port: 1236\r\n
WWWConnect::Connect("localhost","80")\n
0x2749 (A request to send or receive data was disallowed=20
because the socket is not connected and (when sending on=20
a datagram socket using a sendto call)
no address was supplied.): connect()
IP =3D "127.0.0.1:80"\n
source port: 1239\r\n
REQUEST: **************\n
OPTIONS /default.htm HTTP/1.1\r\n
Host: localhost\r\n
Accept: */*\r\n
\r\n
RESPONSE: **************\n
HTTP/1.1 200 OK\r\n
Server: Microsoft-IIS/5.1\r\n
Date: Wed, 28 Jan 2004 16:37:04 GMT\r\n
MS-Author-Via: MS-FP/4.0,DAV\r\n
Content-Length: 0\r\n
Accept-Ranges: bytes\r\n
DASL: <DAV:sql>\r\n
DAV: 1, 2\r\n
Public: OPTIONS, TRACE, GET, HEAD, DELETE, PUT, POST,=20
COPY, MOVE, MKCOL, PROPFIND, PROPPATCH, LOCK, UNLOCK,=20
SEARCH\r\n
Allow: OPTIONS, TRACE, GET, HEAD, COPY, PROPFIND, SEARCH,=20
LOCK, UNLOCK\r\n
Cache-Control: private\r\n
\r\n
WWWConnect::Close("localhost","80")\n
closed source port: 1239\r\n
finished.
..
[quoted text, click to view]

Here's some oddities...
1) Note that after the socket error above, it seems to=20
find the site (IE just hangs). If I set the "socket=20
reuse" check box in WFetch, and try again, it finds the=20
site w/out the error.

2) When I browse localhost with IE, it finally returns=20
with page unavailable. If I then click on the "Detect=20
Network Settings" link, it finds the site after a short=20
pause. From that point on in the session, I can find the=20
site. However, if I quit from the session, I'm back to=20
square 1. This seems consistent with what WFetch is=20
returning.


Hope this HELP!s.

Mark
[quoted text, click to view]