I have successfully set up a SQL Server Failover Cluster environment on local machine. But when I try to create a SQL Server Failover Cluster on EC2 with FSx. I can only connect my SQL server instance on owner node. Are there any differences to note?
I would like to create on singe-AZ mode.
That's my environment :
EC2 Node1 IP : 10.80.16.101
EC2 Node2 IP : 10.80.16.102
Windows cluster IP : 10.80.16.90
SQL Cluster Server Name : DBServer091
SQL Cluster IP : 10.80.16.91
All firewalls is turned off
Situation:
When the owner node is Node1. I can ping the SQL cluster IP(10.80.16.91) and Server Name(DBServer091) successfully in Node1, but Node2 can't. Also I can only connect the SQL by SSMS on Node1.
When I switch the owner node to Node2. The Node1 ping the ip or Server Name failed.
After searching a lot of information, the problem still has no results.
Can anyone help me to fix this issue?
Related
I am getting the below error when trying to connect to RDS SQL Server database:
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.
Configuration of AWS is as follows:
I have a vpc which has a public subnet and a private subnet. The private subnet has two ec2 instances and both the ec2 instances has the same security group. I am able to connect to rds instance with one ec2 instance but getting the above error when trying to connect with the second ec2 instance. All the resources have the same availability zone.
I have tried below options but not able to resolve the issue:
I have tried adding the IP address of the ec2 instance in the rds server's security group directly but that is not helping.
I have disabled the firewall and anti-virus but it is not making any difference.
I have telnet from the ec2 instance to the rds server on port 1433 and I am not able to connect. So it looks like the issue is with a firewall or security group.
I have checked Network ACLS but we don't have any specific ACL set up. It just has default rules which are not blocking any traffic.
I have double-checked everything (security group, network ACL, DNS name of the server, credentials) but not able to figure this out. Please help me to get this fixed.
So I've been working on this for a few hours now and have made no progress. I know this may be an easy/stupid question, so I apologize in advance for my extreme lack of knowledge here.
I have a MYSQL 5.7 database in which I am trying to push to a MS SQL 2008 database. The MYSQL database is local on my Ubuntu 16.04 machine. I have configured FreeTDS to try and do this.
The issue is the person only gave me these parameters which I believe are incomplete.
Server Address: database\SQLEXPRESS
User Name: DatabaseUser
Password: datapassword
Databasename: DBName
Don't I need an IP address/web address and a port to connect? It seems that the "string\SQLEXPRESS" format is not an actual server address (or may be for people who are on the servers network).
Additionally, since the MS SQL Sever is run on a windows machine, will I need my IP address to be white-listed, or does this depend on how the server was set up?
SQL Server addresses are specified via an IP address or hostname, followed by an (optional) instance name. The point of instance names are to differentiate between different instances of SQL Server on the same machine. Regular, non-Express versions of SQL Server don't have an instance name by default, so you should be able to just specify the server's IP or hostname in the address field:
Server Address: 192.168.0.1
SQL Server Express's instance does have a name by default, SQLEXPRESS. If you know you're connecting to a SQL Server Express instance, then most likely you're looking for
Server Address: 192.168.0.1\SQLEXPRESS
As far as connecting to the server, yes, the server needs to be reachable via TCP/IP from the client, so that presumably depends on your network setup.
You also need to enable remote access to the server. This setting is exposed in Management Studio -> Connect to server -> Right click on server, Properties... -> Connections node -> Remote server connections -> Check "Allow remote connections to this server". You might have to do this from a SQLMS instance on the server.
You also need to make sure that your preferred connection protocol (Shared Memory, Named Pipes, TCP/IP) is enabled. You can do this via Sql Server Configuration Manager, which should be installed on the server. Open it, then SQL Server Network Configuration Node -> Protocols for -> Enable or disable the protocols as desired.
I am tring to set up a db2 server on a Windows 7 machine and I cant connect to database from remote, only from local. I think I might miss some configuration.
1) I turned off the firewall
2) my database information is:
Database 2 entry:
Database alias = SAMPLE
Database name = SAMPLE
Local database directory = C:
Database release level = f.00
Comment =
Directory entry type = Indirect
Catalog database partition number = 0
Alternate server hostname =
Alternate server port number =
Part of the output from netstat -a command is:
TCP [::]:49155 WIN-whatever:0 LISTENING
TCP [::]:49164 WIN-whatever:0 LISTENING
TCP [::]:49165 WIN-whatever:0 LISTENING
TCP [::]:50000 WIN-whatever:0 LISTENING
From the client if I ping my server it does not respond
Also if I scan it with nmap -sV <server_ip_address> it doesn't return me open ports and services which use it
From the client, to connect, I run the following commands:
db2 list node directory
SQL1027N The node directory cannot be found.
catalog tcpip node <i am not sure what does here> remote <server_ip_address> server <port_number>
no output
this implies that something is wrong. I tried couple of things for node and nothing works
I am have no idea what is going on and how to fix it.
Thank you for help
First of all, the fact that you cannot ping the server and nmap doesn't see the open ports means your problem, at least at this point, lies outside DB2. Once you fix your network issues, here's the procedure you can follow to set up remote connectivity to a DB2 database via TCP/IP.
1) Optional. You can use either a service name or a port number to configure the DB2 instance. If you want to use the service name, on the server add a line to /etc/services similar to db2c_db2inst1 50000/tcp, which assigns the service name "db2c_db2inst1" to the port 50000.
2) On the server update the DB2 instance configuration: db2 update dbm cfg using svcename db2c_db2inst1 (or db2 update dbm cfg using svcename 50000 if not using the service name). To verify: db2 get dbm cfg | grep SVCENAME.
3) On the server update the DB2 registry variable: db2set DB2COMM=TCPIP. To verify: db2set DB2COMM.
4) On the server restart the instance: issue db2stop force, then db2start.
5) On the remote client, assuming the DB2 client software is installed, issue db2 catalog tcpip node whatever remote <your server IP address> service <your DB2 port number>. Note that the node name ("whatever" in this example) is limited to 8 ASCII characters.
6) On the remote client issue db2 catalog database <your database name> at node whatever, referring to the node name ("whatever") that you defined in step 5.
7) On the remote client verify connectivity: db2 connect to <your database name> user <user name> using <password>
Try to do a telnet on the instance port to check that everything is right from the client to the server
telnet DB2-Server-name 50000
Where DB2-Server-name is the server name or IP address. Make sure you can get the server.
50000 is the most often DB2 port, but you have to check the configuration.
Once you get connection to the server, you can configure the node with the previous answer.
The target database is located on a LAN with a local IP. The local IPs are distributed by my modem's DHCP server and is something like 192.168.1.xxx. I've already redirected port 1433 to the machine which holds the sql server (192.168.1.xxx) and I can reach to it with a SQL Management Studio connection, using my WAN IP from the source machine. However, when I write my WAN IP as the Copy Database task's target, it returns an error which indicates that connection cannot be established.
Might I be missing the writing convention for the target? I tried the following (my WAN IP is 78.187.xxx.xxx and my target MSSQL Server's name is EXP32):
78.187.xxx.xxx
78.187.xxx.xxx\EXP32
\\78.187.xxx.xxx
\\78.187.xxx.xxx\EXP32
GO TO
-> SQL server configuration manager
-> On network configuration -> protocol for mssqlserver -> enable except VIA
-> go to component services and on services restart sqlserver and express if you have
My SQL server installed on remote computer, that works via proxy server. I know the external IP address, and local network IP of computer. How can I connect?
Follow instructions on MSDN:
Connecting to SQL Server Through a Proxy Server:
How to: Connect to SQL Server Through a Proxy Server (SQL Server Configuration Manager)
If the computer hosting SQL Server is behind a proxy server, and you have no alternate route to that host other than through that proxy server, you're going to have to determine the process necessary to configure the proxy to allow connections from your box to the SQL server...