Administrator Guide

Solution: Ensure that the:
1 Device service is running correctly
2 Server service is running correctly
3 Path between the device service and the server service is running correctly (use ping)
4 Subnet and IP ranges are dened correctly (when you are attempting to discover devices by subnet or IP range)
You can also run the DNS_DHCP_Lookup Utility to verify if the WDM server is reachable or not.
Problems with Discovering PXE Devices
Problem: You are having problems with discovering PXE devices.
Solution: Ensure that:
1 port 4011 is open in all routers
2 IP-Helper addresses are dened and pointing to the WDM-Server
3 the PXE devices have re-booted at least one time after being discovered by WDM (before WDM recognizes them as PXE devices, the
PXE devices must be re-booted at least one time after being discovered)
Package Errors
Problem: You are receiving package errors.
Solution: Try the following:
1 Verify the scripting syntax
2 Edit the script (*.rsp) and re-mark out LU command (have target device available)
3 Make use of Network Snier
4 Ensure that the WDM Server IP address has not changed
5 Ensure that the Repository information is correct
6 Ensure that you can manually FTP a le to the Repository
7 Ensure that you can run an unattended install
8 Ensure that the package structure is correct (Folder = *.rsp name = scripts'NUMBER'value)
Wake on LAN Command Does Not Reach Remote
Devices
Problem: The HServer is unable to send the WOL command to the remote devices.
Solution: Enable port forwarding for UDP port 16962.
Peer Assisted Deployment Issues
This sections describes some common issues or questions you may have with respect to Peer Assisted Deployment.
Determining whether the HTTP Application used for PAD is Running and Responding
The HTTP application used for PAD accepts the V99 command that can be sent to a system through the browser. The response to the
V99 command from the HTTP Application would be &00. For example, if the HTTP application is running on a system with the following
URL 10.150.202.101 and it listens on port 9980, the V99 command would be:
http://10.150.202.101:9980/V99
108
Troubleshooting