+ Post New Thread
Results 1 to 2 of 2
O/S Deployment Thread, Newbie : PXE:E55 ProxyDHCP service did not reply to request on Port 4011 in Technical; ...
  1. #1

    Join Date
    Mar 2013
    Posts
    2
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Newbie : PXE:E55 ProxyDHCP service did not reply to request on Port 4011

    Hello All, Please try to help me with the following. Thanks.
    ISSUE:
    In a specific Adsite PC’s are unable to PXE-boot from the network after pressing F12. It appears to contact DHCP, and finally fails 10 minutes later with : “PXE:E55 ProxyDHCP service did not reply to request on Port 4011”

    SYSTEMS INVOLVED:
    SCCM 2007 R3
    PC : Virtual PC on an XP PC
    WDS : Server 2008 R2
    VLAN : Only 1 subnet
    HP Switches

    NOTES:
    * PC, WDS, DHCP in same subnet but seperate systems
    * WDS not configured (as recommended)
    * No options configured on DHCP (eg.60, 67 etc.)
    * HP Switches
    * Same error also on Physical PC's
    * I have done all expected troubleshooting steps like restart server, re-install WDS, PXE, x86/x64 Boot packges replicated on PXE and DP
    * The Network team reports no issues. If this is indeed a network issue, how can I convince them?
    LOGS ETC.
    ------------
    (a) Wireshark Details
    * Captured for about 30 seconds after F12
    * Labels
    - 10.1.1.1 Gateway
    - 10.1.1.2 DHCP
    - 10.1.1.3 WDS
    - 10.1.1.4 VirtualPC (running on an XP PC in same subnet)

    Client Captures :
    -----------------
    * Wireshark active on XP PC on which the VirtualPC is to be imaged
    * Capture Filter = "ether host <Microsof_a1:b2:c3> or host 255.255.255.255"
    No. Time Source Sport Destination DPort Protocol Info
    1 0 0.0.0.0 68 255.255.255.255 67 DHCP DHCP Discover - Transaction ID 0xd7f746
    2 0.021991 10.1.1.2 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0xd7f746
    3 0.033015 10.1.1.1 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0xd7f746
    4 0.03338 10.1.1.1 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0xd7f746
    5 4.020094 0.0.0.0 68 255.255.255.255 67 DHCP DHCP Request - Transaction ID 0xd7f746
    6 4.033852 10.1.1.2 67 255.255.255.255 68 DHCP DHCP ACK - Transaction ID 0xd7f746
    7 4.034699 Microsof_a1:b2:c3 Broadcast ARP Who has 10.1.1.3? Tell 10.1.1.4
    8 4.04192 10.1.1.1 67 255.255.255.255 68 DHCP DHCP ACK - Transaction ID 0xd7f746
    9 4.055626 xxxxxx_d1:e2:f3 Microsof_a1:b2:c3 ARP 10.1.1.3 is at xx:xx:xx:d1:e2:f3
    10 4.055976 10.1.1.4 68 10.1.1.3 4011 DHCP DHCP Request - Transaction ID 0xd7f746
    11 4.074769 Microsof_a1:b2:c3 xxxxxx_d1:f2:f3 ARP 10.1.1.4 is at Microsof_a1:b2:c3
    12 8.038492 10.1.1.4 68 0.0.0.0 4011 DHCP DHCP Request - Transaction ID 0xd7f746
    13 12.101602 10.1.1.4 68 10.1.1.3 67 DHCP DHCP Release - Transaction ID 0xd7f746
    14 12.101927 0.0.0.0 68 255.255.255.255 67 DHCP DHCP Request - Transaction ID 0xd7f746
    15 12.153739 10.1.1.2 67 255.255.255.255 68 DHCP DHCP ACK - Transaction ID 0xd7f746
    16 12.162067 10.1.1.1 67 255.255.255.255 68 DHCP DHCP ACK - Transaction ID 0xd7f746
    17 12.358486 10.1.1.4 68 0.0.0.0 4011 DHCP DHCP Request - Transaction ID 0xd7f746
    18 16.224459 10.1.1.4 68 0.0.0.0 4011 DHCP DHCP Request - Transaction ID 0xd7f746
    19 20.232096 10.1.1.4 68 10.1.1.3 67 DHCP DHCP Release - Transaction ID 0xd7f746
    20 20.232445 0.0.0.0 68 255.255.255.255 67 DHCP DHCP Discover - Transaction ID 0x1d7f746
    21 20.263569 10.1.1.2 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0x1d7f746
    22 20.272424 10.1.1.1 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0x1d7f746
    23 20.272784 10.1.1.1 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0x1d7f746
    24 28.253207 0.0.0.0 68 255.255.255.255 67 DHCP DHCP Request - Transaction ID 0x1d7f746
    25 28.286415 10.1.1.2 67 255.255.255.255 68 DHCP DHCP ACK - Transaction ID 0x1d7f746
    26 28.286581 10.1.1.4 68 10.1.1.3 4011 DHCP DHCP Request - Transaction ID 0x1d7f746
    27 28.286819 10.1.1.1 67 255.255.255.255 68 DHCP DHCP ACK - Transaction ID 0x1d7f746


    WDS Server Captures :
    ---------------------
    * Capture filer = "port 67 or port 68 or port 69 or port 4011"
    * packet 8 below mentions error in Wireshark : header checksum incorrect : 0x0; should be ... (I hear this can be ignored)

    No. Time Source SPort Destination DPort Protocol Info
    1 10.984442 10.1.1.1 67 10.1.1.3 67 DHCP DHCP Discover - Transaction ID 0xd7f746
    2 10.986126 10.1.1.3 67 10.1.1.1 67 DHCP DHCP Offer - Transaction ID 0xd7f746
    3 10.989614 10.1.1.1 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0xd7f746
    4 10.99051 10.1.1.1 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0xd7f746
    5 14.996137 10.1.1.1 67 10.1.1.3 67 DHCP DHCP Request - Transaction ID 0xd7f746
    6 15.001967 10.1.1.1 67 255.255.255.255 68 DHCP DHCP ACK - Transaction ID 0xd7f746
    7 15.034113 10.1.1.4 68 10.1.1.3 4011 DHCP DHCP Request - Transaction ID 0xd7f746
    8 15.058217 10.1.1.3 4011 10.1.1.4 68 DHCP DHCP ACK - Transaction ID 0xd7f746
    9 19.009247 10.1.1.4 68 0.0.0.0 4011 DHCP DHCP Request - Transaction ID 0xd7f746
    10 23.109825 10.1.1.1 67 10.1.1.3 67 DHCP DHCP Request - Transaction ID 0xd7f746
    11 23.121994 10.1.1.1 67 255.255.255.255 68 DHCP DHCP ACK - Transaction ID 0xd7f746
    12 23.321528 10.1.1.4 68 0.0.0.0 4011 DHCP DHCP Request - Transaction ID 0xd7f746
    13 27.18608 10.1.1.4 68 0.0.0.0 4011 DHCP DHCP Request - Transaction ID 0xd7f746
    14 31.226225 10.1.1.1 67 10.1.1.3 67 DHCP DHCP Discover - Transaction ID 0x1d7f746
    15 31.227854 10.1.1.3 67 10.1.1.1 67 DHCP DHCP Offer - Transaction ID 0x1d7f746
    16 31.230974 10.1.1.1 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0x1d7f746
    17 31.231868 10.1.1.1 67 255.255.255.255 68 DHCP DHCP Offer - Transaction ID 0x1d7f746
    18 39.230293 10.1.1.1 67 10.1.1.3 67 DHCP DHCP Request - Transaction ID 0x1d7f746
    19 39.234294 10.1.1.1 67 255.255.255.255 68 DHCP DHCP ACK - Transaction ID 0x1d7f746
    20 39.248309 10.1.1.4 68 10.1.1.3 4011 DHCP DHCP Request - Transaction ID 0x1d7f746
    21 39.249824 10.1.1.3 4011 10.1.1.4 68 DHCP DHCP ACK - Transaction ID 0x1d7f746

    ---------------------------
    * From the above, it seems the UDP packet from WDS:4011 does not reach VirtualPC:68. After which the PC releases IP and the process loops.
    * smspxe.log when WDS tries to reply with wdsnbp.com from UDP-4011 to UDP-68
    ============> DHCPREQUEST Reply to client ([010.001.001.004:68]) Len:339 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    DHCP message: smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Operation : BootReply (2) smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Hardware Address type : 1 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Hardware Address Length: 6 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Hop Count : 0 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Transaction ID : 46F7D704 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Seconds Since Boot : 64 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Client IP Address : 010.001.001.004 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Your IP Address : 000.000.000.000 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Server IP Address : 010.001.001.003 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Relay Agent IP Address : 000.000.000.000 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Hardware Address : xx:x:xx:a1:b2:c3: smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    BootFileName "smsboot\x86\wdsnbp.com" smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Magic Cookie: 64565733 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Options: smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Type = 53 DHCP Message Type: 5=DHCPAck smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Type = 54 Server idenitifier: 010.001.001.003 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Type = 97 UUID: xxxxx445ere87e68945678b8d2f4e12a4sdf smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Type = 60 ClassIdentifier: PXEClient smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    Type = 250 0201010504000007a903020014040200ba0626506c65617365 20776169742e20534d53206973206c6f6f6b696e6720666f72 20706f6c696379 smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    <============ DHCPREQUEST Reply (end) smspxe 3/16/2013 12:06:54 AM 7780 (0x1E64)
    [010.001.001.003:67] Recv From:[010.001.001.001:67] Len:348 1533af0 smspxe 3/16/2013 12:09:02 AM 8836 (0x2284)
    ============> Received from client: smspxe 3/16/2013 12:09:02 AM 8836 (0x2284)
    DHCP message: smspxe 3/16/2013 12:09:02 AM 8836 (0x2284)
    Operation : BootRequest (1) smspxe 3/16/2013 12:09:02 AM 8836 (0x2284)
    Hardware Address type : 1 smspxe 3/16/2013 12:09:02 AM 8836 (0x2284)

    (b) Test with PortQry.exe (v2)
    * portqry.exe -n 10.20.30.40 -e 68 -p udp -sp 4011
    * I understand portqry sends a dummy packet to host (-n) at port (-e) from port(-sp) using protocol (-p)
    * 10.20.30.40 is a random PC in some other Adsite
    * Wireshark captures packets at 10.20.30.40;
    * no capture filter; display filter set to ip.addr == "WDS" or "RandomXP" or "randomServer"
    * portqry executed on :
    - WDS - 10.1.1.3 : No packets were received by 10.20.30.40
    - a random XP PC in same subnet of WDS : No packets were received by 10.20.30.40
    - a random server from ANOTHER Adsite : Packet received fine.
    * If I change the portqry.exe protocol from udp to tcp, then packet is received fine from all WDS/XP/Server above.

    Please let me know what further information is required. Thanks.

  2. #2

    Join Date
    Mar 2013
    Posts
    2
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    It turned out to be a switch port configuration issue. The network team mentioned that the WDS server was connected to a 'User' port instead of a 'server' port. (Whatever that means !!)
    That solved it.



SHARE:
+ Post New Thread

Similar Threads

  1. [MDT] Was working, now getting PXE-E55 ProxyDHCP service did not reply
    By stanwell in forum O/S Deployment
    Replies: 3
    Last Post: 20th September 2012, 01:04 PM
  2. Terminal Services (Server not Found)
    By Sunderwood in forum Windows Server 2000/2003
    Replies: 11
    Last Post: 31st March 2009, 07:19 AM
  3. Wireless networks speeds i did not know this...?
    By Uraken in forum Wireless Networks
    Replies: 3
    Last Post: 26th February 2008, 08:43 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •