• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 656
  • Last Modified:

Attach to SQL server via VPN

We have T1 connection using CBeyond.  We use their VPN tool to connect remotely using a VPN connection created in XP network connections.  The server we are connecting to using Terminal Services/Remote Desktop  is not a domain controller but a member of a domain.  We can connect to that server but only if the user is local to the server ie, username, not domain\username.  So far so good since we have been able to use shared resources.

The problem is that we have an applicaton that requries XP SP2.  We tried to install the application at the remote locations by connecting to the VPN thus acquiring an IP address on the remote LAN and access to shared resources however the application needs to use SQL server which is on another server located on the remote LAN.  The SQL server is not installed on the server we are using as the Terminal Services server but on another DC on the same LAN.

Can SQL server be seen as a shared resource or are we doing something wrong in our approach?

thanks,
0
frdbadf
Asked:
frdbadf
  • 6
  • 4
3 Solutions
 
Todd GerbertIT ConsultantCommented:
Your question is a little confusing... you establish a VPN to a remote network, and use that VPN strictly for a remote desktop to a server? Are the remote network and server both yours?

SQL server can accept network connections, and can accept a valid network connection regardless of the source - whether it's from a computer in the same building, a computer attached via VPN, or a Windows Mobile SmartPhone half way around the world.  SQL server isn't going to know, or care, how you're attached to the network.

So long as SQL server is configured to accept a network connection, and any routers or firewalls between you and the SQL server are configured to allow that type of network traffic to pass, it should work.
0
 
frdbadfAuthor Commented:
Tgerbert,

Thanks for the reply.  All servers are at the HQ location.  The branch office is using the VPN connection.  Once the VPN connection is established, the branch computers establish a Terminal session using Remote Desktop.  This works fine except for 1 application that requires XP SP2 (the terminal server is W2K)... with the VPN connection only we can map drives and printers to shared resources on the network however, when we try and install this app on the remote desktops they do not see our SQL server instance.
0
 
Todd GerbertIT ConsultantCommented:
So workstations at the branch office are able to use SMB file sharing and RDP over the VPN, but cannot connect directly to the SQL server?  Sounds like either the SQL server isn't setup to allow network connections, or a firewall/router is setup to only allow certain types of traffic.

On the SQL server you should have a SQL Server Configuration Manager, you'll need TCP/IP enabled.  You'll also need TCP port 1433 to be able to pass through the routers and firewalls unblocked.
Untitled.png
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
frdbadfAuthor Commented:
The question is not abandoned.  We implemented changes to the router for port 1433 over the weekend as specified by tgerbert and checked the SQL configuration as he stated.  The person trying to install the SQL app said it failed last night.  I've asked him to submit to me what app and install instruction so I can try.

Again we VPN in using a VPN connection we created in XP, Control Panel, network connections.  At this point we are able to use other shared resources, ie network drives, printers.
0
 
NetCitizenCommented:
If you are using other than default instance (Ex: ServerName\SQLEXPRESS), you need to open 1434. Also, check if the instance is using port 1433 or another port.
0
 
frdbadfAuthor Commented:
NetCitizen,

I had found reference to UDP port 1433 online and to check the port the instance was using by doing the following:

MS SQL Server Tools -> Configuration Tools -> SQL Server Configuration Manager
Open SQL Server 2005 Network Configuration, under Protocols for the Instance I found TCP/IP which gave me the port for the instance.

Upon opening this port along with UDP 1433 I was able to connect to the instance only by using the IP address\Instance name.

This worked only if we used SQL login, we could not used Windows Authentication.  At this point we are able to install the software, however upon starting the application it says we are not able to find the default profile which I think is app specific.

We are using CBeyond's VPN to authenticate login, never are we asked to login to the domain.  We are able to connect to shared resources ok and now find the SQL server.  I think the VPN we are using is why we can't use Windows Authentication.

Anyone have any thoughts to this.  If no answers I will be closing and awarding the points in a day or two.


thanks,
0
 
Todd GerbertIT ConsultantCommented:
That could be... on one of the VPN client's you can try running the command:

net use \\yourSQLServer\ipc$

before trying to connet to SQL server with windows authentication.  Does that make any difference?
0
 
frdbadfAuthor Commented:
tgerbert,

Thanks for that.  It asked me to login and accepted a Windows login but did not solve the problem yet.

I am researching whether uninstall/reinstall after that command execution will help or not.

thanks,
0
 
Todd GerbertIT ConsultantCommented:
So running that command first enabled your application to run correctly, or no?
0
 
frdbadfAuthor Commented:
No, the command requested and accepted the Windows Authentication but the program still has a problem which may be totally separate from SQL.

The application says it is unable to find the default profile... I am going to try some things to resolve this and/or contact the app's tech dept.

I will keep you posted.
0
 
frdbadfAuthor Commented:
NetCitizens comment was correct but I had addressed what he said.  I awarded him points though because the issue has to be addressed.
0

Featured Post

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now