Hello,
I have a Win2K3 server with SQL2005 Express installed. The server also allows VPN connections.
From a remote computer, I can VPN without problem to the server. However, I get mixed results when trying to connect to the SQL Server. Usually it doesn't connect at all. If I play with forcing TCP/IP or Named pipes and/or connect using Windows Authentication or SQL Authentication, I can usually get a connection. This is after trying a variety of different connection types. I can't make it consistently repeat the failure or success of the connection, so I am puzzled what the correct method should be.
Once connected, the connection is very very slow. So slow that it's not even worth doing. I am using DSL on both ends.
A while back, before I had enabled VPN, I temporarily exposed the server IP address to the internet so that I could ping the IP address from a remote location. In doing this, I was able to connect to SQL server with decent speed and performance.
I don't think that its a VPN problem though because I can copy files to and from the server relatively quickly.
The slow SQL performance and erractic connection is exhibited using the client front end (which uses OLEDB) as well as simply connecting using SQL Management Studio.
From within the main office, on a LAN, all connections to SQL server work just fine with good speed and performance.
So - all that said, is there a performed method of connecting to SQL server via VPN? Are there any specific ports I need to enable in the firewall? (I've twiddled with this but it doesn't seem to help or hurt it).
Thanks
I have a Win2K3 server with SQL2005 Express installed. The server also allows VPN connections.
From a remote computer, I can VPN without problem to the server. However, I get mixed results when trying to connect to the SQL Server. Usually it doesn't connect at all. If I play with forcing TCP/IP or Named pipes and/or connect using Windows Authentication or SQL Authentication, I can usually get a connection. This is after trying a variety of different connection types. I can't make it consistently repeat the failure or success of the connection, so I am puzzled what the correct method should be.
Once connected, the connection is very very slow. So slow that it's not even worth doing. I am using DSL on both ends.
A while back, before I had enabled VPN, I temporarily exposed the server IP address to the internet so that I could ping the IP address from a remote location. In doing this, I was able to connect to SQL server with decent speed and performance.
I don't think that its a VPN problem though because I can copy files to and from the server relatively quickly.
The slow SQL performance and erractic connection is exhibited using the client front end (which uses OLEDB) as well as simply connecting using SQL Management Studio.
From within the main office, on a LAN, all connections to SQL server work just fine with good speed and performance.
So - all that said, is there a performed method of connecting to SQL server via VPN? Are there any specific ports I need to enable in the firewall? (I've twiddled with this but it doesn't seem to help or hurt it).
Thanks