frdbadf
asked on
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,
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,
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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,
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,
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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,
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,
So running that command first enabled your application to run correctly, or no?
ASKER
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.
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.
ASKER
NetCitizens comment was correct but I had addressed what he said. I awarded him points though because the issue has to be addressed.
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.