Windows Forum

Ask something
Discussion Locked

2000 server identity crisis

0 helpful
4 replies

by why

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

(Repost from NT)

I have a 2000 server not a DC, in a simple, single 2000 domain.

netstat -a manages to resolve the TCP listener address 0.0.0.0:0 to a hostname that is not on our network, and is not accessible from it (though it might have been when the server was installed - don't know)

netstat -an looks normal.

Other 2000 servers in the same network show their own name in netstat -a as one would expect.

Any bright ideas - I suspect this has caused havoc with various applications getting confused about whether a socket is local or remote.

4 replies

by aaron h.

Netstat gets the name that it lists in the netstat ?a command from the registry. Look in the registry at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

And look at the Hostname value. This value should be the name of your machine. If you modify the value and run netstat ?a again you will see an immediate change. I am not sure if this is what you are describing but it was interesting to look into. Please let us know if this works. (note: I did this on XP Pro. It ought to be the same for win2k)

by why

Something wrong here ... answer wasn'r unacceptable, but didn't solve the problem.

Anyway hostname in registry was correct.
Search of registry (and whole root drive) didn't find spurious machine name in ascii form.

Haven't done hex search, and then there's hidden keys ...

However, dropping the machine our of the domain gave the same result - and after rejoining still the same.

Any more help gratefully received.

by why

Well, I solved it myself in the end.

Server was running MS Firewall Client (no don't ask - I want to find the guy who set it up first ...)

Disable it and all is hunky dory.

The hostname that netstat managed to find was the ISA server that our local ISA server uses as proxy, thus no direct connection from the machine in question. Suspect this might just be a bug.

Also suspect that Firewall client might just be the reason for the rest of the havoc ...

This discussion is closed to new replies.