If NTOOL tells you "bootp/dhcp failed" it means exactly what it says. But this can have two different reasons. Either your packet driver is OK, but no dhcp server answered NTOOL's request. In this case there must be a problem with the dhcp server.
Or your packet driver did not load properly, possibly because it is misconfigured or invoked with incorrect parameters. Watch carefully the messages the packet driver issues while loading. Sometimes it helps in debugging to load the packet driver manually as it is easier this way to read all the messages. Usually the packet driver reports the ehternet address of the card it found. Does it look reasonable? And mTCP's DHCP message "failure to get dhcp address. check your cabling and packet driver settings" means the very same thing. If you failed to load the packet driver completely, then NTOOL would tell you "NO PACKET DRIVER FOUND" while mTCP's DHCP would write "Could not access packet driver". ___________________________________________________________ Empfehlen Sie WEB.DE DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 100,- Euro! https://freundschaftswerbung.web.de ------------------------------------------------------------------------------ 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
