Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Remote Connection using VPN

Author  Topic 

Dgsonic
Starting Member

5 Posts

Posted - 2011-10-22 : 20:31:10
I have a problem connecting using SQL Studio 2008 R2 to my office SQL Server when I'm at home. I can connect to my SQL Server 2008 and SQL Server 2005 servers from home via SQL Studio but not any of the NEW SQL server 2008 R2 servers. I get the standard error 40 name instance not found. When I take my laptop into the office and connect to my docking station I can connect without any problem to the same servers that fails using VPN. The only difference is that my SQL Server 2008 R2 servers I created a named instance instead of default instance name. Both servers are servername\instancename. I had to do this because Sharepoint 2010 would only work if i use a servername\instancename.

Why does it work in office and not at home via VPN. I looked at all the VPN and Event Logs and no errors. I turn off all the FIREWALLS to test. Created INBOUNDS FOR 1433, 1434, SQLBROWSER.. I've read every article in internet and tried everything.. NOTHING. HELP!!!!!!!

Derek

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-10-23 : 20:39:21
Try connecting from home into the 2008 R2 servers via ServerName,PortNumber.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Dgsonic
Starting Member

5 Posts

Posted - 2011-10-24 : 11:23:28
Can you give me an example. Are you saying something this MYSERVER,1433\INSTANCENAME

quote:
Originally posted by tkizer

Try connecting from home into the 2008 R2 servers via ServerName,PortNumber.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog



Derek
Go to Top of Page

afrika
Master Smack Fu Yak Hacker

2706 Posts

Posted - 2011-10-24 : 12:20:06
Replace SERVER Name

SERVER _IP_Adress,1433

Go to Top of Page

Dgsonic
Starting Member

5 Posts

Posted - 2011-10-24 : 12:36:52
Same Error.... Server Name not found...

quote:
Originally posted by afrika

Replace SERVER Name

SERVER _IP_Adress,1433





Derek
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-10-24 : 14:58:08
Do a telnet test then. Open a cmd window on your home computer, type in:

telnet ServerName 1433

where ServerName is the name of the server you are trying to reach that keeps erroring. Let us know what happens in the telnet test. A blank window is good, an error is not.

Are you sure the problem server is listening on port 1433?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Dgsonic
Starting Member

5 Posts

Posted - 2011-10-24 : 22:07:17
The Telnet got Errors Connecting on all the SQL Server 2008 r2 machines and successful on all the SQL Server 2008 and SQL Server 2005 machines. The difference again is that all the SQL Server 2008 r2 are on Windows 2008 Server using servername\instancename and all the other SQL Server 2008 and SQL Server 2005 machines are on Windows 2003 Service Pack 3 using just Servername to access. Again I've disabled all firewalls onto the the R2 machines. If I remote into the SQL 2005 or 2008 machines and launch SQL Studio, all those machines can connect to the R2 machines from the SQL Studios in the office. When I launch SQL Studio from Laptop VPN only R2 machines fail. If I take my laptop into office and don't touch one thing on laptop it connects to R2 machines with no problem.

I'm thinking there are some DNS or Wins IP tables not loading on VPN network which is preventing those machines from being found on network. Must be something to do with Windows Server 2008.



quote:
Originally posted by tkizer

Do a telnet test then. Open a cmd window on your home computer, type in:

telnet ServerName 1433

where ServerName is the name of the server you are trying to reach that keeps erroring. Let us know what happens in the telnet test. A blank window is good, an error is not.

Are you sure the problem server is listening on port 1433?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog



Derek
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-10-24 : 22:12:46
You'll need to talk with your network administrator. Telnet is the most basic test that we can do, and it is erroring.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Dgsonic
Starting Member

5 Posts

Posted - 2011-10-27 : 16:24:01
I resolved problem for those that have same problem. Under this link http://social.msdn.microsoft.com/Forums/en-GB/sqldataaccess/thread/96042d3d-59ca-42db-8524-5d3188214504 I went into SQL Configuration and made every single PORT 1433. Every Port under properties was blank. I made them all 1433 and now after 4 months it works. In the past I just had to enable the TCP/IP port and that was it, not add 1433 to all the ports under property for IP addresses.

Derek
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-10-27 : 19:31:10
Well it sounds like your system wasn't listening on port 1433, which is why you couldn't connect to it. Next time, try connecting with the listening port which you can find in the SQL Server Error Log at startup time.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-10-27 : 19:31:41
By the way, a named instance will not listen on port 1433 automatically. And it looks like you did install a named instance. Keep that in mind for next time.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -