Solved

DOS TCP/IP Client and Windows 2000 DHCP

Posted on 2004-10-14
9
226 Views
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...

Thanks
0
Comment
Question by:970170
  • 4
  • 3
9 Comments
 
LVL 15

Expert Comment

by:adamdrayer
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.
0
 

Author Comment

by:970170
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.
0
 

Author Comment

by:970170
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!!!

0
 
LVL 15

Expert Comment

by:adamdrayer
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?
0
IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 

Author Comment

by:970170
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...
0
 
LVL 15

Expert Comment

by:adamdrayer
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.
0
 

Author Comment

by:970170
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..
0
 

Accepted Solution

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

modulo
Community Support Moderator
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Greetings, Experts! First let me state that this website is top notch. I thoroughly enjoy the community that is shared here; those seeking help and those willing to sacrifice their time to help. It is fantastic. I am writing this article at th…
A common practice in small networks is making file sharing easy which works extremely well when intra-network security is not an issue. In essence, everyone, that is "Everyone", is given access to all of the shared files - often the entire C: drive …
It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

744 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

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now