Sven
Apr 6, 2020 9:39:18 AM

WinSQL SQLSTATE=08001

Hello Forum,

can someone help about this error?

The error is only in the Home-Office not in the Office.

SQL30081N  Kommunikationsfehler. Verwendetes Kommunikationsprotokoll: "TCP/IP".  Verwendete Kommunikations-API: "SOCKETS".  Position, an der der Fehler erkannt wurde: "192.168.0.x".  Übertragungsfunktion, die den Fehler festgestellt hat: "send".  Protokollspezifische(r) Fehlercode(s): "10054", "*", "0".  SQLSTATE=08001

Regards

Sven



Synametrics support engineer
Apr 6, 2020 10:14:17 AM

WinSQL SQLSTATE=08001

Sven,

This is a network related issue. You're trying to connect to 192.168.0.x , which refers to a different machine when you're in your office. That IP address does not refer to the same machine when you're in your home-office. Are you using a VPN?

I'd recommend you contact the network adminstrators in your company and ask them what is the correct IP. In addition to the correct IP, you will also need the tcp/ip ports open from your home.



Anonymous
Apr 8, 2020 7:32:33 AM

WinSQL SQLSTATE=08001

HEllo Support,

 

thanks for the feedback. And yes we use ipsec vpn.

We use the same ip from home and from office. The

only difference is from other networks Office-Net and Home-Net.

Maybe it is an firewall problem? As I said it works but I have to make in the program reconnect.

 

Regards

Sven

 

 



Synametrics support engineer
Apr 8, 2020 9:36:38 AM

WinSQL SQLSTATE=08001

If the firewall/VPN disconnects intermitently, it will also disconnect the TCP/IP connection between WinSQL and your database. In that case you will have to reconnect again.

WinSQL can detect a broken connection when you run SQL queries. It should automatically try to reconnect, provided your VPN connect is not broken.

Navigation

Social Media

Powered by 10MinutesWeb.com