Hello

I have configured a new Distribution Point which will act as the PXE service point for OSD for clients within a remote office. 

At the moment I have configured boundaries which means that the client I am using as a test, successfully pulls applications from the remote DP. 

The problem occurs when trying to PXE this client to the new DP. When the client boots, I can see the following:

Downloaded WDSNBP from <New Distribution Point IP Address> <New Distribution Point IP Address>
WDSNBP started using DHCP Referral
Contacting server <New Distribution Point IP Address> (Gateway: 0.0.0.0)
No Response from Windows Deployment Services Server - Launching pxeboot.com
Press F12 for Network Service Boot

I have checked on the new DP and the WDS service is running. If I stop the WDS service manually, I get a TFTP time-out message on the client instead of the WDS error which suggests to me that WDS is working in some capacity. 

If I change the DNS settings so that it PXE boots to the general servers it works fine and rebuilds the machine which suggests there are not any issues with the client or the SCCM settings which are site wide. 

Should I be concerned about the gateway being listed as 0.0.0.0?

Checking the PXE log (SMSPXE.log) on the DP, I do get entries which coincide with the client attempting to PXE boot, but this isn't very helpful, nor does it show an actual error, all i get is: 

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16787399" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
AB:CD:EF:1C:8B:97, 4AC88C60-3FE0-1C49-8B97-E03F498679D9: device is in the database.

I have the firewall on the new DP disabled for now so i can confidently rule out the connection being blocked.

Both the client and new DP are on the same subnet. 

I have tried unchecking the PXE option, this seemed to remove WDS and the PXE role, I then rebooted and rechecked the PXE option. 

The error message stayed the same

Has anyone seen / resolved this issue before?

I have seen a number of other posts on various forums regarding this and often the problem is unknown computer support - however, this machine is listed within SCCM as active.

Any help or guidance would be really appreciated. 

Hi,

Have you distributed both x86 an x64 boot images to DP?

For more information, please review the link below:

How to troubleshooting Pxe Service Point for SCCM 2012

http://jackychuasce.blogspot.com/2012/07/how-to-troubleshooting-pxe-service.html

Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

Yes, the DNSis and issue, sounds like a DHCP miss configuration? I assume you go through switches, so are your IP helpers set in place? Have you tried to boot with a media and test if it works?

Thanks for the suggestions....

Yes, boot images are distributed without error. 

I think the DNS issue may be a red herring as the client is on the same sub net as the PXE service point, so should not need a gateway. Also the client does actually receive a response from the server ("no response from windows deployment services", as I said if I stop the WDS service then the error changes to TFTP time-out, so we are reaching the server. 

Referring to the troubleshooting link - a lot of this refers to errors shown in SMSPXE.log - however I do not get any errors listed in there. I have seen entries when it is processing the WIM files successfully and just two lines when the client tries to PXE boot - but no errors at all. 
The settings look OK, although slightly different to the suggested settings, eg. we do not have a password and we do not enable unknown computer support - i am pretty confident this inst the problem as the client is a recognised device within SCCM and we have all our other PXE service points configured with the same settings and they work fine. 

I can see entries within event viewer for Windows Deployment Services, but the only one which shows error is the debug log, the following entries in there time in with the client PXE booting

[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tftpsession.cpp:1636] Expression: , Win32 Error=0x4d3
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tftpsession.cpp:1720] Expression: , Win32 Error=0x4d3
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tftpserver.cpp:1211] Expression: , Win32 Error=0x4d3
[WDSServer/WDSPXE] [base\eco\wds\wdssrv\wdspxe\src\pxeep.cpp:646] Expression: , Win32 Error=0x3e5
[WDSServer/WDSPXE] [base\eco\wds\wdssrv\wdspxe\src\pxeep.cpp:646] Expression: , Win32 Error=0x3e5

Is there a WDS log which may show me more?

Any help would be greatly appreciated as I am running out of ideas

Thanks for your input so far :-)

Anybody got any further with this?

The whole WDS usage is SCCM looks like extremely frail solution that when works, is OK, but when it starts failing then it is a nightmare to fix.

Had PXE DP working fine, then one day it does not do so any more

Same errors in debug log

[WDSServer/WDSPXE] [base\eco\wds\wdssrv\wdspxe\src\pxeep.cpp:646] Expression: , Win32 Error=0x3e5
[WDSServer/WDSPXE/SMSPXE] 00:0C:29:FA:7F:0B, 97A84D56-5070-6C2A-827F-709842FA7F0B: Not serviced.
[WDSServer/WDSPXE] [base\eco\wds\wdssrv\wdspxe\src\pxeep.cpp:646] Expression: , Win32 Error=0x3e5

Tried all that there is around, none making it work again

Seb

Got it back to working only after WDS uninstall (by removing it from DP role - PXE & multicast tabs), server reboot, re-enable RXE & MC which does WDS re-install/config

Still, a long windy way to get something working.