Pxe boot halts with MTFTP message on specific platforms
-
It’s a symlink
-
I’m trying the latest svn to see if it makes a difference. And I’ll try pointing the filename to undionly.kpxe instead
-
It didn’t make a difference. =(
-
AFAIK ‘TFTP Aborted’ here just means that the client tricks the server to aquire the file size before requesting the whole file. Do you see any more TFTP traffic after this (maybe leave it for a few minutes)??
By the way, 59 is the size of the packet and NOT the error code!
For a more detailed explanation see here: [url]http://www.vercot.com/~serva/an/WindowsPXE1.html[/url] (8.7- Troubleshooting TFTP issues.)
-
Oh yeah, I knew that about the packet size. I just haven’t used wireshark in a while, how silly of me.
I had left the packet capture on and noticed that there was some more tftp traffic about 10 minutes after the tftp abort.
It transfers 203 blocks one packet at a time and then send default.ipxe.
Since I wasn’t monitoring it when this happened I don’t know if that means it eventually did get to the boot screen.
So I started an upload task and stayed and watched this time.
It seems it does boot into it, yay! But it takes an extra 10 minutes on VM’s and the HP 8000 elite. And there’s the annoying proxy dhcp issue on the 8000 elite as well.
I’m not sure I’d quite call this resolved though, but I suppose having to wait an extra 10 minutes isn’t that big of a deal.Thanks,
-JJ -
Interesting stuff… I’m sure I read something about 10 minute issue somewhere yesterday… Ah, found it! But it is in german I suppose: [url]https://forum.opsi.org/viewtopic.php?f=7&t=910[/url]
Try online translator or maybe I just give you some hints on what they are talking about. In the first post you see two packet dumps. First one is working perfectly, second one (pay attention to the timestamps) hast the 10 minute issue. And then in the last post the same guy says that he’s solved it and mentions a misconfiguration of their DHCP server. In his case vendor-specific options (option 43) were misinterpreted by the TFTP client and made it do this weird thing of timing out after 10 minutes before retrying again… hope that helps.EDIT: Just found another post in a different forum: [url]https://social.technet.microsoft.com/forums/systemcenter/en-US/db17272b-68f1-4b18-a9b7-b0391bf846d8/pxe-booting-strange-problem[/url]
And Tom is right, it boils down to the question of who and why this options was configured?! We see quite a few people having TFTP issues lately. Maybe same issue…?? -
If 43 fixes it the question then becomes did you implement or has there been VoIP introduced in your network?
-
Well after updating to the latest svn and watching and monitoring the packets as the mtftp thing took 10 minutes on a vm and then restarting the server, the 8000 elites magically started working again and it looks like VMs too.
Maybe option 43 was enabled somewhere I don’t have control over, it’s a common model in the college and some people using the same dhcp server use landesk for their imaging, maybe they were trying something with that. I’ll ask around, I don’t like magical solutions to problems other people might be looking for answers too.
Maybe I just had to let the mtftp run it’s course a few times?As for VOIP, that does exist on our network, lots of ip phones, but it’s never caused a problem before.
Now I am having a new problem though. The answers probably somewhere else in these forums though. I’m now getting a can’t mount nfs error. Probably to do with updating FOG versions, oh and by the by I really like the new interface and I’m excited to try out this mac os X image option. But first I gotta solve this NFS not mounting thing.
Thanks for all your help. I love these FOG forums, so very helpful all the time.
-JJ
-
[quote=“mecsr, post: 42909, member: 23886”]As for VOIP, that does exist on our network, lots of ip phones, but it’s never caused a problem before.[/quote]
Kind of weird isn’t it. Just another one of those “haven’t changed anything” issues.
Just kidding…[quote=“mecsr, post: 42909, member: 23886”]I’m now getting a can’t mount nfs error.[/quote]
Try mounting the shares from another computer and see if you get any errors…
[CODE]mkdir -p /mnt/nfstest && mount -v <server-ip>:/images /nfstest
umount /nfstest
mount -v <server-ip>:/images/dev /nfstest
umount /nfstest && rmdir /nfstest[/CODE] -
Thanks, I just tried that, but I noticed the same problem in another thread where someone is having the same problem, and where you told them to try the same thing. So I’m going to post the results over there
[url]http://fogproject.org/forum/threads/problem-with-permission-denied-after-fog-server-restart.12503/[/url]Gotta help keep the forum organized and what not right. I’ll post here again if I here back about whether or not option 43 was touched by someone else.
Thanks again for all the help.
