DOS TCP/IP Client and Windows 2000 DHCP

Posted on 2004-10-14
Last Modified: 2010-03-18
Ive been using a boot CD for ghosting computers.  The boot CD boots in DOS and runs the Microsoft TCP/IP Network Client for DOS.  I was able to get everything working, including successfully getting an IP address from a DHCP server on the network.  This DHCP server used to be on Windows NT.  I have since switched DHCP services over to a Windows 2000 server.  I am now unable to get an IP address from my DOS boot CD.  The only clue I have is that if I create a reservation on the Win2K DHCP server for the specific MAC address of the machine Im booting my CD from, IT WORKS!!.. This solution, however is not feasible as I will be moving to many machines and obviously cant go around adding new reservations on my server all the time.  My question is... is there something that Windows 2000 DHCP Servers do that do not give out IP addresses to non-windows machines or something?  Ive poked around the DHCP settings but cant seem to find anything relevant.  Can anyone explain to my why it works if I put in a reservation for the specific computers MAC?  I am totally confused.  Please help...

Question by:970170
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
LVL 15

Expert Comment

ID: 12317818
Is your NT Server still running DHCP?  If you reserve the address in 2000, it shouldn't pick up a new IP unless you have a rogue DHCP server out there.

Author Comment

ID: 12318200
No, Ive shut down all DHCP services on the NT box.  And when I say I've added a reservation, it means that I've told the 2000 server to assign a specific IP to a specific MAC address.  When that MAC contacts the DHCP server, DHCP gives it the predetermined IP instead of taking a random one from the pool.

Author Comment

ID: 12318207
I am willing to bump up the points if someone can help me solve this problem... I know its got to be something quick and someone out there must know it!!!

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

LVL 15

Expert Comment

ID: 12318704
Check your protocol.ini, does it mention the old NT server by IP address anywhere?  does it have disableDHCP = 1?

Also, have you gotton the W2k DHCP to work on any computer?  is the NIC it is listening on configured with an IP address and subnet mask inside the scope it is leasing?

Author Comment

ID: 12319339
No.. protocol.ini does not mention any IP address and no i dont have disableDHCP=1.  Dont mean to repeat myself, but it WILL work if i put in a reservation for the MAC.  So it appears as if the correct W2K server is sending out the correct broadcasts.. and that it is available on the network.  Yes all my windows workstations work fine with the new DHCP server, its only the DOS boot CD that refuses to.  No the DHCP server's IP information is not within the scope that it is leasing...
LVL 15

Expert Comment

ID: 12319564

>>No the DHCP server's IP information is not within the scope that it is leasing...
Well it should be.  Not that the server's IP address shouldn't be reserved but it is important that the DHCP server be on the same logical subnet as the addresses it is leasing.

after the client receives the IP address information, the DHCP server and client need to be on the same subnet for the finalization to work.  The fact that the DHCP server is working when it is specfically communicating with the client by MAC address is a hint that this is the problem.

Author Comment

ID: 12320166
I figured it out!!..

1) my DHCP and clients are of course on the same subnet, i just said that the server's IP itself is not in the scope of what im designating as "client" ranges.  they are both in the same subnet and are talking.

2) the problem was that I did not have dynamic BOOTP enabled on the server.  the MS DOS tcp/ip client uses the old protocol instead of straight DHCP and thats why it wasnt picking anything up.  I read through the entire DHCP manual and finally stumbled onto it.

Thanks for your efforts..

Accepted Solution

modulo earned 0 total points
ID: 13237980
PAQed with points refunded (250)

Community Support Moderator

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Preface There are many applications where some computing systems need have their system clocks running synchronized within a small margin and eventually need to be in sync with the global time. There are different solutions for this, i.e. the W3…
We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
Finds all prime numbers in a range requested and places them in a public primes() array. I've demostrated a template size of 30 (2 * 3 * 5) but larger templates can be built such 210  (2 * 3 * 5 * 7) or 2310  (2 * 3 * 5 * 7 * 11). The larger templa…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question