10-17-2014, 02:05 PM
OK, so it\'s definitely an ETH02. By idle time out, do you mean connection timeout? I\'ve set this to 0. It did get to 76% on the update (cable) first time of trying after that, but again timed out with the error \'unable to write to the transport connection: an existing connection was forc...\'.
Are there any other DS Manager settings that need to change? I have everything as default except the IP is DHCP enabled and now the connection timeout as 0.
Also - I can now ONLY connect to the UCM through comfigurator in update firmware mode with update cable attached. With the cable removed, Comfigurator can no longer connect to the UCM even though DS MAnager can see it.
I don\'t have a UCM USB
Are there any other DS Manager settings that need to change? I have everything as default except the IP is DHCP enabled and now the connection timeout as 0.
Also - I can now ONLY connect to the UCM through comfigurator in update firmware mode with update cable attached. With the cable removed, Comfigurator can no longer connect to the UCM even though DS MAnager can see it.
I don\'t have a UCM USB