Problem starting tftpd32/tftpd64 on inactive adapter (Windows)
#1
Posted 26 May 2011 - 08:38 PM
Problem:
Computer has two network adapters installed. I have configured both TFTP and DHCP servers to bind to one of the adapters IP address. If I start the TFTP32/64 service with a network cable connected to the adapter such that the network is active (carrier present), everything works fine. However, if I start the service with the cable disconnected or the connected boot device powered-off (no carrier present), then the TFTP and DHCP servers do not start. Launching the GUI to verify the configuration shows that the TFTP server and DHCP server tabs are missing as though they are not enabled. Open the settings dialog and the DHCP tab shows that the DHCP server configuration is not set (IP poolstarting address is 0.0.0.0, size = 0, etc.). The INI file has the DHCP option set to bind to the inactive adapter IP address, however the other network adapter IP address is displayed/selected. Using netstat -an shows that nothing is listening on the various UDP ports 67 or 69.
It is required that we bind the TFTP and DHCP servers to the one adapter only. Also, it is typical that the boot device connected to the Ethernet adapter on the PC is powered-off during the installation and starting of the TFTP service.
Has anyone else had this problem? Does anyone know of a solution (beyond the obvious workaround of having an active network when starting the service)?
Thanks in advance.
#2
Posted 26 May 2011 - 09:41 PM
Sounds like there is something like that going on here where if the adapter isn't "active", it is being ignored. Isn't there a software setting to over-ride this? Have you looked at all the adapter "settings"???
Sorry nothing specific - Good Luck!
#3
Posted 27 May 2011 - 06:18 PM
Using the non-service version of tftpd32, it reports errors attempting to bind DHCP to the "inactive" adapter.
My guess is there is some error returned by a Windows system call.
It would be nice if there was a retry option if the binding fails.
#4
Posted 28 May 2011 - 03:01 PM
Yes, this sounds a lot like the error condition I mentioned...Thanks for the feedback.
Using the non-service version of tftpd32, it reports errors attempting to bind DHCP to the "inactive" adapter.
My guess is there is some error returned by a Windows system call.
It would be nice if there was a retry option if the binding fails.
And some sort of option to retry over time would be a nice addition in this case. Maybe something for the developer to consider???
#5
Posted 04 July 2011 - 07:50 AM
#6
Posted 19 July 2011 - 03:20 AM
#7
Posted 19 July 2011 - 03:40 AM
Is there a cable (and an active connection) on the adapter? i.e. if there are lights to indicat that the HW layer is up and running, are they ON...Bump... can anyone help?
As stated above, Windows is "finiky" about enabling a piece of HW that it things is not connected - doesn't matter what you think the settings are "set" to.
If worse comes to worse, make yourself a Loopback plug...see this diagram for the RJ-45 - basically
- 1 loops back on to 3
- 2 loops back onto 6
#8
Posted 24 December 2012 - 10:19 AM
Hi,
I am also facing the same issue with two Ethernet ports in my PC. Is there any solution for this?
Kindly let me know.
Thanks.
Regards,
Sathish kumar D
#9
Posted 29 December 2012 - 04:21 PM
It does not make sense to start a network service that tries to bind to an IP address that doesn't exist. If the network connection has its link disconnected, then the IP interface doesn't exist. Some laptops' network adapters actually disappear without a link (you hear the "hardware disconnected" sound). I'd suggest either getting proper server hardware or using a hub or switch to ensure that the laptop's network connection always has a link.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users