(MDT), WDS and PXE TFTP not happening

[PiqueABoo]

Just playing virtually and will probably give up soon and use Plan-B, but I've got MDT and WDS on a DC alongside DHCP. MDT is only relevant in that I've imported it's PE boot wim into WDS. So with a little help from Network Monitor...

 

PXE client boots

PXE client gets an IP address etc.

PXE client gets path+name of PXE boot file it needs to TFTP

PXE client requests the boot file from (WDS) TFTP, but it doesn't respond - no network packets are returned to the client.

 

Netstat -anb shows WDS listening on the TFTP port, WDS is set to talk to any old client, the firewall is off.

 

Is there some big TFTP Responses ON/OFF button I'm missing?

 

--

Plan-B which worked, was to turn WDS off, set DHCP options 66 (server's address) & 67 (pxeboot.n12), kill option 60, install the freebie Solarwinds TFTP and put this lot all in TFTP-Root because subfolders don't work:

 

BCD

boot.sdi

bootmgr.exe

pxeboot.n12

winpe.wim

 

winpe.wim is a renamed Lite Touch PE wim.

Edited September 16, 2008 by PiqueABoo
Plan B

[Gatt]

I get a similar issue with WDS.. (Same setup as PiqueaBoo above)

It freezes at TFTP... just after the workstation gets an IP address.

It then takes up to 5 mins for it to proceed to the F12 prompt

 

Sometimes it fails with a TFTP Open Timeout (PXE-E32?) or I get the F12 - choose my option (Deploy) but then errors saying it cant get the nece3ssary files

 

This has only happened in the last week.. Wondering if this is cos of any recent updates?

[john]

I just built my WDS box this week and seems fine, took the vista boot image from a Vista Business CD Set we have on VLK and its been fine. Is your file corupt perhaps? Is it worth re-loading the winbom.img?

 

Has your server got 2 NICs in it? If it has disable one of them and try it with just one live and active to see if that helps, RIS never liked more than one OOTB.

[PiqueABoo]

It's not corrupt images and there's just the one virtual NIC. This is simply 2008 WDS TFTP component listening but not responding (no return network packets) to the initial request for the initial boot file - don't recall the file name in the request, but it was a *.com and it was there in what I **think** is the right place on the server.

 

Apparently (I'm no expert) WDS TFTP used to be a bit more standalone amd complete, but it's more integrated with the WDS service in 2008 and only implements the subset of TFTP you need for WDS. Maybe it doesn't like the request for some reason so just ignores it.

 

If I could maybe a) find or enable a relevant log, b) persuade it to spit out a bit of detail I might get further... but so far I can't find any info on whether that's possible or not.

[c0pe]

I am having the same issue! has anyone figured this out?

 

PXE-E32 TFTP open timeout

 

mdt and wds running on server 2008 sp2 (also a domain controller)... was working fine for a long time now this problem...

 

whats the deal?

[plexer]

I have a virtual 2003 server as my WDS server, DC and DHCP are on another physical server and it all works as it should.

 

Ben