TFTP Server
-
@Raymond-Bell Is there any possibility of a Rogue DHCP server on your network right now?
-
@Tom-Elliott said in TFTP Server:
@Raymond-Bell Is there any possibility of a Rogue DHCP server on your network right now?
Nope Unless one of the new switches is handing out dhcp but i dont see that happening
-
@Raymond-Bell Do the new Switches have the proper IP Helpers in place to point at the DHCP server?
I know this is a lot of questions, just thinking all possibilities.
A good way to test is to put a machine that may be on your new switch, and put it in between (before the new switch) and see if all is working properly.
-
@Tom-Elliott said in TFTP Server:
@Raymond-Bell Do the new Switches have the proper IP Helpers in place to point at the DHCP server?
I know this is a lot of questions, just thinking all possibilities.
A good way to test is to put a machine that may be on your new switch, and put it in between (before the new switch) and see if all is working properly.
LOL i would but every switch is a new switch and all i done was set up the Vlans on them 40 new switches and new single mode fiber
-
@Raymond-Bell Well, if I remember my working in a Central Network area, the only switch that required the IP helper was the “central” switch. So assuming a similar setup (multiple switches, all vlan’s pointing to a Central switch, and that switch communicating with your DHCP server) the IP Helper statement would just need to be setup for each vlan to point to your appropriate dhcp server.
Hopefully this helps.
Also, if you had VLAN specific Boot Options for 66/67, maybe make sure all are setup appropriately. I’m guessing, though, that you have it set as the “global” scope.
-
@Tom-Elliott You think i need to turn DHCP replay on on all the switches? or just the core switch?
-
@Raymond-Bell Just the “core” switch as I’m guessing all others already know how to route to the core.
-
@Tom-Elliott I don’t think it would be the core because the STATE
owns the core switch… I may just try just that link port on first switch in line from the Core -
@Tom-Elliott Ok after some testing with 2 computers plugged in to same new switch one works great boots right in to fog the other enter tftp server same computers models same DHCP
-
@Raymond-Bell Then I really don’t know what’s going on. I’m sorry man, maybe @Sebastian-Roth or @George1421 can be of some more help. I’m not much on the figuring out side as I used to be, and I’ve given everything I can think of.
Sorry I’m not more useful at this point.
-
@Tom-Elliott said in TFTP Server:
@Raymond-Bell Then I really don’t know what’s going on. I’m sorry man, maybe @Sebastian-Roth or @George1421 can be of some more help. I’m not much on the figuring out side as I used to be, and I’ve given everything I can think of.
Sorry I’m not more useful at this point.
Ok thanks man…
i even unplugged the one that was giving me the tftp and plugged it into the port one that is work and same error
-
@Raymond-Bell TBH I only skimmed this thread so I may have missed something. But my intuition is telling me there is a secondary dhcp server responding to the target computer giving it conflicting pxe boot info.
-
So lets start with some data collection.
Is the dhcp server, fog server and target computer all on the same subnet/vlan? If so we can use the fog server to help us see what is going on in the pxe booting process.
I have a tutorial here on how to use tcpdump from the FOG server to capture a pcap file of the booting process: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
If the dhcp server, fog server, and pxe booting client are on the same subnet/vlan then go and grab the pcap and post it here. If any is on a different vlan then give us an idea of your network design so we can come up with a useful plan to collect this information.
-
@george1421 yes there are all on same subnet/vlan
Here you go sir0_1542402185175_output.pcap10.24.32.60 is the ip the host pulled from dhcp
-
@Raymond-Bell Ah found it.
You actually have 3 dhcp servers responding. If you use wireshark and inspect the pcap file at patch #19 There is a dhcp server 192.168.15.1 that is giving band info. The other 2 dhcp servers 10.24.31.232 and .230 are in harmony. The 192.168.15.1 appears to be a cisco router on the surface.
-
@george1421 You the man i will look for that and i might just know what it is sorry to bother all of you …
-
@Raymond-Bell That 192.168.15.1 looks like its a real device on your network in that its giving the correct domain name, but its subnet mask and IP address range is not compatible with the rest of your network.
-
@george1421 said in TFTP Server:
@Raymond-Bell That 192.168.15.1 looks like its a real device on your network in that its giving the correct domain name, but its subnet mask and IP address range is not compatible with the rest of your network.
Ok might be the Earth Quake centers stuff
-
You mean I was kind of on the right track? Lol. Yay me! I just don’t do all the fancy pcap stuff sorry.
-
@Tom-Elliott said in TFTP Server:
You mean I was kind of on the right track? Lol. Yay me! I just don’t do all the fancy pcap stuff sorry.
LOL you are fine im thinking it might be a Cisco ATA i had a user connect this morning