R
Rob Oaks
I am the sys admin at a company that has several IBM ThinkPad T30s
with a built-in Intel(R) PRO/100 VE NICs. I have one myself, and it
connects to the NT4 domain with no problem. However, another system
that I just setup (generated it from a Ghost image and then ran
NewSID--not that this is relevant) can't seem to pull an IP address
(i.e. ipconfig/renew does nothing) and always configures the auto
configuration IP address (169.254.x.x). If I configure a static IP,
everything works fine (so I really don't think it's a hardware
problem) but, of course, that's unacceptable.
At first I thought the problem was with the NIC driver as the errant
system has a newer driver than mine that was installed by the Windows
update website. However, when I uninstalled the new driver and
configured the old driver precisely like the NIC on my system, it
still didn't work. I also tried the following, suggested elsewhere:
1) Obtained the latest service pack for Windows
XP.
2) Used the Network Diagnostics tool to identify any failed settings.
It just indicated a bad DHCP address of 255.255.255.255 (I already
knew there was a DHCP problem)
3) Used netsh to reset TCP/IP configuration.
Now, my theory is that there is some XP pro registry setting that's
preventing the XP DHCP client from doing its thing correctly. Do I
need to disable the autoIPconfiguration stuff. Any ideas? I'm
desperate.
Rob Oaks
with a built-in Intel(R) PRO/100 VE NICs. I have one myself, and it
connects to the NT4 domain with no problem. However, another system
that I just setup (generated it from a Ghost image and then ran
NewSID--not that this is relevant) can't seem to pull an IP address
(i.e. ipconfig/renew does nothing) and always configures the auto
configuration IP address (169.254.x.x). If I configure a static IP,
everything works fine (so I really don't think it's a hardware
problem) but, of course, that's unacceptable.
At first I thought the problem was with the NIC driver as the errant
system has a newer driver than mine that was installed by the Windows
update website. However, when I uninstalled the new driver and
configured the old driver precisely like the NIC on my system, it
still didn't work. I also tried the following, suggested elsewhere:
1) Obtained the latest service pack for Windows
XP.
2) Used the Network Diagnostics tool to identify any failed settings.
It just indicated a bad DHCP address of 255.255.255.255 (I already
knew there was a DHCP problem)
3) Used netsh to reset TCP/IP configuration.
Now, my theory is that there is some XP pro registry setting that's
preventing the XP DHCP client from doing its thing correctly. Do I
need to disable the autoIPconfiguration stuff. Any ideas? I'm
desperate.
Rob Oaks