WDS - PXE Headaches

[mrbeatnik]

Hey all.

Ok, so a PE forum but a WDS connection question.

Tri, I understand if you move the thread to a more appropriate area! Wasn't sure where best to post.

So I have WDS setup on our live server now in native mode (Win 2008 R2 x64).

I have modified option 66/67 on the DHCP server for the reservation of one machine I am testing at the moment.

(66 = IP address of WDS, 67 = boot\x86\wdsnbp.com)

WDS is setup to accept all clients at the moment (no approval required).

I have a boot.wim ready.

I boot up the PC and PXE boot and.... it doesn't boot.

PXE-E53: No boot filename received.

Now normally we have a RIS server (still up and running) configured through the scope for options 66/67.

This works fine of course.... so I'm unsure where the problem is here.

Client is on subnet 103.

DHCP is on subnet 222.

WDS is on subnet 250.

Any help is of course appreciated!!

[Tripredacus]

67 needs to be "\boot\x86\wdsnbp.com" <-- notice the first slash. What you typed did not have that.

I have not tested using relay servers and 2008, only 2003. I am not sure what difference there is between the two. Also I have not dealt with everything being on different subnets.

[mrbeatnik]

No joy there...

Had tried various combinations of the filename, just in case

The \ at the beginning of the ROM name doesn't solve this issue.

[Tripredacus]

Try adding options 6 and 3 as in the WDS guide in my sig.

[mrbeatnik]

Hey Tri,

Fixed it!

Problem was a little obscure I guess.

We set Server scope options (which point to our existing PXE), which in turn applies the options to all reservations on all subnets on that particular DHCP server.

I tried to change the scope options 66/67 on an individual reservation - which appears to work from the MMC, but really the server scope options are still overriding this, even though the reservation does not show the server option any more.

d'oh!

Thanks anyway!

[mrbeatnik]

Hmmmn, although Microsoft says that the scope overriding is not how it should work.

The reservation level options should actually override the server scope options, which isn't happening.

http://technet.microsoft.com/en-us/library...705(WS.10).aspx

Well, in any case I am ok just now, but still strange why that is happening.

This is definately not a PE topic anymore