i have just learned about / resurched / configured / and tested DHCP yesterday. When i started i didn't know what it was and it was not even installed on my computer. I installed it, read about it, conigured the files, and then tested it once on my test network with two windows comps. When i shut everything down at the end of the day all the computers work working exactly like i wanted them to. The windows computers contacted the linux box receaved fixed ip addresses based on hardware and worked fine. 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. the only thing that does work is that the two windows computers can see each other just fine. 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???????????? Does anybody know what is going on??????????? thx scott FadMart - http://www.fadmart.com - An Associate of the World's Largest Store!
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
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 -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here --- Eingehende Mail ist zertifiziert virenfrei. Überprüft durch AVG Antivirus System (http://www.grisoft.com/de). Version: 6.0.618 / Virendatenbank: 397 - Erstellungsdatum: 09.03.2004 --- Ausgehende Mail ist zertifiziert virenfrei. Überprüft durch AVG Antivirus System (http://www.grisoft.com/de). Version: 6.0.618 / Virendatenbank: 397 - Erstellungsdatum: 09.03.2004
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
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
Hi, this should be described clearer. Check if there is STP enabled on the Port, and if so, disable. STP should _never_ be enabled on any Device, connected by a single Network Card. Neither the corresponding Port on the Switch. Otherwise you have a _complete_ Network Failure on any Client-Reboot up to 90 seconds, as STP is blocking all ports during negotiating of Spanning Tree. Greetings Dirk Brandon Hines schrieb:
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
TRIA IT-consulting GmbH Joseph-Wild-Straße 20 81829 München Germany Tel: +49 (89) 92907-0 Fax: +49 (89) 92907-100 http://www.tria.de -------------------------------------------------------- working hard | for your success -------------------------------------------------------- Registergericht München HRB 113466 USt.-IdNr. DE 180017238 Steuer-Nr. 802/40600 Geschäftsführer: Hubertus Wagenhäuser -------------------------------------------------------- Nachricht von: dirk.schreiner@tria.de Nachricht an: brandon@2i.com, suse-security@suse.com # Dateianhänge: 0 Die Mitteilung dieser E-Mail ist vertraulich und nur für den oben genannten Empfänger bestimmt. Wenn Sie nicht der vorgesehene Empfänger dieser E-Mail oder mit der Aushändigung an ihn betraut sind, weisen wir darauf hin, daß jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung sowie Weitergabe des Inhalts untersagt ist. Wir bitten Sie uns in diesem Fall umgehend zu unterrichten. Vielen Dank The information contained in this E-Mail is privileged and confidental intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient or competent to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this E-Mail is strictly prohibited. If you have received this E-Mail in error, please notify us immediately. Thank you
Hi, Is DHCPD running? Since you rebooted the server, you may have forgotten to enable automatic start. Try "rcdhcpd status"; if it says "unused" it is not running. Bye, Holger Am Donnerstag, 11. März 2004 04:14 schrieb Scott Wrobel:
i have just learned about / resurched / configured / and tested DHCP yesterday. When i started i didn't know what it was and it was not even installed on my computer. I installed it, read about it, conigured the files, and then tested it once on my test network with two windows comps. When i shut everything down at the end of the day all the computers work working exactly like i wanted them to. The windows computers contacted the linux box receaved fixed ip addresses based on hardware and worked fine. 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. the only thing that does work is that the two windows computers can see each other just fine. 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???????????? Does anybody know what is going on??????????? thx scott
FadMart - http://www.fadmart.com - An Associate of the World's Largest Store!
These addresses are what are called APIPA addresses. The windows DHCP
client will give these if it cannot get a proper address from a DHCP server.
Probably the thing to check is that your DHCP server is offering addresses
on the correct network interface.
Do you have two network cards?
If so it is common that the DHCP daemon on Linux will only offer DHCP on
eth0 but frequently this is the "WAN interface" i.e. the NIC that you plug
into your cable modem/router, etc. to connect to the internet and often eth1
is the one your local LAN is connected to.
It is fairly easy to get Windows to pick up DHCP off Linux servers, I have
configured it on at least five independant seperate networks in various
situations with various customers and various versions of Windows over the
years.
Let us know if you still have a problem.
Carl
----- Original Message -----
From: "Scott Wrobel"
i have just learned about / resurched / configured / and tested DHCP
When i started i didn't know what it was and it was not even installed on my computer. I installed it, read about it, conigured the files, and
yesterday. then tested it once on my test network with two windows comps. When i shut everything down at the end of the day all the computers work working exactly like i wanted them to. The windows computers contacted the linux box receaved fixed ip addresses based on hardware and worked fine.
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. the only thing that does work is that the two windows computers can see each other just fine. 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???????????? Does anybody know what is going on??????????? thx scott
FadMart - http://www.fadmart.com - An Associate of the World's Largest Store!
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
participants (8)
-
Armin Schoech -
Brandon Hines -
Carl Peto -
Dirk Schreiner -
Frank Huebsch -
Holger Schletz -
Michael Haunzwickl / SYN -
Scott Wrobel