PXE: TFTP open timedout

  1. 3 months ago

    Hi All, we used SCCM for deployments and as we aren't upgrading the SCCM license (2016), I wanted to try my hands on Clonedeploy. I was successfully able to install the software and everything went smoothly. However, when PXE booting, I'm getting an error "TFTP open timedout". We have our Windows DHCP server and I have already defined the 66 and 67 options. Below is the error from logs.
    Connection received from 10.30.2.93 on port 2070 [10/07 08:55:11.173]
    Read request for file <pxeboot.0>. Mode octet [10/07 08:55:11.173]
    OACK: <tsize=25358,> [10/07 08:55:11.173]
    Using local port 63417 [10/07 08:55:11.173]
    File <pxeboot.0> : error 10054 in system call recv An existing connection was forcibly closed by the remote host. [10/07 08:55:11.173]
    Connection received from 10.30.2.93 on port 2071 [10/07 08:55:13.189]
    Read request for file <pxeboot.0>. Mode octet [10/07 08:55:13.189]
    OACK: <tsize=25358,> [10/07 08:55:13.189]
    Using local port 63418 [10/07 08:55:13.189]
    File <pxeboot.0> : error 10054 in system call recv An existing connection was forcibly closed by the remote host. [10/07 08:55:13.189]
    Connection received from 10.30.2.93 on port 2072 [10/07 08:55:17.189]
    Read request for file <pxeboot.0>. Mode octet [10/07 08:55:17.189]
    OACK: <tsize=25358,> [10/07 08:55:17.189]
    Using local port 51427 [10/07 08:55:17.189]
    File <pxeboot.0> : error 10054 in system call recv An existing connection was forcibly closed by the remote host. [10/07 08:55:17.189]
    Connection received from 10.30.2.93 on port 2073 [10/07 08:55:23.174]
    Read request for file <pxeboot.0>. Mode octet [10/07 08:55:23.174]
    OACK: <tsize=25358,> [10/07 08:55:23.174]
    Using local port 51428 [10/07 08:55:23.174]
    File <pxeboot.0> : error 10054 in system call recv An existing connection was forcibly closed by the remote host. [10/07 08:55:23.174]

    Can someone please help?

  2. clonedeploy

    Jul 10 Administrator

    Have you tried disabling the firewall?

  3. Thanks all for your replies. It seems to be working now. It had to be an issue with a specific laptop.

 

or Sign Up to reply!