disable automatic network detection (and subsequent disabling ofinterface)

[B Walker]

Some of our customers have intermittent network related issues (mostly
due to power) and the problem is that if a hub drops for a bit Windows
does a lovely job of disabling the interface... which I don't want!.

Reason being we have local TCP/IP connections to the local machine, for
some odd reason WinXP refuses to honor the HOSTS file or LMHOSTS file (I
know I setup HOSTS as the first place to look) so anytime the local
machine connects to the <local computername> it resolves to the IP
address of the nic and refuses to resolve to 127.0.0.1 regardless of
proper entries in HOSTS.

I think that if I can turn off disabling of the interface (which of
course drops the IP address as in many cases we are forced to use DHCP),
my local connections should continue to be okay. Kinda a workaround
until we can force our local connections to use "localhost" which should
get rid of the problem entirely.

Any other suggestions? The main issue is connections from the local
machine to the local machine get hosed when the NIC is disabled.
Perhaps there's some other things I can go to get WinXP to actually use
the HOSTS file?

tia.

 

[Matt Hickman]

Some of our customers have intermittent network related issues (mostly
due to power) and the problem is that if a hub drops for a bit Windows
does a lovely job of disabling the interface... which I don't want!.

A UPS would do wonders

Reason being we have local TCP/IP connections to the local machine, for
some odd reason WinXP refuses to honor the HOSTS file or LMHOSTS file (I
know I setup HOSTS as the first place to look)

What does hour hosts file look like? Where is it located and
is it named HOSTS (with no extension)?


--
Matt Hickman
... the day I let politics interfere with my appreciation of beauty,
that day I retire of politics. (Prof)
Robert A. Heinlein (1907 - 1988)
_The Moon Is a Harsh Mistress_ c 1966