The next thing I would look at is the setting of dhcp option 67. This will tell you if the tftp service is actually running on the interface you expect (if this is a dual homed host). Again I would check to see if you can see the port 69 listed in the netstat -an|more command. Now this could be that the client could not connect to the tftp server or the request file was not returned. This indicates that the tftp server did not return the requested image. William_H wrote:PXE-E32 TFTP Open Timeout error I know WDS isn't supposed to come into play in this as I have read tons of articles online talking about sccm and pxe booting, but what allowed me to pxe boot the one time, I set wds to not to respond to any clients, and put a 1 sec delay response to pxe request, then set sccm to respond to all pxe request, and put a 0 delay response time. The Windows Deployment Services Server service terminated with the following service-specific error:
I wouldn't be suprised if it has to do with WDS though as I had an error with that service trying to get it running again. I am getting a PXE-32 TFTP open timeout error. been racking my brain on this trying to figure out what changed, cause obviously if i could find that out, theoretically i should be able to get the machines to boot to it again As far as I know, nothing got changed between first boot attempt and second. I know the network is capable of it, as I managed to get a test machine to boot into it one time, and not again. Running into an issue getting SCCM to let me PXE boot.
0 kommentar(er)
