G
Gern Blanston
Greetings all,
I've got a freshly installed Win2K Pro system with all
current patches installed with an interesting problem (and
by interesting I mean annoying).
When I configure it to run using a static IP address
everything works perfectly. It boots up nice and quick
and has no trouble talking to the server.
If I switch to DHCP the start up takes about two extra
minutes, and despite sensing the network, I never get an
IP address. When I tried using IPCONFIG / RENEW to force
a reconnect I get an error telling me to disconnect the
network card or restart the computer.
I've pulled the network card and replaced it with another
one and reinstalled the NIC drivers, all to no effect, but
switching back to a static address eliminates the problem
at once.
I checked the system logs and found no errors. In the
application log there was a warning ("WMI ADAP was unable
to process the PerfDisk performance library due to a time
violation in the open function"), but it appears when
using a statis address as well.
Of course the location where this PC is going to be
installed is on one of our DHCP segements, so sticking
with the static address isn't an option (plus I don't like
the idea of putting it in service with a known problem).
Does anyone have any suggestions on this? Is there a way
to completely re-install the DHCP service, or should I
just FDISK and Format?
Thanks
I've got a freshly installed Win2K Pro system with all
current patches installed with an interesting problem (and
by interesting I mean annoying).
When I configure it to run using a static IP address
everything works perfectly. It boots up nice and quick
and has no trouble talking to the server.
If I switch to DHCP the start up takes about two extra
minutes, and despite sensing the network, I never get an
IP address. When I tried using IPCONFIG / RENEW to force
a reconnect I get an error telling me to disconnect the
network card or restart the computer.
I've pulled the network card and replaced it with another
one and reinstalled the NIC drivers, all to no effect, but
switching back to a static address eliminates the problem
at once.
I checked the system logs and found no errors. In the
application log there was a warning ("WMI ADAP was unable
to process the PerfDisk performance library due to a time
violation in the open function"), but it appears when
using a statis address as well.
Of course the location where this PC is going to be
installed is on one of our DHCP segements, so sticking
with the static address isn't an option (plus I don't like
the idea of putting it in service with a known problem).
Does anyone have any suggestions on this? Is there a way
to completely re-install the DHCP service, or should I
just FDISK and Format?
Thanks