Event ID 1036 — WDSServer Network Availability

Updated: November 21, 2007

Applies To: Windows Server 2008

red

Network connectivity makes communication possible among the WDSServer service, client computers, and Active Directory directory services. Without this communication, the WDSServer service cannot deploy images to client computers. 

Event Details

Product: Windows Operating System
ID: 1036
Source: WDSServer
Version: 6.0
Symbolic Name: E_WDSSERVER_RPC_SEND_FAILED
Message: An error occurred while trying to send reply to the client. Details of request are given below. The binary data contains the first 32 bytes of reply that was sent to the client.

Local Endpoint: %1
Client: %2

This request was processed by %3 provider.

Error Information: %4

Resolve

Check the network configuration

Important: This warning condition may indicate only a temporary communication issue. Before troubleshooting this issue, you should use the steps listed in the Verify section to confirm that the issue still occurs and that you cannot reconnect to an existing session.

To resolve the issue, use the procedures in this topic to ensure that the server has network connectivity.

Note: The following procedures include steps for using the ping command to troubleshoot WDSServer network availability problems. Therefore, before performing these steps, determine whether the firewall settings or Internet Protocol security (IPsec) settings on your network permit Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.

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, type ping <server FQDN>, where <server FQDN> is the fully qualified domain name (FQDN) of the domain controller (for example, server1.contoso.com).
  3. At the command prompt, type ping <IP Address>, where <IP Address>  is the IP address of the domain controller.

Note: 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, firewall configuration, or 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 ensure that the domain controller is running. If the domain controller is running, check its network settings.
  • Check the TCP/IP settings on the local computer by using the following procedure:
    1. Open the Command Prompt window, run the ipconfig /all command, and then check the output to make sure that it is correct.
    2. Run the ping localhost command to verify 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 the ping <local IP address> command. 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 the ping <DNS server IP address> command. If there is more than one DNS server on your network, you should ping each one in turn. If you cannot ping the DNS servers, this indicates a potential problem either with the DNS servers themselves or with the network 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.

Verify

You can verify network connectivity either from a client computer or from the server by using one of the following two procedures.

To verify that the server has connectivity (from a client computer):

  1. Open the Command Prompt window. (Click Start, point to All Programs, click Accessories, and then click Command Prompt.)
  2. At the command prompt, type ping <IP address|fully qualified domain name> to contact the Windows Deployment Services server.
  3. Try to boot the client computer by doing a Pre-Boot Execution Environment (PXE) boot. Make sure that the boot menu and image selection pages are displayed.

To verify that the server has connectivity (from the Windows Deployment Services server):

  1. Open the Command Prompt window. (Click Start, point to All Programs, click Accessories, and then click Command Prompt.)
  2. At the command prompt, type ping <IP address|fully qualified domain name> to contact a remote computer.

Related Management Information

WDSServer Network Availability

Windows Deployment Services

Community Additions

ADD
Show: