|
[NM] this[^] and now it works
I would like to connect to my SQL Server 2005 instance running on my Windows Server 2003 at home from my office. I'v never tried this before, so bear with me...
First, I follow all the instructions here[^]
I then open SSMS an another PC and attempt to connect to my IP, which fails with
"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.
Do I need to do something at my router page to allow access to the server? If so, what?
What else could be wrong??
If it's not broken, fix it until it is
modified 11-Oct-12 17:44pm.
|
|
|
|
|
You'll have to ensure that all the right ports you need are open in the router and make sure that the SQL Server is configured to allow remote connections.
I wasn't, now I am, then I won't be anymore.
|
|
|
|
|
Do keep in mind that there are people out there who are running portscans in their free time. You might find strange things happening in your database if you hook it up to the internet without some precautions;
Set the thing to "Windows Authentication" and turn the SA-account of. There could be a checklist on Google, didn't check that - but you might want to 
Bastard Programmer from Hell 
if you can't read my code, try converting it here[^]
|
|
|
|
|
When your server is behind the router, then it has a "private" IP address, hasn't it? Then things get complicated. You could create a VPN, such that home and office are virtually in the same network (same range of IP addresses), or you have to configure port forwarding on your router. I cannot give details on how to do that...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
