DHCP and network Boot floppy IP problems
- From: "Bruce D. Meyer" <bdmeyer44@xxxxxxx>
- Date: Thu, 14 Apr 2005 22:19:20 -0400
I have sniffed the subnet while trying to receive a DHCP address with each
of the two Boot floppies below:
http://www.nu2.nu/bootdisk/network/
and:
http://www.netbootdisk.com/
I have a boot floppy that I used for about 6 weeks quite heavily during
development of an image.
We are in the slow careful process of switching over from an NT domain
network, to an Active directory forest.
Last week we switched our subnets DHCP server from the NT domain (Windows
2000 server) to a Windows 2003 server that resides on the AD Forest. This
server provides DHCP for our subnet only.
For reasons I cannot determine, I cannot get either of these network boot
disks to work with the new Windows 2003 DHCP server.
Here are my diagnostics:
Running a sniffer on the subnet, I looked for all DHCP traffic during the
period that I booted the machine with the network boot floppy.
I clearly saw the four parts of the DHCP transaction in the sniffed
traffic:
Discovery, Offer, Request, and Acknowledgement.
I saw this two times immediately in sequence. (About 10 seconds between
requests)
If I CTRL-BREAK out of Barts boot disk after it has hung it would then give
me an error stating that the IP address already existed. Checking the
sniffer again, I would see the ip in question did exist, on the MAC address
of the machine running the boot disk. In other words, the machine was
getting the IP address offered, and accepting it, but for some reason, with
both boot disks, the IPCONFIG felt it did NOT have the ip assigned properly.
Moving this machine to a different subnet, booting with each boot disk from
a subnet with a Windows 2000 DHCP server in the Active Directory Forest
(Same forest, different domain site, and subnet) I had success 100% of the
time.
Now, to confound this even more. Earlier in the morning, I had received IP
addresses that satisfied the boot disks on three machines all about the same
time. Then, no success for the rest of the day. I am not clear of what could
be different between Server 2003, and 2000 that could cause this. I don't
believe it is the boot disk at fault, as it worked for six weeks with a
Windows 2000 server, and still works this way. It only fails with the
Windows 20003 server. All hardware is identical on the machines I am running
the boot disk on.
On a note that I can't imagine is related, This Windows 2003 DHCP server is
also a RIS server with the setting for Don't accept connections from
unauthorized clients set. (In the RIS settings) I did unselect this and it
made no difference.
Thanks for any guidance on how to solve this. Ultimately, all I care about
is getting a network boot floppy that will allow me to map to a machine to
pull images from.
Has something changed in DHCP on Windows 2003 that might affect non Windows
clients from understanding the DHCP transaction? If you try to duplicate
this you may find it works fine, and then later, stops working, as I have. I
went from Not working on Wednesday, Working Thursday morning, and not
working the rest of the day. These boot disks also have no problem accepting
DHCP when I hooked them directly into a Cisco 837 router acting as a DHCP
server.
Bruce D. Meyer, CCNA, MCSE
Network Analyst
City of Columbia, SC
.
- Follow-Ups:
- Re: DHCP and network Boot floppy IP problems
- From: Bruce D. Meyer
- Re: DHCP and network Boot floppy IP problems
- Prev by Date: Re: How does it work? Easy question.
- Next by Date: Linksys BEFSX41 IPSEC VPN connect to SBS 2003 with 2 nics and NAT
- Previous by thread: How does it work? Easy question.
- Next by thread: Re: DHCP and network Boot floppy IP problems
- Index(es):
Relevant Pages
|
