TFTP Connection Fail
-
I217-LM network adapter
-
Is it on the same switch as the ProDesks?
-
@Brenth453 Any changes? OS update, FOG update, network changes, switch configuration? firewall?
-
@Quazz Yes same switch and the same network. I tried switching ports on the switch. I am also using the same cable and port plugged into the other PC’s.
-
@Sebastian-Roth As far as changes go, none were made before the issue. I disabled firewall to troubleshoot and I can TFTP from any laptop on our network. I have 2 networks set to give DHCP one is a switch and one is a DHCP server both work fine for giving the DHCP address for the PXE boot. It just seems to be this machine having an issue with TFTP.
-
@Brenth453 said in TFTP Connection Fail:
I have 2 networks set to give DHCP one is a switch and one is a DHCP server
Do those operate at the same time? Some PC firmware is not coping when receiving two DHCP answers!!!
-
@Sebastian-Roth They are on two networks. They act as DHCP for all of the things on their individual IP scheme. aka .112 and .126 networks. The DHCP doesn’t seem to be the problem because I watch the device get assigned the IP. It is after that when TFTP hangs.
-
@Brenth453 Are those two DHCP “servers” on the same physical network? I have seen clients that totally stall or do weird stuff just because they receive two ansers from different DHCP servers.
Can you configure a monitor port on your switch where the client is connected and then capture traffic using another PC/laptop and wireshark? It’s a lot easier to diagnose when we actually see what’s on. Wireshark hast great display filters like
dhcpandtftp. Please upload the PCAP and post a link here so we can have a look. -
@Sebastian-Roth They are on two different VLANs. One handles DHCP through a cisco switch and the other handles DHCP through a server.
-
@Brenth453 said in TFTP Connection Fail:
What is weird is that I was able to image this computer before no problem
Again I need to ask you what has changed. How would we be able to give advice without knowing that background? It can be many things causing this, including a firmware update on those machines… as well as other things mentioned before.
-
@Sebastian-Roth It was a windows 7 machine that couldn’t be logged into so it was wiped and then imaged with windows 10. Otherwise, I did nothing else with the machine or the network configuration.
-
@Brenth453 What else can I tell you? You asked for our thoughts and I gave you a bunch. Feel free to follow this (like take a package capture with wireshark) and share more information with us. We won’t be able to help otherwise.