15 replies
by saihib
by jaydev
by tchieng
by jaydev
by gutridgesj
by shanghai sam
by leizure. . .
by shanghai sam
Yes, DHCP is confiugred properly and we have scoped IP's out that are being used by HUBS and....
Thanks.
by rickh9
by jaydev
by rickh9
by shanghai sam
by gutridgesj
ok, well, here's the deal. Every PC with the problem has an IP address setting of that number somewhere. So, i say delete all the entries in the network settings except the network card and reboot. First, i would mark down what is there so you can put it back.
once the pc comes back up, add tcp/ip using dhcp and reboot. see if the problem still exists. if not, add client for MS and reboot.
the goal is to see what entry was doing it.
DUN has tcp/ip settings so that is a good place tolook.
if the problem comes back and you cannot see where it is, then check the registry for that number and find out if it is lingering around. if so, delete that registry entry.
next, why does that hub need an IP address in the first place? isay trash the ip address on the hub.
you said you did not want to do this, but i would power off the hub for a few seconds and then ping that address to see if it is still out there somewhere. maybe there is more to it than it seems.
i would also check to see if there are other DHCP servers on the network besides what you think there is. maybe a rogue dhcp server is out there and it is assigning that address. also, check the registry on all the dhcp servers for the ip address to see ifit is lingering around somewhere.
all this should keep you busy for a while.
by jaydev
by jaydev
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending