To add to this I was able to obtain the trail of the tracing log 5772] 15:57:16: Expression:, Win32 Error=0x284 the only difference was that it acknowledged each packet where as WDS acknowledges in a set of fourīelow is an example of the TFTP traffic at the point of failure I immediately suspect the firewall, however I'm told by our firewall people that the firewall is not configured to stop TFTP packets,Īlso I was able to successfully transfer a large using tftpd from the same server. I have looked a wire shark trace to see what is happening on the wire, and it look like the TFTP packets are transmitting until a random point and then stop. I have a hard time believing this because it works successfully for weeks at a time. This message means that the client started downloading the file, but didn't finish and the server is terminating the connection since it hasn't seen any packets from the client in a long time. The Following Client failed TFTP Download:ġ460 is ERROR_TIMEOUT. The WDS server gives us the following error The problem we are having is that every few weeks we seem to lose the ability to PXE boot across the firewall to the WDS server Out workstations on one subnet and servers across a WAN link on a separate subnet with a juniper firewall in the middle We have a relativity simple network topology I am hoping to get some advice on some of the WDS issues we have been having over the past 4-5 months
0 Comments
Leave a Reply. |