PXE\WDS server problems

Ask a question

Tuesday, May 01, 2012 4:34 AM

0

I have gone through the steps of removing the BOOT IMAGES from the PXE service point, removing the PXE service point, adding it back and still getting errors with WDS services starting. this is from PXECONTROL.LOG

Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:26:45 PM 4032 (0x0FC0)
Error receiving replies SMS_PXE_SERVICE_POINT 4/30/2012 10:27:00 PM 4032 (0x0FC0)
Pxe test request failed, error code is 16389. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:00 PM 4032 (0x0FC0)
PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:00 PM 4032 (0x0FC0)
Successfully performed availability check against local computer. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:00 PM 4032 (0x0FC0)
Initialization still in progress. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:00 PM 4032 (0x0FC0)
adding address to server list 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:15 PM 4032 (0x0FC0)
adding address to server list 127.00.00.01 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:15 PM 4032 (0x0FC0)
Sending availiability packet to: 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:15 PM 4032 (0x0FC0)
Sent 274 bytes to 010.020.035.220:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:15 PM 4032 (0x0FC0)
Recieved Packet 00C9CE58 does not have associated request. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:15 PM 4032 (0x0FC0)
Error validating replies SMS_PXE_SERVICE_POINT 4/30/2012 10:27:15 PM 4032 (0x0FC0)
Sending availiability packet to: 127.0.0.1 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:15 PM 4032 (0x0FC0)
Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:15 PM 4032 (0x0FC0)
Error receiving replies SMS_PXE_SERVICE_POINT 4/30/2012 10:27:30 PM 4032 (0x0FC0)
Pxe test request failed, error code is 16389. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:30 PM 4032 (0x0FC0)
PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:30 PM 4032 (0x0FC0)
Successfully performed availability check against local computer. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:30 PM 4032 (0x0FC0)
Initialization still in progress. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:30 PM 4032 (0x0FC0)
adding address to server list 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:45 PM 4032 (0x0FC0)
adding address to server list 127.00.00.01 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:45 PM 4032 (0x0FC0)
Sending availiability packet to: 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:45 PM 4032 (0x0FC0)
Sent 274 bytes to 010.020.035.220:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:45 PM 4032 (0x0FC0)
Recieved Packet 00C9D760 does not have associated request. SMS_PXE_SERVICE_POINT 4/30/2012 10:27:45 PM 4032 (0x0FC0)
Error validating replies SMS_PXE_SERVICE_POINT 4/30/2012 10:27:45 PM 4032 (0x0FC0)
Sending availiability packet to: 127.0.0.1 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:45 PM 4032 (0x0FC0)
Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:27:45 PM 4032 (0x0FC0)
Error receiving replies SMS_PXE_SERVICE_POINT 4/30/2012 10:28:00 PM 4032 (0x0FC0)
Pxe test request failed, error code is 16389. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:00 PM 4032 (0x0FC0)
PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:00 PM 4032 (0x0FC0)
Successfully performed availability check against local computer. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:00 PM 4032 (0x0FC0)
Initialization still in progress. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:00 PM 4032 (0x0FC0)
adding address to server list 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:15 PM 4032 (0x0FC0)
adding address to server list 127.00.00.01 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:15 PM 4032 (0x0FC0)
Sending availiability packet to: 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:15 PM 4032 (0x0FC0)
Sent 274 bytes to 010.020.035.220:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:15 PM 4032 (0x0FC0)
Recieved Packet 00C9E068 does not have associated request. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:15 PM 4032 (0x0FC0)
Error validating replies SMS_PXE_SERVICE_POINT 4/30/2012 10:28:15 PM 4032 (0x0FC0)
Sending availiability packet to: 127.0.0.1 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:15 PM 4032 (0x0FC0)
Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:15 PM 4032 (0x0FC0)
Error receiving replies SMS_PXE_SERVICE_POINT 4/30/2012 10:28:30 PM 4032 (0x0FC0)
Pxe test request failed, error code is 16389. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:30 PM 4032 (0x0FC0)
PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:30 PM 4032 (0x0FC0)
Successfully performed availability check against local computer. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:30 PM 4032 (0x0FC0)
Initialization still in progress. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:30 PM 4032 (0x0FC0)
adding address to server list 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:45 PM 4032 (0x0FC0)
adding address to server list 127.00.00.01 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:45 PM 4032 (0x0FC0)
Sending availiability packet to: 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:45 PM 4032 (0x0FC0)
Sent 274 bytes to 010.020.035.220:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:45 PM 4032 (0x0FC0)
Recieved Packet 00C9E970 does not have associated request. SMS_PXE_SERVICE_POINT 4/30/2012 10:28:45 PM 4032 (0x0FC0)
Error validating replies SMS_PXE_SERVICE_POINT 4/30/2012 10:28:45 PM 4032 (0x0FC0)
Sending availiability packet to: 127.0.0.1 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:45 PM 4032 (0x0FC0)
Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:28:45 PM 4032 (0x0FC0)
Error receiving replies SMS_PXE_SERVICE_POINT 4/30/2012 10:29:00 PM 4032 (0x0FC0)
Pxe test request failed, error code is 16389. SMS_PXE_SERVICE_POINT 4/30/2012 10:29:00 PM 4032 (0x0FC0)
PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'. SMS_PXE_SERVICE_POINT 4/30/2012 10:29:00 PM 4032 (0x0FC0)
Successfully performed availability check against local computer. SMS_PXE_SERVICE_POINT 4/30/2012 10:29:00 PM 4032 (0x0FC0)
Initialization still in progress. SMS_PXE_SERVICE_POINT 4/30/2012 10:29:00 PM 4032 (0x0FC0)
adding address to server list 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:29:15 PM 4032 (0x0FC0)
adding address to server list 127.00.00.01 SMS_PXE_SERVICE_POINT 4/30/2012 10:29:15 PM 4032 (0x0FC0)
Sending availiability packet to: 10.20.35.220 SMS_PXE_SERVICE_POINT 4/30/2012 10:29:15 PM 4032 (0x0FC0)
Sent 274 bytes to 010.020.035.220:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:29:15 PM 4032 (0x0FC0)
Recieved Packet 00C9F278 does not have associated request. SMS_PXE_SERVICE_POINT 4/30/2012 10:29:15 PM 4032 (0x0FC0)
Error validating replies SMS_PXE_SERVICE_POINT 4/30/2012 10:29:15 PM 4032 (0x0FC0)
Sending availiability packet to: 127.0.0.1 SMS_PXE_SERVICE_POINT 4/30/2012 10:29:15 PM 4032 (0x0FC0)
Sent 274 bytes to 127.000.000.001:4011 SMS_PXE_SERVICE_POINT 4/30/2012 10:29:15 PM 4032 (0x0FC0)

Getting other errors in the event viewer

BINLSVC"...error reading the netbootSCPBL attribute from the computer object"

Motlegap
- Reply
- Quote

All Replies

Tuesday, May 01, 2012 4:36 AM

0

Also getting "SOURCE: WDSPXE - An error occurred while trying to initialize provider BINLSVC loaded from..."
Motlegap
- Reply
- Quote
Tuesday, May 01, 2012 3:26 PM

0

Try this:

Uninstall PXE Service Point, Uninstall WDS, remove your boot images.

Then Add your boot images into SCCM, Install WDS, Add the PXE Service Point.

Worked for me before when i had issues getting WDS starting.
- Reply
- Quote
Tuesday, May 01, 2012 3:59 PM

0

Which SCCM Sp you are using?
Sharad Singh | My blogs: SharadTech | Twitter: @MrLucknowWale |
- Reply
- Quote
Tuesday, May 01, 2012 4:04 PM

0

I have gone through these steps twice already. Same issues. I notice the WDS service restarts about every 10 minutes
Motlegap
- Reply
- Quote
Tuesday, May 01, 2012 4:08 PM

0

check the following link

http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx
Sharad Singh | My blogs: SharadTech | Twitter: @MrLucknowWale |
- Reply
- Quote
Tuesday, May 01, 2012 4:14 PM

0
Using SCCM 2007 R2 on Win2008 Satndard SP2

Motlegap

Sorry, it's R3
- Edited by Tom Pagel Tuesday, May 01, 2012 4:24 PM
- Reply
- Quote
Tuesday, May 01, 2012 4:25 PM

0

check the following link

http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

Sharad Singh | My blogs: SharadTech | Twitter: @MrLucknowWale |

I've gone through these steps as well....
Motlegap
- Reply
- Quote
Friday, May 11, 2012 8:53 AM

Moderator

0
Hi Motlegap,

Did you configure the WDS after reinstallation? If so, please try to not manually configure or start the WDS service.

Also what about to run the command “WDSUTIL /Initialize-Server [/Server:<Server name>] /RemInst:<Full path> [/Authorize]” to initial the server?

See http://technet.microsoft.com/en-us/library/cc742093(v=ws.10).aspx

Sabrina

TechNet Community Support
- Marked As Answer by Sabrina ShenModerator Thursday, May 31, 2012 2:22 AM
- Reply
- Quote

PXE\WDS server problems

All Replies

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support by product

Other support links

Not an IT pro?