>So, you're trying to hit a site on IIS on your local machine. Is this a straight browser hit (i.e. HTTP/port80) or something else? If something else, can you connect over plain HTTP?
>

Yes, just plain HTTP over port 80.

>- I've never seen "Virtual Machine Network Services" before. Is this something that comes with VMWare or equivalent? Are you running multiple VMs with multiple OSs simultaneously, sharing the hardware?
>

Yes, I installed VM so I could run my web server demo in a real server OS.

>- I'd simplify as much as possible. Remove unneeded protocols, or at least bind protocols only to those adapters where you need them. e.g. do you actually need/use IPv6? Are they all SP2-compatible? Might they need updates?
>

That is pretty much the situation with the external card. It's not using most of the services I listed, just Client for MS Networks and TCP/IP.

>- I haven't used or encountered NetBEUI in years. You can pretty much use TCP/IP everywhere as long as you enable NetBIOS over TCP/IP.
>

No, that's not going to change. It's an extra layer of security in my office.

>- If you have multiple adapters in your machine, is it possible you have to tell IIS to listen on one or all of them?
>

Nope. I know of no way to do this. Plus, this configuration was working perfectly until fairly recently. What I would suspect is VM. Since my presentation is over, I've been thinking of uninstalling it. Maybe I'll do that sooner rather than later to see if that fixes this situation.

>
>Beyond that ... you'll need to speak with the maniac who set up your machine in the first place ;-) It's really hard trying to diagnose something like this remotely and asynchronously.
>

Oh, you want me to start talking to myself now? [bg] And who are you calling a maniac?!?

OK, it seems I've got to uninstall VM for the next step. I'll let you know if that fixes this problem. (But using localhost did work running under Server 2003 on this machine.)