My advice ...

Your problem reports are confusing.  You say that something is not 
working, but it had been working before.  If that is the case, what are 
you changing?  If you can't remember what you changed then it is time to 
slow down and take some notes.

The general method for getting a DHCP address is:

[1] Load the packet driver.  Check the packet driver messages to ensure 
that it actually loaded and that it found the Ethernet card.  It should 
report the MAC address of the Ethernet card and any IO port or IRQ 
settings that it is using.

[2] Wait a few seconds.  Sometimes the cards take a few seconds to 
initialize.  If you are using a batch file that loads the packet driver 
and then runs the DHCP client this is very important.  (Probably not as 
important if you are on VirtualBox or some other machine emulator.)

[3] Run the DHCP client.  In the case of mTCP that program is DHCP.EXE.  
WATTCP varies, but NTOOL is a nice, self contained solution that has 
been discussed here in detail.

If the packet driver is not loaded the DHCP client will probably tell 
you that it could not find the packet driver in memory.  If the packet 
driver is found the DHCP client will send a DHCP request to your cable 
modem, DSL modem, or whatever DHCP server device is on your network.  
That request can fail because of packet loss or timeout - if it fails, 
try it again.

Things you can do to help you debug:

[1] Run with a minimum amount of 'stuff' in your CONFIG.SYS and 
AUTOEXEC.BAT files until you figure out a combination of steps that 
works correctly every time.  You might be loading a device driver or 
program that is causing problems.

[2] Make sure your network cabling is good and well connected.  I have 
had cables go bad before.  Substitute known good cables if you are in 
doubt.  Read the lights on your Ethernet adapter and understand what 
they mean.  Do the same on the router or switch that it is connected to.

[3] Check the lights on your router or switch when the DHCP client is 
running.  Packets will cause the lights to blink.

[4] Check the DHCP server logs if you can.


And lastly, I already mentioned that all of the mTCP applications 
include a debug trace that you can turn on.  Read the DEBUG.TXT file for 
instructions on how to turn it on.



Mike

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to