Share via

Event ID 1536 — PXE Provider Initial Configuration

  • Article

Applies To: Windows Server 2008

After the Windows Deployment Services server role is installed, you must configure the server by using either the Windows Deployment Services MMC snap-in or the /Initialize-Server command-line option. The PXE provider must be configured properly before it can provide client boot services over the network.

Event Details

Product: Windows Operating System
ID: 1536
Source: BINLSVC
Version: 6.0
Symbolic Name: E_BINL_MSG_REFERRAL_SERVER_NOT_FOUND
Message: An error occurred while trying to resolve the referral server name.

MAC address: %1
GUID: %2
Referral Server: %3

Error Information: %4

Resolve

Contact the referral server

Windows Deployment Services must be able to resolve the referral server name.

To resolve this issue, do the following:

  • Ensure that there is network connectivity.

  • Ensure there are boot images on the server

Ensure that there is network connectivity

Note: The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, determine whether the firewall settings and Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that the ping command uses.

To perform these procedures, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To determine whether there is a network connectivity problem:

  1. On the Windows Deployment Services server, open the Command Prompt window.
  2. At the command prompt, run ping <server FQDN>,** **where <server FQDN> is the fully qualified domain name (FQDN) of the domain controller (for example, server1.contoso.com).
  3. Run ping <IP Address>, where <IP Address>  is the IP address of the domain controller.
  4. Note the following:
    • If you can successfully ping the domain controller by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.
    • If you cannot successfully ping the domain controller by IP address, this indicates a possible issue with network connectivity, the firewall configuration, or the IPsec configuration.

If necessary, you can perform the following additional steps to help identify the root cause of the problem:

  • Ping other computers on the network to determine the extent of the connectivity issue.
  • If you can ping other servers but not the domain controller, try to ping the domain controller from another computer. If you cannot ping the domain controller from any computer, first make sure that the domain controller is running. If the domain controller is running, check its network settings.
  • On the local computer, check the TCP/IP settings by doing the following:
    1. Open the Command Prompt window, run ipconfig /all, and then verify that the output is correct.
    2. At the command prompt, run ping localhost to verify that TCP/IP is installed and correctly configured on the local computer. If this command is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with your network adapter.
    3. Run ping <local IP address>. If you can ping the localhost address but not the local address, there may be an issue with the routing table or the network adapter driver.
    4. Run ping <DNS server IP address>.** **If there is more than one DNS server on your network, you should ping each of them in turn. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or possibly a network problem between the computer and the DNS servers.
    5. If the domain controller is on a different subnet, try to ping the default gateway. If you cannot ping the default gateway, this might indicate a problem with the network adapter, the router or gateway device, the cabling, or other connectivity hardware.
  • In Device Manager, check the status of the network adapter. (To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK. )
  • Check the network connectivity indicator lights on the computer and at the hub or router. Check the network cabling.
  • Check the firewall settings by using the Windows Firewall with Advanced Security snap-in.
  • Check the IPsec settings by using the IP Security Policy Management snap-in.

If this does not fix your issue, it is possible that the server does not contain any boot images. In resolve this situation, use the procedure in the following section to verify boot images, add boot images, or both.

Ensure there are boot images on the server

To ensure a boot image exists:

  1. Open the Command Prompt window.
  2. At the command prompt, run wdsutil /get-server /server:<referral server name> /show:images
  3. Verify that at least one boot image is listed.
  4. If there are no boot images listed, add a boot image to the server by running WDSUTIL /Add-Image /ImageFile:<boot image> /ImageType:boot /server:<referral server name> at the command prompt.
  5. If the preceding action returns an error, this indicates that the referral server is not a valid Windows Deployment Services server, and you will need to assign the computer to a different server. To do this, run the following command at the command prompt: WDSUTIL /SetDevice /Device:<name> /ReferralServer:<ServerName>

For more information about adding images and configuring computers, see "How to Perform Common Tasks" at https://go.microsoft.com/fwlink/?LinkId=89223.

Verify

To verify that the server is correctly configured:

  1. Open the Command Prompt window.
  2. At the command prompt, run wdsutil /get-server /show:config.
  3. If the output does not contain any errors, the server is correctly configured.

PXE Provider Initial Configuration

Windows Deployment Services