I have SQL Server Express running on machine GERSWHIN. On GERSHWIN itself, SSMS connects using: GERSWHIN\SQLEXPRESS.
The server is running on port 1344, and from the Internet, I can telnet into GERSHWIN, exposed as, say, abc.com, on port 1344.
From another computer using SSMS, what should be the string to use in the Server name field to connect to this SQL Server?
I tried abc.com:1344 and abc.com:1344\SQLEXPRESS but both got the same error:
Related
i moved my website on a server, it have installed web application and SQL server instance (this site is only for private network), if i try to access sql instance from SSMS it connect without problem, but when i try to access data from my website or SSMS installed on another pc connected to the same network it's says me that instance name is not correct or firewall block sql server ports. Sql connection string is correct, both SQL Server and SQL Browser services are active, named pipes and TCP are enabled, and i've added rules to firewall to allow connection from port 1433 and 1434(this one is for UDP) but i've the same problem, any help?
I have a SQL Server hosted on my local machine that I am trying to connect from my VM. The VM can access the internet and also a python server hosted on my local machine (10.0.2.2:8000 works).
However, when i try to connect Sqlectron to my Local machines SQL Server, I get a connection refused (I put in the host address as 10.0.2.2:1433)
Is there any settings I need to look into?
Open SQL Server Config Manager and enable TCP Connection
I cannot create a simple new SQL Server RDS instance and connect to it. I've provided screenshots of the configurations I have used below:
RDS MS SQL Server Configuration Step 1
Security Group Settings
DB Instance Settings
Error when attempting to connect via SSMS 2017 without port
Error when attempting to connect via SSMS 2017 with port
From the above as I understand it my security group is set up correctly (My IP should be able to connect via SQL Server authentication via port 1433). Without providing a port in SSMS 2017 I get a "Named Pipes Provider" error and when I do provide the 1433 port (testdb.cjkirvd4vbhk.us-west-2.rds.amazonaws.com,1433) I get a timeout error. What am I doing wrong? I just want to be able to create a SQL Server RDS instance and connect to it.
I have a remote Windows Server 2017 with MS SQL Server and I want to connect with it remotely from my machine (but currently I'm unable to).
First of all I want to ask if I get the IP address right (or rather Server Name field in SQL Server prompt in MS SQL Server Management Studio)
mentioned server name field
Let's say IP of the remote server is 135.150.96.96. The instance of the SQL Server on remote server is "TEST". The port is 63011. If I'm one of admins on remote server I assume this server works all the time for all users.
135.150.96.96\TEST,63011
Is this address correct?
I know there are more things to check (services, firewall etc.) that's why I want to be sure I type server name correctly.
I am trying to set up a development testing server, Windows 2008 Server with IIS and SQL Server 2008 Express. The IIS and classic ASP (yeah, supporting antique projects) works fine, including connecting to remote SQL Server 2008 servers, via SQLOLEDB.
However, I fail to connect to the local SQL Server 2008 Express instance. It is installed as an instance (ie, PC-NAME\SQLEXPRESS), and user/pwd authorisation is enabled. I can successfully set up an ODBC entry, so the server works fine. The problem lies in getting the IIS-ASP-SQLOLEDB see the server and connect to it.
Simple connection string, which works on any remote SQL Server 2008 servers, fails at my local express server:
Provider=SQLOLEDB;Data Source=.\SQLEXPRESS;User ID=userName;Password=_pwd_;Database=DbName
The error I get is
SQL Server does not exist or access denied.
The server error log does not contain any trace of unsuccessful login attempt, so I assume there is some problem resolving the data source (because of the instance name?), or the server is somehow inaccessible (protocol, security settings?) from the IIS process.
In SQL Server 2008 express edition it runs on dynamic ports. The solution is just go to properties of the TCP/IP and in the TCP Port just give whatever port you want your SQL Server to listen on.
strConn = "Provider=SQLOLEDB; Network Library=DBMSSOCN; Data Source=.\SQLEXPRESS; Connection Timeout=15;Packet Size=4096; Initial Catalog=DbName; User ID=userName; Password=_pwd_;"
Can you post how you access the connection object via ASP?