[SOLVED] PXE Boot Different Subnets Microsoft WDS Server

Associate
Joined
7 Aug 2012
Posts
949
[ooooops just realised this might be have been posted in the wrong sub-forum]

Hi All,

I was wondering if you could help....?

I've setup a Microsoft Server 2016 WDS Server at LocationA, and on the local LocationA LAN it works fine. Local PCs get a DHCP address from the local switch, the PC PXE boot finds the WDS server and the imaging works fine.
Note, there is no DHCP configuration on the WDS server.

At LocationB, the LAN is on a different subnet, however routing is working between the two locations (A and B) and I can ping the WDS server from LocationB LAN switch, as well as LocationB PCs logged into Windows, so the routing appears to be OK.

When I try and PXE Boot from LocationB, the PXE PC gets the correct IP and Default Gateway Information from the LocationB LAN/DHCP pool, however the closest I've got it to working is under Configuration 1 below. Reading online it sounds like Configuration 2 is all I need, however it doesn't seem to work.

So far I have tried the following network switch configurations at LocationB....

Configuration 1:
DHCP Pool: option 66 ip <LocaitonA WDS IP Address>
DHCP Pool: option 67 ascii Boot\x64\pxeboot.com
VLAN x: ip helper-address <LocationA WDS IP Address> configured
,

Result: LocationB PC PXE boot reports two instances of PXE-E32: TFTP open timeout, 4x events are recorded in the WDS event log stating the download failed, example below:

The Following Client failed TFTP Download:
Client IP: <LocationB PC IP Address>
Filename: Boot\x64\pxeboot.com
ErrorCode: 1460
File Size: 25358
Client Port: 2074
Server Port: 54845
Variable Window: false

----------------------------------------------------------------------


Configuration 2:
no DHCP pool option 66 configured
no DHCP pool option 67 configured
VLAN x: ip helper-address <LocationA WDS IP Address> configured

Result: LocationB PC PXE boot reports PXE-E53: No boot filename received, there are no events recorded in the WDS server event log
----------------------------------------------------------------------
Configuration 3:
DHCP Pool: option 66 ip <LocaitonA WDS IP Address>
DHCP Pool: option 67 ascii Boot\x64\pxeboot.com
no ip helper-address configured
Result: LocationB PC PXE boot reports one instance of PXE-E32: TFTP open timeout, there are no events recorded in the WDS server event log


Any help on this matter would be appreciated.

Thanks

Swain90
 
Last edited:
I've managed to get a little further.

Changing the TFTP block size from 0 > 512 in the WDS Server Manager, I now get successful TFTP downloads recorded in the WDS event viewer, however the PXE boot screen progresses to the next stage, but then displays TFTP download failed.
 
Last edited:
Finally got it working!



My DHCP Pool: option 67 parameter was wrong on the switch, i've changed it to DHCP Pool: option 67 ascii Boot\x64\wdsnbp.com and then also changed the TFTP block size in the WDS manager to 1024 and everything has sprung into life.
 
Back
Top Bottom