Windows Wont PXE Boot
-
Not wireshark but you can use tcpdump for that. For simple debugging use this:
[CODE]tcpdump -i eth0 -nn udp[/CODE]
‘udp’ is just a very simple filter so that you don’t see to much other traffic…
If you want to dig into the packet dump you’re better of writing the captured packets to a pcap file and load that on a different computer where you can use wireshark:
[CODE]tcpdump -i eth0 -w tftp-debug.pcap[/CODE]
Change ‘eth0’ to whatever interface on the FOG you use… -
Ok using tcpdump I get a lot of traffic but caught the ip I was looking for:
IP 10.2.8.60.2075 > 10.2.8.5.69: 35 RRQ “unidonly.kpxe” octet blksize 1456
IP 10.2.8.5.52343 > 10.2.8.60.2075: UDP, length 15That is the only communication I see which is possible I missed more as there was a lot of code to watch. When I tried to do this command:
tcpdump -i eth0 -w tftp-debug.pcap
I get Permission denied -
Looks promising. Seams like the client sends a request to get undionly.kpxe from the TFTP server and the server also responds (second packet). To see this clearly you should get a full packet dump. Maybe try this:
[CODE]tcpdump -i eth0 -w /tmp/tftp-debug.pcap[/CODE]
You won’t see any packets on the console then. Run the command, start your client and stop tcpdump with Ctrl-C after your client got the timeout. ZIP and upload that pcap file and I’ll have a look and see what I can see… -
made the file but I am unable to FTP into the server the password it says to use at FOG_TFTP_FTP_PASSWORD in ver 1.2 its only 6 characters long and it doesn’t work I am using filezilla which has always worked in the past am I using the wrong password? I mean I remember the other one being about 20 chars long. Forgot to mention shows making a connection just says password is incorrect.
-
So I just tried to run ftp on the fog server itself and it say password is wrong as well, the only password that was changed was the default password for the fog web login which was never connected to the ftp before but it doesn’t work either I am not sure what is going on but I can’t believe that the ftp password is only 6 chars long.
-
So I tried the default username I created when I set up Ubuntu and that one lets me ftp in but fog username and password come up as incorrect. Anyways here is the dumped file, computer trying to get image is 10.2.8.60
[url=“/_imported_xf_attachments/1/1711_TFTP debug.zip?:”]TFTP debug.zip[/url]
-
don’t know why your password was changed, but it’s simple enough to change it again
[CODE]passwd fog[/CODE] -
From the packet dump I can see that the TFTP/FOG server receives the clients request for the file undionly.kpxe and answers back with option acknowledgement (see here for details about this: [url]https://tools.ietf.org/html/rfc2347[/url]). Normally the client is supposed to send another request then! My guess is that the server answer does not make it to the client. Can you connect a hub just in front of the client and capture packets there??
And please check out this troubleshoting guide too: [URL=‘http://www.fogproject.org/wiki/index.php/Tftp_timeout…’]http://www.fogproject.org/wiki/index.php/Tftp_timeout[/URL]
-
Well I solved the problem it was either the laptop or VM Player 6 moved program to a desktop with VM player 7 and no issues now I will try VMP 7 on the laptop to see if that’s the issue or if it was VMP6 causing the issues I am curious to see what it is and how I will fix it but for now it’s working this way.
-
Well found out what was killing VMPlayer from Network booting it was Symantec Network threat protection causing the issue when disabled it works just the way it should. Now I just need to find where to add an exception for vmplayer so I don’t need to keep disabling the network protection.
