RIS, Blus Screening for duplicate IP address's

[Kyle]

I think i have read about this before on here but i can't seem to find it. I have had a couple of issues over the last few days with RIS. It has happened on 2 different sorts of pc's. I have gone to re-image a pc and get a Blue Screen error complaining od Duplicate Ip Address or IP address currently in use.

 

I have checked DHCP and i cant find a duplicate, I also find that if i leave the pc off for a few hours it then works fine. I have tried removing the PSU, resetting BIOS etc ans it still keeps getting-ht duplicate ip address blue screen.

 

Does any one know what causes this or an explanation/way round it?

[Dos_Box]

I had an identical problem a few weeks ago with a brnad new Dell. What you have to do is exclude the IP from your range in DHCP, and then RIS the system. You can realease the IP safely after this. It only effected 1 PC out of a batch of 40, and the problem was unheard of by them. They even added the fix to thier KB

[ajbritton]

If you configure your DHCP server to 'test' each IP before it is handed out, this should happen less often.

[Dos_Box]

That wasn't an issue. The address was good, and not pingable or in use by anything else. The system just hated it. No reasons were detectable. A new IP later and all was well.

[Geoff]

Duplicate MAC addresses perhaps?

[Dos_Box]

Nope. It's Dell kit and when you setup the computers managed account no duplicates were detected.

[ajbritton]

Just because you can't ping an IP address, does NOT mean it is not in use. Of course, if that was the case the DHCP server would not be able to detect it either I guess!

[Geoff]

True, a windows machine with it's firewall up would be an obvious culprit.

[Dos_Box]

Nope, nope and nope. I spent 4 days looking. The adress was never leased to anything apart from that machine, XP firewall is disable in GP. DNS registered nothing to that IP, and I used numerous tools to search it out. In short, it was a rouge IP that RIS or the PC took a dislike to.

The strage thing is, you would start RIS imaging fine, and bomb out after about 20 - 30 seconds.

[Geoff]

I wasn't a 'bad' address like .255 or .0 was it? Windows TCP/IP has a dislike to these addresses (even though they are perfectly valid in our /22 range).