April 14, 2009 at 9:54 am
Hi all,
I’m trying to find out if it is possible to connect to the client’s database from my local pc(while connected on client’s vpn) from the local SQL Server management studio on my pc. Is it sufficient if the ODBC is created?
Or is there a specific client we can use to connect to the client’s database from local Management studio? Currently, we connect to client’s vpn and log onto their server to access their sql server database.
Thanks for any help.
April 14, 2009 at 10:11 am
Try pinging the client's ip if you can get there, you can connect to their DB provided the client's server is listening on default port or else you might need to configure alias for you client DB server on your local machine.
To create an alias go to sql server configuration manager-- sql server native client configuration--aliases
April 14, 2009 at 10:24 am
Thanks Bobby. Is there a way to find out the port??
Also, when I connect from my local pc, it will have my windows login. When I connect to client's vpn and start management studio, will it still connect?
Thanks a lot
April 14, 2009 at 11:06 am
Are you using Windows Authentication to connect to SQL Server? When you connect to the server, are you using a client specific domain account?
If so, then you will not be able to connect to SQL Server using Windows Authentication without defining the network credentials. There are a couple ways you can define that network credential:
1) Download ShellRunAs from SysInternals, execute ShellRunAs from a command window and launch SSMS (e.g. C:\SysInternals\ShellRunAs.exe /netonly SqlWb.exe). This will prompt for your network credentials, enter the domain\username credentials and password. In SSMS - you can now connect using Windows Authentication.
2) Open command window and run: C:\Runas /netonly /user:domain\username SqlWb.exe. This will prompt on the command line for your password. Enter the domain\username password and you can then connect to the SQL Server using Windows Authentication.
If you are not using Windows Authentication, then you don't need either of the above. All you should need is the SQL user and password to that instance.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
April 14, 2009 at 11:10 am
Yes, we are using Windows authentication. Thanks a lot. I'll try this out.
April 14, 2009 at 11:39 am
You should ask your client for the port number.
One way to find that is go to sql server configuration manager (on clients windows box hosting the server) --sql server 2005 network configuration--protocols for ms sqlserver--tcpip --ipaddresses (pls keep in mind that you cannot do this since you cannot connect to your client).
April 14, 2009 at 12:00 pm
I have another question - how do you connect to the client's server? Do you connect using an IP address or the name? If you use IP address, then that is what you are going to use from your local PC - if name, then you can use that.
As for the port numbers, that will only be an issue if one of the following conditions exist:
1) You are connecting to the default instances and the port number is a static port.
2) You are connecting to a named instance, the port number is a static port and the SQL Browser service is not running.
And finally, if there is any type of port filtering on the VPN connection - that could prevent you from accessing SQL Server without connecting to the server first.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
April 15, 2009 at 6:07 pm
Thanks everyone. I tried the option 1 and it worked for me. Thanks again.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply