A customers machine did the windows 10 build 1066 update last night. Now I have a connection error 1100. I can ping the ip. The ports are open in the firewall. I cannot connect with edbManager either. Anyone else?

Ivan,

<< A customers machine did the windows 10 build 1066 update last night. Now I have a connection error 1100. I can ping the ip. The ports are open in the firewall. I cannot connect with edbManager either. Anyone else?
>>

What happens if you (temporarily) disable the firewall on the client machine ?  Does it start working ?  If so, then you've still got a firewall issue.

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Oddly enough it seems to be somewhat resolved. A tmp work around was to stop the service, and run edbsrvr.exe from the task bar. Which worked. The next day, I stopped/closed the edbsrvr on the task bar. And started the edb service. Client can magically connect once again.

The only left over oddity is that the edb manager (or my windows app) cannot connect on the server PC via 127.0.0.1, but gladly connects using it's assigned ip. I've never seen that happen before, but I can live with it.

Ivan

On 4/16/2017 11:37 AM, Ivan Sine wrote:
> The only left over oddity is that the edb manager (or my windows app) cannot connect on the server PC via 127.0.0.1, but gladly connects using it's assigned ip. I've never seen that happen before, but I can live with it.

Make sure your server is still listening on all IP's (i.e. 0.0.0.0) and
not just on the actual assigned IP.

Raul