Wrong IP, wrong Subnet, no DHCP

[YellowOnline]

Hello people,

I have a LAN with four computers on it, all connected with each other and to the internet through a DLINK router.
The LAN IP-adresses are 192.168.0.X,the subnetmask is good ol' 255.255.255.0 and gateway 192.168.0.1 (the router).
Everything is finy with the network itself, but yesterday I plugged another computer into the network and it doesn't get its IP through DHCP. In stead it takes a random (I guess it's random at least) IP, 169.254.26.47 and goes to subnet 255.255.0.0. This is strange because the PC is not different from the other: they're all fully updated Win2000 Pro.
I tried to enter the adresses manually, but that didn't make any difference (not that I expected so, but at least I could give it a try, except that I can ping the network when I do it manually (which I can't now with IP set to automatically).
There is one thing that comes into my mind that might be important to mention: the computer that doesn't want to configure to the network is a clone (with a different networkname of course) from another one on the network.

Although making me frustrated, I guess this is a pretty easy problem for you more experienced admins out there. Any help is appreciated! Things to exclude: the cables and the router (they're all OK, really sure of that). I tried reinstalling the TCP/IP protocol: no change; the systemlog doesn't say much except that DHCP gave adaptor #<doesn't matter> IP #<doesn't matter either, it's the wrong one>.

Aargh. My guess is that it has something to do with the cloning.

Peace,

Yellow

 

[Serbtastic]

The 169.254.26.47 address gets assigned when your computer can't reach the DHCP server, for whatever reason. When you assigned the IP/subnet/gateway/dns addresses manually, it should have worked. What do you mean it didn't work? Did you remember to assign the DNS server address as well?

 

[bluthund]

Hi, Is the clone image ghosted or a clean install? You may want to check the hosts file, or better, try an ipconfig /all from the CLI and then see if the IP has a lease period assigned. Ipconfig /all should give you the details to determine if you are getting the IP via DHCP. If so, you may want to check your routers' config. Otherwise you could then try ipconfig /release.

Lifetime Learner

 

[bluthund]

Oops,
Mea culpa, didn't look close at the IP.

Lifetime Learner

 

[YellowOnline]

Hello again,

serbtastic> yes I assigned the DNS servers as well; I tried it manually again after your post, but alas: even ping doesn't work (all time-out).

bluthund> I can't release or renew since it doesn't connect to the DHCP. The host-files are empty on all computers (except for localhost). When DHCP enabled I tried renewing it as well, but it keeps giving me the wrong IP - the one serbtastic learned me about that it's the one you get when DHCP cannot be reached. For this reason there is no lease either.
About the clone: I cloned a harddisk to another harddisk (in the same computer) through Partition Magic (Norton Ghost was annoying me, cf. the Hard Drive forum), then I put the clone into this computer, made the partition active through fdisk and everything was OK - except this networking thingy.

The problem gets down to not being able to reach the DHCP server, as serbtastic pointed out.

There are two differences if I take a closer look at ipconfig: the DNS-suffix - which seems quite obvious because this is from the ISP and the computer can't connect to the router so he can't connect to internet either.
And the second one might be interesting: type is set to Broadcast on the problematic computer, while the others are set to Mixed (I hope this is a correct translation).

Thanks for your time.

Peace,

Yellow

 

[bluthund]

YO,
ipconfig /all should give you a Windows IP config and beneath, one for your ethernet adapter. You have an
unknown
variable here, your NIC, which could have a corrupt driver or may be even faulty. See if you can resolve that issue first by reinstalling the driver or updating it. Also you could try a known good NIC. Basically, try to resolve the hardware issue first. Where did the box come from, on which you installed the OS image?

Lifetime Learner

 

[YellowOnline]

Thank you for your replies. I just removed the networkcard and installed another one, and running smooth. It wasn't driver related nor the networkcard is broke (checked it on another computer meanwhile).
Probaly it was wrongly configured somewhere when I booted it first (it had the same network ID as the clone then), and replacing the networkcard was the right way to reset that configuration. Meanwhile I put the original networkcard in it again, and still everything alright.

Peace,

Yellow

 

[bluthund]

YO,
check your ethernet cable as well. Try one you know that works.

Lifetime Learner