WDS/PXE server setup issues.
Posted on 2014-09-11
I am currently in the process of setting up an additional WDS/PXE server for another office to host and deploy .WIM images. The server is currently setup with two NICs, one setup for IPv4 DHCP (to the internet/domain named Local Area Connection), and one for IPv4 static IP (the network computers will PXE boot from named WDSLAB.NET). This configuration works great on our existing WDS but I cannot get it to function correctly on the one I am building. This server is not on our domain or in AD.
I have the following roles active on the server:
Windows Deployment Services (the only feature is Transport Server)
The static IP NIC (WDSLAB.NET) is setup as follows:
IPv4 address: 192.168.2.101
Subnet mask: 255.255.255.0
Default gateway: 192.168.2.1
DNS servers: (using DNS servers that are known on the separate corporate network)
A DHCP Scope has been configured to exclude 192.168.2.101 (the server) and assign 192.168.2.100 - 192.168.2.250.
The following options are enabled for the DHCP Scope/server:
003 Router : 192.168.2.1
066 Boot Server Host Name : 192.168.2.101
067 Bootfile Name : D:\RemoteInstall\boot\x64\WDSNBP.COM
015 DNS Domain Name : wdslab.net
060 PXEClient : PXEClient
No reservations or filters are configured. The firewall service is disabled.
Shares are configured properly under File Services (the share was copied/cloned from our other working server).
All settings have been mirrored, and this server is on a separate isolated network from our other working server.
Client computers sometimes lease an address, but boot with the following error:
PXE-E55: ProxyDHCP service did not reply to request on port 4011.