• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5337
  • Last Modified:

Windows Deployment Services - Cannot communicate with WDS Server after PXE Boot

I am currently experiencing an issue with my Windows Deployment Server. I have built it up, configured it, loaded in some boot.wims and injected relevant drivers for the hardware. I have also created a custom unattend file to connect it to the relevant Install.wim image and drivers etc.

When I PXE boot the laptop, the Windows Boot Menu comes up as expected, and I select the image I wish to boot to. When it boots up, I am presented with the error "WdsClient: An error occurred while communicating with the Windows Deployment Services server. Please check to ensure that the server is operational and that the necessary ports are open on the server's firewall. Server Name [xxxxxxxxxx.domain.local], Server IP: [10.x.x.x]" where xxx's are replaced with the relevant WDS Server name and IP Address.

The odd thing is, when I boot a VMware Guest into PXE boot and load up the VMware boot.wim I made for testing, it works perfectly. No issues. What makes it even more weird, is that I did get it working when I first built the server up.

On the client, I get this from the Setupact.log

2012-09-14 11:27:48, Info       [0x070035] DIAG   CallBack_DiagnosticDataGeneration: Called with notification for Initialization
2012-09-14 11:27:48, Info       [0x07003b] DIAG   CallBack_DiagnosticDataGeneration: Starting Timer as we are starting new phase
2012-09-14 11:27:48, Info       [0x0b0022] WDS    StartNetworking: Trying to start networking.
2012-09-14 11:27:48, Info                  WDS    Network service dhcp not running or could not be queried: 477e80 1 1
2012-09-14 11:27:48, Info                  WDS    Network service lmhosts not running or could not be queried: 477e80 1 1
2012-09-14 11:27:48, Info                  WDS    Network service lanmanworkstation not running or could not be queried: 477e80 1 1
2012-09-14 11:27:48, Info                  WDS    Network service bfe not running or could not be queried: 477e80 1 1
2012-09-14 11:27:48, Info                  WDS    Network service ikeext not running or could not be queried: 477e80 1 1
2012-09-14 11:27:48, Info                  WDS    Network service mpssvc not running or could not be queried: 477e80 1 1
2012-09-14 11:27:59, Info                  WDS    Installing device pci\ven_8086&dev_1502&subsys_162b103c X:\WINDOWS\INF\oem0.inf succeeded
2012-09-14 11:28:00, Info                  WDS    No computer name specified, generating a random name.
2012-09-14 11:28:00, Info                  WDS    Renaming computer to XXXXXXXX.
2012-09-14 11:28:00, Info                  WDS    Acquired profiling mutex
2012-09-14 11:28:00, Info                  WDS    Service winmgmt disable: 0x00000000
2012-09-14 11:28:00, Info                  WDS    Service winmgmt stop: 0x00000000
2012-09-14 11:28:00, Info                  WDS    Service winmgmt enable: 0x00000000
2012-09-14 11:28:00, Info                  WDS    Released profiling mutex
2012-09-14 11:28:00, Info                  WDS    Acquired profiling mutex
2012-09-14 11:28:00, Info                  WDS    Install MS_MSCLIENT: 0x0004a020
2012-09-14 11:28:00, Info                  WDS    Install MS_NETBIOS: 0x0004a020
2012-09-14 11:28:00, Info                  WDS    Install MS_SMB: 0x0004a020
2012-09-14 11:28:00, Info                  WDS    Install MS_TCPIP6: 0x0004a020
2012-09-14 11:28:00, Info                  WDS    Install MS_TCPIP: 0x0004a020
2012-09-14 11:28:00, Info                  WDS    Service dhcp start: 0x00000000
2012-09-14 11:28:00, Info                  WDS    Service lmhosts start: 0x00000000
2012-09-14 11:28:00, Info                  WDS    Service ikeext start: 0x00000000
2012-09-14 11:28:01, Info                  WDS    Service mpssvc start: 0x00000000
2012-09-14 11:28:01, Info                  WDS    Released profiling mutex
2012-09-14 11:28:01, Info                  WDS    Spent 812ms installing network components
2012-09-14 11:28:02, Info                  WDS    Spent 1450ms installing network drivers
2012-09-14 11:28:02, Info                  WDS    QueryAdapterStatus: found operational adapter with DHCP address assigned.
2012-09-14 11:28:02, Info                  WDS    Spent 0ms confirming network initialization; status 0x00000000
2012-09-14 11:28:02, Info                  WDS    GetNetworkingInfo: WpeNetworkStatus returned [0x806]. Flags set: WPE_NETWORK_ADAPTER_OPERATIONAL WPE_NETWORK_DHCP_ENABLED WPE_NETWORK_ADAPTER_HAS_DHCP_ADDRESS 
2012-09-14 11:28:02, Info       [0x0b0023] WDS    StartNetworking: Networking successfully started.
2012-09-14 11:28:02, Info       [0x0a0014] UI     In WDS Mode. Callback for WDS UI happened
2012-09-14 11:28:02, Info       [0x0b006e] WDS    GetServerParamsFromBootPacket: WDS Server information. Server Name [xxxxxxxxxxx.domain.local], Server IP Address [10.x.x.x]
2012-09-14 11:28:02, Info                  WDS    	List of interfaces on client
2012-09-14 11:28:02, Info                  WDS    IP Address [10.x.x.x] MAC Address [12345678901234]
2012-09-14 11:28:02, Info       [0x0b008c] WDS    CClientLibrary::InitializeRpcSession: Binding String=11111111-1111-1111-1111-11111111@ncacn_ip_tcp:10.x.x.x
2012-09-14 11:28:02, Info       [0x0b002e] WDS    InitializeUnattend: There is no unattend file available on the server.
2012-09-14 11:28:02, Error      [0x0b002d] WDS    InitializeUnattend: Error getting unattend from server. Error = [0x80070002][gle=0x00000002]
2012-09-14 11:28:02, Error      [0x0b0065] WDS    CallBack_WdsClient_DetectWdsMode: Failed to create client session or initialize WDS unattend. Error [0x80070002][gle=0x00000002]
2012-09-14 11:28:02, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while communicating with the Windows Deployment Services server. Please check to ensure that the server is operational and that the necessary ports are open on the server's firewall. Server name [xxxxxxxx.domain.local], Server IP address [10.x.x.x].]

Open in new window


I have checked all the obvious things: Turned on PortFast, tried different networks, subnets, cables, ports etc. Tried different DHCP servers,  turning off the Server Firewall, and even rebuilt the whole WDS server up again from scratch. Also tried turning off Task Offloading in the boot.wim and on the server.

I have been looking at this issue for 2 weeks now and literally have no more ideas to try.
0
WotanAU
Asked:
WotanAU
  • 2
1 Solution
 
Nagendra Pratap SinghCommented:
Try this on an older PC. If it works then you just need to add drivers to it.

Your elitebook must be a very new model.
0
 
WotanAUAuthor Commented:
Tried it on another older PC and it worked a treat. It does look like the newer model drivers are not fully compatible with WDS. I will hunt around for some more generic ones from the Chipset manufacturer. Thanks for your help.
0
 
WotanAUAuthor Commented:
Rule #1: Always go back to basics.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now