Question Locked

I can connect to my workplace's SQL Server at work, but not at home

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Let me preface by saying that I can connect to the server fine (from the same computer; I use my laptop at work) from the office. At home I can use Remote Desktop to connect to the server itself, but trying to connect just to the SQL Server instance via Management Studio gives me an error stating:

TITLE: Connect to Server
------------------------------

Cannot connect to xxx.xx.xxx.xxx.

------------------------------
ADDITIONAL INFORMATION:

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Anyone know what could be causing this? As I said I'm able to connect to it using the exact same method, on the exact same computer, when I'm inside our office, but not when I'm at home.

4 replies

by skdtech

Different Access permissions for onsite and remote access logins

by wayne62682

The server is hosted externally in a secure facility, not in our office, so I'm thinking it might have some kind of firewall rule to only allow SQL Server connections from the office gateway's IP.

by dumphrey

If the security officer is worth a poop then the acls will be tied to static ip addresses between your office and the server.

Contact an admin to see if they can get you access from home if you really need it.

This discussion is closed to new replies.