Community
EIdSocketError 11001
Links used in this discussion
Links used in this discussion
Allan Hokanson,
User (Posts: 4)
Mar 04, 2019 7:04:07 pm EST
Support level: Free or trial
On my upgrade Windows Server 2016 (Upgraded from 2012) I am unable to connect to the ID server on the internet This is only appearing. I receive the following error messages.
CheckID Connection to internet-id error. Host: "id.remoteutilities.com:5655". Exception class: "EIdSocketError". Message: "Socket Error # 11001
CheckID Connection to internet-id error. Host: "id.remoteutilities.com:443". Exception class: "EIdSocketError". Message: "Socket Error # 11001
Ports are open in my firewall.
I am able to access the ID servers from standalone viewers installed on other computers (Windows 10) from inside my firewall so it is not a Firewall Issue.
There is no longer Antivirus installed on my 2016 server.
The Windows Firewall is disabled for all connection types on my 2016 server.
There was no problem with the viewer when this server was 2012.
I do believe that for the first month or so after upgrading the viewer did work properly.
CheckID Connection to internet-id error. Host: "id.remoteutilities.com:5655". Exception class: "EIdSocketError". Message: "Socket Error # 11001
CheckID Connection to internet-id error. Host: "id.remoteutilities.com:443". Exception class: "EIdSocketError". Message: "Socket Error # 11001
Ports are open in my firewall.
I am able to access the ID servers from standalone viewers installed on other computers (Windows 10) from inside my firewall so it is not a Firewall Issue.
There is no longer Antivirus installed on my 2016 server.
The Windows Firewall is disabled for all connection types on my 2016 server.
There was no problem with the viewer when this server was 2012.
I do believe that for the first month or so after upgrading the viewer did work properly.
Allan Hokanson,
User (Posts: 4)
Mar 04, 2019 8:18:09 pm EST
Support level: Free or trial
I just installed the viewer on another Windows 2016 server and imported the exported connections and all is well. The problem is definitely local to the other Windows Server 2016. I guess I will start over with the new server. However if anyone does have some insight as to where I might need to go to fix the original server I would appreciate it since it is my Remote Desktop Services ALL Roles server.
Conrad Sallian,
Support (Posts: 3074)
Mar 05, 2019 4:49:24 am EST
Hello Allan,
Thank you for your message.
Here is a related KB article https://www.remoteutilities.com/support/kb/socket-error-11001-host-not-found/
Hope that helps.
Thank you for your message.
Here is a related KB article https://www.remoteutilities.com/support/kb/socket-error-11001-host-not-found/
Hope that helps.
* Website time zone: America/New_York (UTC -5)