2000 server identity crisis

(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.