September 14, 2004 at 5:38 pm
I am new to SQL Server and I am a bit confused. Here is the scenario.
I have a home PC (xp pro) on which I have loaded SQL Server. This is fine as I can see it in my EM. On my work server I also have sql server which I need to administer. Both of them (my home pc as well as my work server are behnd a linksys router). I am connecting to my work via a vpn. I start my vpn and then I start my EM to register my server. It times out on me. What do I do?
September 16, 2004 at 10:26 am
I am doing the same (XP pro at home, connecting via VPN).
I am guessing, but the first problem I had was DNS name resolution of the server name. Try pinging the work server from dos. If the server name is 'not recognised' then try pinging the server by its IP address. If that works, try pinging the server name with its work domain name on the front (eg ping domainname.server). If this works then you need to change your VPN settings to tell it to prefix your server names with the domain name.
If you can't ping the server at all and you have a firewall, make sure that you have added your work ip address range to your firewall. If you have a firewall, check the alert log for relevant messages.
If you can't ping at all and you don't have a firewall, the problem could be that you don't have domain security access to the server with the user name you are connecting to the work network with via the VPN.
If you can ping the server OK by server name, then the problem could just be that your EM has a low value in its 'connection timeout' property. In your home PCs EM go to Tools-Options-Advanced tab and increase the Login time-out. Also check the work SQL server (at work) properties to make sure it accepts remote connections from other SQL servers (in EM right click on server name (maybe just '(local)') select Properties, go to Connections tab and check the 'Allow other SQL servers to connect remotely to this SQL server using RPC' option is ticked).
Hope this gives you some pointers.
Peter
September 16, 2004 at 11:25 am
adding to what Enthusiast mention, at home try to register your work's sql by using the local ip address in stead of server name.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply