Is it necessary to have the ip-helper address on the vlan interface?
We are having problems with thin-clients obtaining a dhcp address. This happens sporadically and to resolve we must make a reservation in dhcp then give the client a static address with the reservation address then change the client back to dhcp. I feel like this is a switch problem.
If your DHCP server is located on the same subnet as the clients, then you do not need to have a helper address configured.
The purpose of the helper address is to forward the DHCP Discover packet, which is a L3 broadcast, from the client to the DHCP server when it sits on another vlan. A router will not forward broadcasts by default, so the helper address tells the router to forward the DHCP Discover packet in a unicast to the DHCP server specified in the helper address command.
Are you certain that the DHCP server itself is not experiencing problems? Maybe intermittent connectivity to the network?
Are you sure that the DHCP pool of addresses is not getting exhausted?
Thanks for info. I do not believe the dhcp is having problems. There are still plenty of addresses available and their are clients that are computers and they do not have this problem only the thin clients. My thinking was they act differently them the PC's. No one can seem to pin-point what the problem is. I want to make sure that my switches are not the cause.
The ip-helper address command is used to forward dhcp requests to a dhcp server, so it should be put under the vlan interface that your thin clients are on, by default the ip-helper address command forwards the following udp port no:37,49,53,67,68,69,137 & 138. The first thing to try would be to see if you can ping the dhcp server from the switch, also you may want to see if under the ports that the thin clients are connected too, you have spanning-tree portfast, may be the thin clinets are sending the DHCP requests before the port is actually in a forwarding state, spanning-tree portfast used only be used on ports that have one host.
Our external switches are controlled by a third-party and they refuse to set the ports to spanning-tree portfast. They have been notified by me about the problem but do not offer any solutions and do not want to set the ports to portfast. I think portfast would solve this problem. Good respond Will.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...