Yes, you should also check for spanning-tree options. Many computers today boot faster than STP is able to activate the port. Your DHCP requests are likely never making it onto the network. Frank Huebsch wrote:
Hello!
What kind of network infrastructure are you using? I experienced problems with dhcp clients connected to managed switches. The problem ocurred when fastpath was activated on the client port. After disabling fastpath the first dhcp request passed without problems.
Can anyone give me further information on the reason/implication?!?
HTH Regards, Frank
-----Original Message----- From: Michael Haunzwickl / SYN [mailto:michael.haunzwickl@syn.at] Sent: Thursday, March 11, 2004 8:36 AM To: armin.schoech@web.de; suse-security@suse.com Subject: AW: [suse-security] DHCP Problems
Hi there,
My experience shows my that windows (xp specially) takes a few moments to capture the ip address from the DHCP Server, and before it captures the IP from there, it is assigning those 169.254.x.x addresses. That means ... When you startup the pc, open a dos box and enter "ipconfig" you will see those 169.254.x.x address, wait a view seconds and repeat the command and you will get correct IP and Subnet from the DHCP, wait a few moments more and you will get the Standardgateway. It seems that XP takes a longer time then NT, 2000 to get the DHCP infos.
The problem is now: If you have a script in the autostart file, which is mapping your Drives or if you have Network drives mapped automaticly by the win-explorer-functions, it will not succeed, because the commands are executed before the DHCP Ips are received ...
M
-----Ursprüngliche Nachricht----- Von: Armin Schoech [mailto:armin.schoech@web.de] Gesendet: Donnerstag, 11. März 2004 08:18 An: suse-security@suse.com Betreff: Re: [suse-security] DHCP Problems
Hi Scott,
Today i start everything up and nothing is working the same way. the ip addresses on the windows comps are 169.254.150.xx when the specified range is 192.168.1.1xx the subnet masks are wrong and the gateways on the windows comps are non existant.
--> please make sure you have set "Get IP automatically" on the windows machines. The 169.254. IP is chosen automagically by Windows when nothing else is available.
the only thing that does work is that the two windows computers can see each other just fine.
--> This is because they both have 169.254. IPs and thus are on the same subnet.
both windows computers have been instructed to talk to the linux box and one (win 2000 pro) says that it has done just that when asked with ipconfig /all, the other one is going somewhere totaly different for the address. they are supposed to go to 192.168.1.44 and the stray (win 98) is going to 255.255.255.255 for a DHCP server????????????
--> Before receiving an IP from the DHCP server, the client can just send out a packet to everybody (broadcast: 255.255.255.255) and wait for an answer from a DHCP server telling his own IP and the new IP the client should use.
Does anybody know what is going on???????????
--> Try to run "tcpdump port 67 or port 68" on the DHCP server to see the incoming DHCP packets and the replies. Do you have a firewall on the DHCP server ? It has to let through the DHCP packets (port 67/68) from the internal net.
Good luck! Armin
-- Am Hasenberg 26 office: Institut für Atmosphärenphysik D-18209 Bad Doberan Schloss-Straße 6 Tel. ++49-(0)38203/42137 D-18225 Kühlungsborn / GERMANY Email: schoech@iap-kborn.de Tel. +49-(0)38293-68-102 WWW: http://armins.cjb.net/ Fax. +49-(0)38293-68-50