• Connection timed out (0x4c126035) Connecting to vDisk on Citrix Provisioning Services Server

    August 15, 2011

    PVS

    In Citrix Provisioning Services 5.6 SP1, when setting a new device to boot from vDisk using XenServer 5.6 SP2, the following error was received (Figure 1):

    Could not boot from filename “ardpb32.bin”: Connection timed out (0x4c126035)

    Figure 1

    Performing a search via an Internet search engine returned various solutions for older versions of XenServer and also recommendations to disable all TCP Offloading in the master image the vDisk is created from.  TCP Offloading had already been disabled in the master image.  Another suggestion was to verify that DHCP Option 60 was not set.  I verified that Option 60 was not set (Figure 2).

    Figure 2

    Now that the Internet has been used for help, time to turn to checking the obvious.  Citrix Provisioning Services uses TFTP and this runs as a service.  Is the TFTP service running?  Look at Figure 3.

    Figure 3

    Somehow the TFTP Service was stopped.  There is nothing in either the Application or System event logs to indicate why the service either stopped or didn’t start when the PVS Server was powered on.  Starting the TFTP Service and then restarting the Virtual Machine that is receiving the streamed vDisk fixed the error (Figure 4).

    Figure 4
    ,





    About Carl Webster

    Webster is a Sr. Solutions Architect for Choice Solutions, LLC and specializes in Citrix, Active Directory and Technical Documentation. Webster has been working with Citrix products for many years starting with Multi-User OS/2 in 1990.

    View all posts by Carl Webster

    7 Responses to “Connection timed out (0x4c126035) Connecting to vDisk on Citrix Provisioning Services Server”

    1. PVSAdmin Says:

      We encountered the same error despite we have the TFTP/PXE services running on the PVS server.

      Client boots from network to DHCP, able to get PXE but when while getting the ARDBP32.BIN file it failing with timeouts.

      Any further thoughts?

      Reply

    2. Adam Says:

      in my case I have 2 PVS Servers with NetScaler “load balance” TFTP VIP and I found that I forgot to check the source ip box. it’s all working now. Thanks for this post.

      Reply

      • Gonzalo Abarza Says:

        Adam,

        In my case i found that i forgot to check the “Use Client IP” in the “Load balance Group”

        Thanks!

        Reply

    3. Graham Says:

      Hi Carl,

      “Me too” on PvS 6.0.1 on XenServer 6.0.2. The only message was one at boot time saying the service started. I’ve set the service to restart on failure see if that helps.

      Graham

      Reply

    Leave a Reply to Graham