I am trying to connect to a MySQL remote server. I was able to connect prior to moving my internet service to Suddenlink.
I am now getting the error:
2003 - Can't connect to MySQL server on 'www.server.com' (10038)
I have added my new IP address to Remote MySQL.
Any suggestions as to what may be going on?
Thanks!
Related
I have installed the "Informix Developer Edition 14.10.FC9 Windows" database on my local windows 10 machine.
I like to connect with the sql client DBeaver (22.3) to the database 'test'.
I know the server, the username, the password and the database name. See the following screenshot:
If i test the connection i get the following error:
Socket connection to server (ol_informix1410#localhost:1526) failed. Check your server is reachable from this client on the host:port specified.
Connection refused: connect
Do I really have the wrong port and if so how do I find out the correct port?
I am trying to connect my ASP.NET Core application to a remote SQL Server.
The application is deployed using IIS WScore 2016 image. When I run the application on my host, it's working, but in the container using this connection string :
Data Source=xx.xxx.xx.xx,1433;Initial Catalog=somedb;User Id=xxxxxx;Password=xxxxx;
or:
Server=xx.xx.xx.xx,PORT_NB;Database=DATABASE;User Id=USER;Password=PASSWORD
But no luck - I am using the default Docker network.
The error is like this:
Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.)
Notes:
The server is allowing the remote connection
All the connection strings are tested and can connect to the remote SQL Server from the application that runs on the host
I have read the Docker documentation and they mentioned the IP forwarding but the example was on linux containers and I did not find any help about connecting the Windows containers to a remote SQL Server
Question
My concrete question is how to expose the container to the outside world and I can connection my container to the other remote services like a remote SQL Server?
Should I use host network or bridge with the IP forwarding?
Any help? Thanks
I changed the connection string to this :
"ConnectionString": "Server=xx.xxx.xx.xx\\MSSQLSERVER,1433;Initial Catalog=Dbname;User Id=username;Password=xxxxxxx;"
then i restarted the AppPoll and it worked
What is the current network you're using for this container? If you used the default network, then you're using Network Address Translation (NAT). What that means is that you're using the host IP address to connect to the external network. So, your problem most likely is that the SQL Server is rejecting the connection from the IP of the container host.
The alternative on Windows is to use a different network drive. There are many options and I'd recommend you look at the option that better suits your needs: https://cda.ms/4nP
I had the same error, try removing the port from the connection string as follows:
"ConnectionString": "Server=ContainerName;Initial Catalog=Dbname;User Id=username;Password=xxxxxxx;"
I have installed Firebird 3.0.1 on a PC and on a VM client. I installed Flamerobin on both to test the connection.
I can connect to localhost on both PC and VM using Flamerobin, so I assume the Firebird server is running on both and Flamerobin is installed on both OK
I can connect to the Firebird server on the VM from the PC and open a database Ok
From the VM I can open a database on the PC, but when I try to retrieve the server version on the PC I get an error ISC_Service_attach failed (Unable to complete network request to host).
I have no idea what the problem is given that I can open a database ok, but cannot access any of the utility services.
I am using fbclient.dll 3.0.1.32591 on both VM and PC
If you can achieve network request to server, you need to check firewall setings on server and set fb default port as inbound acceptable. If you would had same problem after that, than you probably need proper fbclient library, for FB3 on client, VM. Hope this helps.
I'm evaluating TeamCity 9.0.4 and using HSQLDB.
Now trying to setup MS SQL Server 2014 as External Database.I don't have a named instance(NULL).
So I tried the following connection URL
connectionUrl=jdbc:sqlserver://<host>:1433;databaseName=<database name>
connectionProperties.user=<user>
connectionProperties.password=<password>
When I trying to load the build server I'm getting this message.
TeamCity is starting
Continuing attempts to connect to the database
TeamCity server is connecting to MSSQL database. The database server
is not started yet, or the connection properties are not properly set.
And also I checked the log file, this is what I got.
[2015-05-20 14:08:34,513] INFO - jetbrains.buildServer.STARTUP -
Current stage: Continuing attempts to connect to the database
SQLSERVER is up,I think there is a problem with connection URL.
What can I do to solve this.
TeamCity 9.x Documentation Setting up an External Database
Thanks DevOps.
My mistake, I was testing TeamCity locally.
Problem was with the SQL Server Network Connection.
TCP/IP was disabled for SQLEXPRESS
Enable TCP/IP for SQLEXPRESS
Open SQL Server Configuration Manager
Go to Protocols for SQLEXPRESS under SQL Server Network
Configuration.
Right-click on TCP/IP and choose Properties. Set Enabled = YES.
Better check this too, click on IP Addresses tab and find the section
IP All. Set TCP Port to 1433.
I am using Mac book and having client and server running on same machine. Server opens socket whenever it has to send command to Client. Problem is Client opens socket at startup but whenever server opens on . Ip adress is different. I would like to know if i create tunnel between these 2 sockets. Right now, while in server i am getting "Connection refused" error.
Any help is appreciated.
Thanks
Just use 127.0.0.1 loopback address for testing your initial socket code. Server bind()s and listen()s on some known port, client connect()s to it. Once you figure out that setup you can move on to routing between real addresses.