Strange: Server Explorer can't see localhost unless machine connected to internet

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

YeeCN - 23 Dec 2004 05:18 GMT

Hi,

I am having this strange behaviour with my Server Explorer. It can't connect
to localhost unless I am connected to the internet (via dialup connection or
LAN). It gives an error that says "server name could not be found". I track
it down to a socket error which i think is connected to resolving name in
DNS

I am using Windows 2003 server in stand-alone mode (i.e. no domain
controller, no DNS server).

Thanks.
Yee

Reply to this Message

Sylvain Lafontaine - 24 Dec 2004 04:29 GMT

Old bug (feature?) that came into life when the TCP/IP stack has been
"corrrected" some years ago. I don't remember how to solve it (because I'm
now using an external router which is always on) but I think that involves
using the Microsoft Loopback Adapter (but I'm not sure).

You can try 127.0.0.1 or the name of your machine instead of Localhost but I
don't remember if this will work. The only thing that I remember is going
out to buy a router and stop fighting (loosing time) with that problem.

S. L.

> Hi,
>
[quoted text clipped - 12 lines]
> Thanks.
> Yee

Reply to this Message

Rate this thread:

Strange: Server Explorer can't see localhost unless machine connected to internet

Free Magazines