Cannot connect to SQL Server 2008 R2 remotely

Question

Cannot connect to SQL Server 2008 R2 remotely

Viewing 5 posts - 31 through 34 (of 34 total)

You must be logged in to reply to this topic. Login to reply

emmanuel.constant Right there with Babe Points: 761 More actions · Answer 1

Luis Cazares (7/31/2012)
In the part where it asks
Which SQL Server do you want to connect to?
Server:
Just put the IP Address and port. Example:
192.168.0.1,1433
If it works, that might be some problem with your DNS.
If it doesn't
Could it be a problem of Windows Server configuration?

Ok, So I would add this to where the ODBC setup and/or the SQL Management Studio UI?

Luis Cazares SSC Guru Points: 183706 More actions · Answer 2

emmanuel.constant (8/1/2012)
Luis Cazares (7/31/2012)
In the part where it asks
Which SQL Server do you want to connect to?
Server:
Just put the IP Address and port. Example:
192.168.0.1,1433
If it works, that might be some problem with your DNS.
If it doesn't
Could it be a problem of Windows Server configuration?
Ok, So I would add this to where the ODBC setup and/or the SQL Management Studio UI?

Both of them, as they are independent from each other. It depends on which one do you need.

Luis C.
General Disclaimer:
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

How to post data/code on a forum to get the best help: Option 1 / Option 2

emmanuel.constant Right there with Babe Points: 761 More actions · Answer 3

Luis Cazares (8/2/2012)
emmanuel.constant (8/1/2012)
Luis Cazares (7/31/2012)
In the part where it asks
Which SQL Server do you want to connect to?
Server:
Just put the IP Address and port. Example:
192.168.0.1,1433
If it works, that might be some problem with your DNS.
If it doesn't
Could it be a problem of Windows Server configuration?
Ok, So I would add this to where the ODBC setup and/or the SQL Management Studio UI?
Both of them, as they are independent from each other. It depends on which one do you need.

I tried both attempts and was not able to log in. Images of errors and entries attached.

Luis Cazares SSC Guru Points: 183706 More actions · Answer 4

That would be a problem with Windows or domain permissions.

Try to connect to that server outside of SQL, if someone else is in charge of that, you should contact him.

Luis C.
General Disclaimer:
Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

How to post data/code on a forum to get the best help: Option 1 / Option 2

Gazareth One Orange Chip Points: 27737 More actions · Answer 5

I'd add that if you're using a named instance, as you seem to be, port 1433 is unlikely to be the correct port.

To elaborate: port 1433 is what the default instance runs on.

You'll need to find out from the admin of the DB server which port your instance is listening on.

Or alternatively, IPNumber\InstanceName will also work in Management Studio, if the SQL Browser service is running on the server.