J

JohnTwo

Member

Last active 7 months ago

  1. 7 months ago
    Fri Feb 16 15:20:24 2018
    J JohnTwo started the conversation TFTP Timeout on Client (DHCP ok).

    Setup: Windows 7: Clone Deploy Server, Clone Deploy Proxy and TFTPD32 all on one server.

    DHCP working great, client computer gets an i.p. address from TFTD32 DHCP Server. But TFTP just times out.

    On the TFTPD32 logs, I see:

    Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 18:03:73:D6:82:73 [16/02 09:47:53.801]
    Client requested address 0.0.0.0 [16/02 09:47:53.801]
    DHCP: proposed address 192.168.0.20 [16/02 09:47:55.346]
    2932 Request 2 not processed [16/02 09:47:55.346]
    Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 18:03:73:D6:82:73 [16/02 09:47:59.402]
    Previously allocated address 192.168.0.20 acked [16/02 09:47:59.402]
    2932 Request 2 not processed [16/02 09:47:59.402]
    Connection received from 192.168.0.20 on port 2070 [16/02 09:47:59.402]
    Error : connect returns 10051: <A socket operation was attempted to an unreachable network.> [16/02 09:47:59.402]
    Connection received from 192.168.0.20 on port 2071 [16/02 09:48:01.430]
    Error : connect returns 10051: <A socket operation was attempted to an unreachable network.> [16/02 09:48:01.430]
    Connection received from 192.168.0.20 on port 2072 [16/02 09:48:05.439]
    Error : connect returns 10051: <A socket operation was attempted to an unreachable network.> [16/02 09:48:05.439]
    Connection received from 192.168.0.20 on port 2073 [16/02 09:48:11.429]
    Error : connect returns 10051: <A socket operation was attempted to an unreachable network.> [16/02 09:48:11.429]
    Connection received from 192.168.0.20 on port 2074 [16/02 09:48:19.393]
    Error : connect returns 10051: <A socket operation was attempted to an unreachable network.> [16/02 09:48:19.393]

    Any ideas?

    Thanks!

  2. Fri Feb 16 15:16:49 2018

    I find the documentation is missing many steps and convoluted. Example:

    Such as the Clone Deploy Proxy Server:

    PC PXE Operation When Installed On Same Server as DHCP

    This method does not require any additional IP Helpers because there should already be one pointing to the DHCP server.

    If installing on an existing DHCP server, port 67 is already in use and the proxy cannot bind to respond to discover requests. You must set listen-dhcp to false in CloneDeploy Proxy DHCP and set option 60 to PXEClient on the DHCP server.

    Ok....you must set listen-dhcp to false in CloneDeploy Proxy DHCP (this is documented on the CloneDeploy Proxy DHCP setup document) and set option 60 to PXEClient on the DHCP server.

    Since you suggest we use TFTP32D's DHCP server, why not include how to set it in the .ini file on the same paragraph above?

    I had to go digging around in ANOTHER forum to find the exact wording to set option 60 the .ini TFTP32D's DHCP Server.

    Someone really needs to make a step by step documentation from start to finish using ONE SET of software: Windows with TFTPD32 and Clone Deploy Proxy.

    Instead of the current state which is: You can use own DHCP server, and you SHOULD use Clone Deploy Proxy, but you need to set this in your own DHCP server because you are using it on the same server. I have like 4 tabs open for 3 different software's. Put it all on ONE PAGE with step by step instructions.

  3. Fri Feb 16 14:50:41 2018
    J JohnTwo joined the forum.