Connection over VPN

I have MSDE server installed on a pc at work. This PC runs Windows XP and
runs as a VPN server as well.
I have SQL Server Enterpise Manager on my laptop, and need to be able to
manage the MSDE server when connected to work from home, using a VPN.
When I try to add the server in Enterprise Manager, it says access is denied
or server is unavailable. I have read a lot of posts about using named
pipes, opening port 1723 but none of these have worked for me.
Any ideas please?
Tom
I suspect your actual error message was "sql server does not exist or
access denied". There are many potential causes as outlined in this article:
328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306
If the problem is only with VPNs I would probably concentrate on ports that
are blocked for VPN connections or permissions that are different for VPN
connections.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection over VPN

I have MSDE server installed on a pc at work. This PC runs Windows XP and
runs as a VPN server as well.
I have SQL Server Enterpise Manager on my laptop, and need to be able to
manage the MSDE server when connected to work from home, using a VPN.
When I try to add the server in Enterprise Manager, it says access is denied
or server is unavailable. I have read a lot of posts about using named
pipes, opening port 1723 but none of these have worked for me.
Any ideas please?
TomI suspect your actual error message was "sql server does not exist or
access denied". There are many potential causes as outlined in this article:
328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306
If the problem is only with VPNs I would probably concentrate on ports that
are blocked for VPN connections or permissions that are different for VPN
connections.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection error to remote SQL instance, over VPN

I am trying to connect to an instance of SQL Express through a vpn, simply using the SQL Management Studio, providing the server ip address x.x.x.x\MSSQLSERVER, and using SQL authentication login. I receive the following message:

Cannot connect to <server>, etc., etc.

error 25: - Connection string is not valid

Does anyone understand this? I am trying to connect through the SQL Server Management interface, not with a client program that would utilize a connection string. Is there something which prevents Management Studio from working over a vpn?

To connect, I am using SQL authentication, and have verified the login and password locally on the target pc. The SQL browser service is running on the target pc, and I can telnet to the port which it is monitoring, through the same vpn connection. Remote connections are enabled for TCP/IP in the Surface Area configuration on the target pc.

Any help appreciated.

x.x.x.x\MSSQLSERVER is not correct. You cannot use MSSQLSERVER as the instance name because it is reserved for default instance. Since your instance is SSE, you should use x.x.x.x\sqlexpress. Based on your description, your connection should work with the fix. Please make sure UDP port 1434 (used by sql browser) is blocked by firewall.|||

SSE is installed as the default instance, so /MSSQLSERVER does work, as tested locally. Also the assigned port is opened through the firewall, as tested by telnetting through the vpn.

However here is additional information since I posted the problem: Using a packet tracker, I can see no handshaking messages are transmitted on the vpn network when the connection is attempted by SSE Studio. If I connect to a local SQL pc (on my local, non-virtual network), I see the TCP messages, handshaking, etc. and it instantly connects. Why does SSE Studio not attempt to connect over the vpn network? Ping and telnet do work over that network, so the operating system correctly distinguishes the networks. Just not SSE Studio. Is there a way to force it to this network?

|||If it's default instance, you should remove MSSQLSERVER, use x.x.x.x only. Also, use c:\windows\system32\cliconfg.exe on your client machine to check whether TCP is enabled on the client. Is your server listening on TCP port 1433? If not, please confirm sql browser is running and UDP port 1434 is in firewall's exception list. Thanks.|||

I figured it out, the connection text must specify the port after the ip address. Format:

x.x.x.x,1433 (or whatever port #)

It works in SSE Studio, and in the client app. (Access project). An example is here: http://www.connectionstrings.com/, under SQL Server connections -> SqlConnection(.NET) -> connection via ip address.

What is confusing is that the port specification is apparently not required if connecting to another pc on the same lan, only if connecting over the internet/vpn.

|||

If x.x.x.x,1433 workes, x.x.x.x should work unless your have any alias defined for x.x.x.x. You use c:\windows\system32\cliconfg.exe to check it.

If you tcp port is not 1433, then you must make sure sql browser is running and UDP port 1434 is not blocked. "x.x.x.x,port" can bypass the requirement of sql browser.

Connecting via VPN

Your machine and the customer's are not in the same domain so Windows
authentication won't work because there's no way to authenticate the user on
your machine. SQL Auth should work unless there's something else blocking
the TCP/IP connection. It might help to know what error you're getting and
if there is an error in the server error log. Running EM remotely is
actually the best solution in this case.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Middletree" <middletree@.hottttttttmail.com> wrote in message
news:OitGvBWlGHA.4772@.TK2MSFTNGP04.phx.gbl...
> One my company's customers has allowed me to connect to their network via
> VPN. Overall, it seems to work fine. I can remote in, or map drives, etc.
> However, I have been unable to use my SQL2000 Enterprise manager to
> connect to their database. I can remote into the machine where that
> database resides and open up EM there, but I can't do it from EM on my
> machine. That is, I'm getting a 'logon failed' error, regardless of
> whether or not I am using Windows or SQL authentication.
> I did some digging, and found that ports 1433 and 1434 need to be open for
> this to happen. However, the customer has stated that he isn't blocking
> off these ports.
> Anyone know of any issues with doing this over VPN?
>One my company's customers has allowed me to connect to their network via
VPN. Overall, it seems to work fine. I can remote in, or map drives, etc.
However, I have been unable to use my SQL2000 Enterprise manager to connect
to their database. I can remote into the machine where that database resides
and open up EM there, but I can't do it from EM on my machine. That is, I'm
getting a 'logon failed' error, regardless of whether or not I am using
Windows or SQL authentication.
I did some digging, and found that ports 1433 and 1434 need to be open for
this to happen. However, the customer has stated that he isn't blocking off
these ports.
Anyone know of any issues with doing this over VPN?|||Your machine and the customer's are not in the same domain so Windows
authentication won't work because there's no way to authenticate the user on
your machine. SQL Auth should work unless there's something else blocking
the TCP/IP connection. It might help to know what error you're getting and
if there is an error in the server error log. Running EM remotely is
actually the best solution in this case.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Middletree" <middletree@.hottttttttmail.com> wrote in message
news:OitGvBWlGHA.4772@.TK2MSFTNGP04.phx.gbl...
> One my company's customers has allowed me to connect to their network via
> VPN. Overall, it seems to work fine. I can remote in, or map drives, etc.
> However, I have been unable to use my SQL2000 Enterprise manager to
> connect to their database. I can remote into the machine where that
> database resides and open up EM there, but I can't do it from EM on my
> machine. That is, I'm getting a 'logon failed' error, regardless of
> whether or not I am using Windows or SQL authentication.
> I did some digging, and found that ports 1433 and 1434 need to be open for
> this to happen. However, the customer has stated that he isn't blocking
> off these ports.
> Anyone know of any issues with doing this over VPN?
>|||[vbcol=seagreen]
And your local firewall (if any)?
Try to connect with telnet on port 1433 and/or osql or sqlcmd with the
"tcp:"-prefix.
More infor here
http://blogs.msdn.com/sql_protocols.../22/483684.aspx
And the remote connection is not always the best solution - perhaps the
local machine is a development-station for test and debugging - porting
changes is a whole lot easier with local access...
/ola|||[vbcol=seagreen]
And your local firewall (if any)?
Try to connect with telnet on port 1433 and/or osql or sqlcmd with the
"tcp:"-prefix.
More infor here
http://blogs.msdn.com/sql_protocols.../22/483684.aspx
And the remote connection is not always the best solution - perhaps the
local machine is a development-station for test and debugging - porting
changes is a whole lot easier with local access...
/ola

Connecting to SQL Server with Zone Alarm

I am trying to use a cisco VPN connection to SQL Server. Zone Alarm is
blocking the ports, does anyone know which ports in zone alarm that I need
to unblock?Check the following article:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
-Sue
On Mon, 24 Apr 2006 20:50:01 -0700, Art Yates
<ArtYates@.discussions.microsoft.com> wrote:

>I am trying to use a cisco VPN connection to SQL Server. Zone Alarm is
>blocking the ports, does anyone know which ports in zone alarm that I need
>to unblock?

Connecting to SQL Server over a VPN & through a router...

Hi All,
I have a NetGear combined wireless router / ADSL modem, and am
attempting to connect to SQL Server from my (wifi enabled) laptop, but
am getting a 'failed to create SSPI context' message (note that I'm
using Windows Authentication). I'm connected to my work LAN through a
SonicWall VPN. If I take the router out of the equation, I can connect
fine - even through the VPN.
Outlook also has no luck connecting - it appears that some aspect of
Windows Authentication is broken by the router being included in the
setup.
I can ping machines on my company LAN when connected through the
router, and can also connect to SQL server using the SS authentication
- so I'm not far away from being able to authenticate.
Any thoughts/help would be much appreciated.
Thanks,
Will (LemonSmasher)
Mmm... looks like I've 'solved' this. Having established the VPN
connection for the first time, I logged off of Windows, then logged
back on, reestablished the VPN connection and then authentication
worked. Must've been down to something being cached in my original
session - if anyone can shed light on this (or if its just a lucky
coincidence!), I'd be interested in hearing from you!
Will.
LemonSmas...@.hotmail.com wrote:
> Hi All,
> I have a NetGear combined wireless router / ADSL modem, and am
> attempting to connect to SQL Server from my (wifi enabled) laptop, but
> am getting a 'failed to create SSPI context' message (note that I'm
> using Windows Authentication). I'm connected to my work LAN through a
> SonicWall VPN. If I take the router out of the equation, I can connect
> fine - even through the VPN.
> Outlook also has no luck connecting - it appears that some aspect of
> Windows Authentication is broken by the router being included in the
> setup.
> I can ping machines on my company LAN when connected through the
> router, and can also connect to SQL server using the SS authentication
> - so I'm not far away from being able to authenticate.
> Any thoughts/help would be much appreciated.
> Thanks,
> Will (LemonSmasher)

Connecting to SQL Server over a VPN & through a router...

Hi All,
I have a NetGear combined wireless router / ADSL modem, and am
attempting to connect to SQL Server from my (wifi enabled) laptop, but
am getting a 'failed to create SSPI context' message (note that I'm
using Windows Authentication). I'm connected to my work LAN through a
SonicWall VPN. If I take the router out of the equation, I can connect
fine - even through the VPN.
Outlook also has no luck connecting - it appears that some aspect of
Windows Authentication is broken by the router being included in the
setup.
I can ping machines on my company LAN when connected through the
router, and can also connect to SQL server using the SS authentication
- so I'm not far away from being able to authenticate.
Any thoughts/help would be much appreciated.
Thanks,
Will (LemonSmasher)Mmm... looks like I've 'solved' this. Having established the VPN
connection for the first time, I logged off of Windows, then logged
back on, reestablished the VPN connection and then authentication
worked. Must've been down to something being cached in my original
session - if anyone can shed light on this (or if its just a lucky
coincidence!), I'd be interested in hearing from you!
Will.
LemonSmas...@.hotmail.com wrote:
> Hi All,
> I have a NetGear combined wireless router / ADSL modem, and am
> attempting to connect to SQL Server from my (wifi enabled) laptop, but
> am getting a 'failed to create SSPI context' message (note that I'm
> using Windows Authentication). I'm connected to my work LAN through a
> SonicWall VPN. If I take the router out of the equation, I can connect
> fine - even through the VPN.
> Outlook also has no luck connecting - it appears that some aspect of
> Windows Authentication is broken by the router being included in the
> setup.
> I can ping machines on my company LAN when connected through the
> router, and can also connect to SQL server using the SS authentication
> - so I'm not far away from being able to authenticate.
> Any thoughts/help would be much appreciated.
> Thanks,
> Will (LemonSmasher)

Connecting to SQL Server across VPN

I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is on
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
Thanks
Hi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>

Connecting to SQL Server across VPN

I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is on
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
Thanks
Hi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>
|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>

Connecting to SQL Server across VPN

I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is on
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
ThanksHi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>

Connecting to SQL Server across VPN

I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is on
192.168.10.0. The database is on a folder that is shared and 'Everybody'
has full control.
The POS is on 192.168.11.0 and has drive X mapped to the share on the server
with the database. The POS software gets a SQL access denied error
connecting to the database on the server. POS terminal on the same network
connect without any trouble.
How can I work around this? We are using Microsoft Retail Management POS
system.
ThanksHi,
Create a Server Alias using Client network utility, specifying TCP IP as
protocol. After that use the new Alias server name to connect to sql server.
Thanks
Hari
SQL Server MVP
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>|||I successfully connected across a PPTP VPN and then to SQL server, but it
was a very round-about way. It was necessary that I have a permanent VPN
tunnel up and performance was an issue. This made it necessary to have two
routers create the tunnnel instead of SBS, however, getting there was a
chore and I thought I would share this.
I first established a PPTP tunnel between the two Netopia R910 routers.
Then on the remote POS terminal (192.168.11.2), I created an entry in LMHOST
pointing the server (tpsrvr01) to 192.168.10.2. Then I changed the DNS on
the the POS to point to the SBS server, 192.168.10.2.
I then tried to manually join the domain, but an error was thrown up that no
domain controller could be contacted when I changed from workgroup to
thepatch.loca
I stopped the router from answering PPTP requests and forwarded PPTP
requests to RRAS on the SBS server. I created a PPTP VPN connection on the
POS, made a connection to the SBS server, then joined the domain. When the
workstaion rebooted, I check off the dialup box on the login screen, made a
VPN connection first, and logged on to the domain.
After all this was successful, I got the VPN tunnel going again between the
two routers and the POS terminal logged on fine to the SBS server. I was
also able to connect to the SQL server database for the POS too.
"Rob_Wal" <r042wal@.dontspammeatgmail.com> wrote in message
news:evofEf1WFHA.1404@.TK2MSFTNGP09.phx.gbl...
>I have a PPTP VPN tunnel created with two Netopia routers. SQL Server is
>on 192.168.10.0. The database is on a folder that is shared and
>'Everybody' has full control.
> The POS is on 192.168.11.0 and has drive X mapped to the share on the
> server with the database. The POS software gets a SQL access denied error
> connecting to the database on the server. POS terminal on the same
> network connect without any trouble.
> How can I work around this? We are using Microsoft Retail Management POS
> system.
> Thanks
>

Connecting to SQL Server 2005 over VPN Not working

I am having trouble connecting to SQL Server 2005 from my home via VPN
connection to my office. I have enabled remote connections on the
server. I can actually connect to my local SQL Server instance from
the Server machine while connected to the VPN but not the other way
around. I can browse shared folders from the Server machine so my vpn
connection is good. Other machines in the office can remotely connect
to the SQL Server instance on the server machine.
Is there some setting on the server, such as somewhere in RRAS, that I
need to configure to allow me to connect?
FYI: I am using SQL Authentication
ThanksHi
"chack.busedge@.gmail.com" wrote:

> I am having trouble connecting to SQL Server 2005 from my home via VPN
> connection to my office. I have enabled remote connections on the
> server. I can actually connect to my local SQL Server instance from
> the Server machine while connected to the VPN but not the other way
> around. I can browse shared folders from the Server machine so my vpn
> connection is good. Other machines in the office can remotely connect
> to the SQL Server instance on the server machine.
> Is there some setting on the server, such as somewhere in RRAS, that I
> need to configure to allow me to connect?
> FYI: I am using SQL Authentication
> Thanks
>
Check out http://support.microsoft.com/kb/287932 on the ports that you will
need to have access to for the connection. Have you tried terminal services
or Remote desktop to access the server?
John|||On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
>
>
> "chack.buse...@.gmail.com" wrote:
>
>
>
> Check outhttp://support.microsoft.com/kb/287932on the ports that you will
> need to have access to for the connection. Have you tried terminal service
s
> or Remote desktop to access the server?
> John- Hide quoted text -
> - Show quoted text -
The VPN was configured using the RRAS console. Is there something I
need to configure there to allow port 1433 access via VPN?
Yes, I can remote desktop into the server. That's how I am
configuring the VPN.
Thanks|||On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
> TheVPNwas configured using the RRAS console. Is there something I
> need to configure there to allow port 1433 access viaVPN?
> Yes, I can remote desktop into theserver. That's how I am
> configuring theVPN.
> Thanks- Hide quoted text -
> - Show quoted text -
Ok, I finally got something to work. I was reviewing this article
http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
Ports value to be 1033. On a whim I decided to set my server name
value for my connection to...
SERVER\INSTANCENAME,1033
And voila, it freeking worked. I don't know why, but at this point I
don't care. I am thrilled to have a connection that I can use at
home. I sure hope this helps out someone else in the future.|||Hi
"chack.busedge@.gmail.com" wrote:

> On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> Ok, I finally got something to work. I was reviewing this article
> http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
> Ports value to be 1033. On a whim I decided to set my server name
> value for my connection to...
> SERVER\INSTANCENAME,1033
> And voila, it freeking worked. I don't know why, but at this point I
> don't care. I am thrilled to have a connection that I can use at
> home. I sure hope this helps out someone else in the future.
>
You had not said that you had a named instance of SQL Server!! By default
that will use a dynamic port instead of 1433 see
http://msdn2.microsoft.com/en-us/library/ms177440.aspx You have forced the
server to use a specific port (which seems to be open!!)
Ports from 1024 through 49151 are IANA registered ports, and 1033 is
registered for netinfo. IANA recommend that dynamic or Private Ports from
49152 through 65535 are used.
John

Connecting to SQL Server 2005 over VPN Not working

I am having trouble connecting to SQL Server 2005 from my home via VPN
connection to my office. I have enabled remote connections on the
server. I can actually connect to my local SQL Server instance from
the Server machine while connected to the VPN but not the other way
around. I can browse shared folders from the Server machine so my vpn
connection is good. Other machines in the office can remotely connect
to the SQL Server instance on the server machine.
Is there some setting on the server, such as somewhere in RRAS, that I
need to configure to allow me to connect?
FYI: I am using SQL Authentication
Thanks
Hi
"chack.busedge@.gmail.com" wrote:

> I am having trouble connecting to SQL Server 2005 from my home via VPN
> connection to my office. I have enabled remote connections on the
> server. I can actually connect to my local SQL Server instance from
> the Server machine while connected to the VPN but not the other way
> around. I can browse shared folders from the Server machine so my vpn
> connection is good. Other machines in the office can remotely connect
> to the SQL Server instance on the server machine.
> Is there some setting on the server, such as somewhere in RRAS, that I
> need to configure to allow me to connect?
> FYI: I am using SQL Authentication
> Thanks
>
Check out http://support.microsoft.com/kb/287932 on the ports that you will
need to have access to for the connection. Have you tried terminal services
or Remote desktop to access the server?
John
|||On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
>
>
> "chack.buse...@.gmail.com" wrote:
>
>
> Check outhttp://support.microsoft.com/kb/287932on the ports that you will
> need to have access to for the connection. Have you tried terminal services
> or Remote desktop to access the server?
> John- Hide quoted text -
> - Show quoted text -
The VPN was configured using the RRAS console. Is there something I
need to configure there to allow port 1433 access via VPN?
Yes, I can remote desktop into the server. That's how I am
configuring the VPN.
Thanks
|||On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
> TheVPNwas configured using the RRAS console. Is there something I
> need to configure there to allow port 1433 access viaVPN?
> Yes, I can remote desktop into theserver. That's how I am
> configuring theVPN.
> Thanks- Hide quoted text -
> - Show quoted text -
Ok, I finally got something to work. I was reviewing this article
http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
Ports value to be 1033. On a whim I decided to set my server name
value for my connection to...
SERVER\INSTANCENAME,1033
And voila, it freeking worked. I don't know why, but at this point I
don't care. I am thrilled to have a connection that I can use at
home. I sure hope this helps out someone else in the future.
|||Hi
"chack.busedge@.gmail.com" wrote:

> On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> Ok, I finally got something to work. I was reviewing this article
> http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
> Ports value to be 1033. On a whim I decided to set my server name
> value for my connection to...
> SERVER\INSTANCENAME,1033
> And voila, it freeking worked. I don't know why, but at this point I
> don't care. I am thrilled to have a connection that I can use at
> home. I sure hope this helps out someone else in the future.
>
You had not said that you had a named instance of SQL Server!! By default
that will use a dynamic port instead of 1433 see
http://msdn2.microsoft.com/en-us/library/ms177440.aspx You have forced the
server to use a specific port (which seems to be open!!)
Ports from 1024 through 49151 are IANA registered ports, and 1033 is
registered for netinfo. IANA recommend that dynamic or Private Ports from
49152 through 65535 are used.
John

Connecting to SQL Server 2005 over VPN Not working

I am having trouble connecting to SQL Server 2005 from my home via VPN
connection to my office. I have enabled remote connections on the
server. I can actually connect to my local SQL Server instance from
the Server machine while connected to the VPN but not the other way
around. I can browse shared folders from the Server machine so my vpn
connection is good. Other machines in the office can remotely connect
to the SQL Server instance on the server machine.
Is there some setting on the server, such as somewhere in RRAS, that I
need to configure to allow me to connect?
FYI: I am using SQL Authentication
ThanksHi
"chack.busedge@.gmail.com" wrote:
> I am having trouble connecting to SQL Server 2005 from my home via VPN
> connection to my office. I have enabled remote connections on the
> server. I can actually connect to my local SQL Server instance from
> the Server machine while connected to the VPN but not the other way
> around. I can browse shared folders from the Server machine so my vpn
> connection is good. Other machines in the office can remotely connect
> to the SQL Server instance on the server machine.
> Is there some setting on the server, such as somewhere in RRAS, that I
> need to configure to allow me to connect?
> FYI: I am using SQL Authentication
> Thanks
>
Check out http://support.microsoft.com/kb/287932 on the ports that you will
need to have access to for the connection. Have you tried terminal services
or Remote desktop to access the server?
John|||On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
>
>
> "chack.buse...@.gmail.com" wrote:
> > I am having trouble connecting to SQL Server 2005 from my home via VPN
> > connection to my office. I have enabled remote connections on the
> > server. I can actually connect to my local SQL Server instance from
> > the Server machine while connected to the VPN but not the other way
> > around. I can browse shared folders from the Server machine so my vpn
> > connection is good. Other machines in the office can remotely connect
> > to the SQL Server instance on the server machine.
> > Is there some setting on the server, such as somewhere in RRAS, that I
> > need to configure to allow me to connect?
> > FYI: I am using SQL Authentication
> > Thanks
> Check outhttp://support.microsoft.com/kb/287932on the ports that you will
> need to have access to for the connection. Have you tried terminal services
> or Remote desktop to access the server?
> John- Hide quoted text -
> - Show quoted text -
The VPN was configured using the RRAS console. Is there something I
need to configure there to allow port 1433 access via VPN?
Yes, I can remote desktop into the server. That's how I am
configuring the VPN.
Thanks|||On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > Hi
> > "chack.buse...@.gmail.com" wrote:
> > > I am having trouble connecting toSQLServer2005from my home viaVPN
> > > connection to my office. I have enabled remote connections on the
> > >server. I can actually connect to my localSQLServerinstance from
> > > theServermachine while connected to theVPNbut not the other way
> > > around. I can browse shared folders from theServermachine so myvpn
> > > connection is good. Other machines in the office can remotely connect
> > > to theSQLServerinstance on theservermachine.
> > > Is there some setting on theserver, such as somewhere in RRAS, that I
> > > need to configure to allow me to connect?
> > > FYI: I am usingSQLAuthentication
> > > Thanks
> > Check outhttp://support.microsoft.com/kb/287932onthe ports that you will
> > need to have access to for the connection. Have you tried terminal services
> > or Remote desktop to access theserver?
> > John- Hide quoted text -
> > - Show quoted text -
> TheVPNwas configured using the RRAS console. Is there something I
> need to configure there to allow port 1433 access viaVPN?
> Yes, I can remote desktop into theserver. That's how I am
> configuring theVPN.
> Thanks- Hide quoted text -
> - Show quoted text -
Ok, I finally got something to work. I was reviewing this article
http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
Ports value to be 1033. On a whim I decided to set my server name
value for my connection to...
SERVER\INSTANCENAME,1033
And voila, it freeking worked. I don't know why, but at this point I
don't care. I am thrilled to have a connection that I can use at
home. I sure hope this helps out someone else in the future.|||Hi
"chack.busedge@.gmail.com" wrote:
> On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> > On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> >
> >
> >
> >
> >
> > > Hi
> >
> > > "chack.buse...@.gmail.com" wrote:
> > > > I am having trouble connecting toSQLServer2005from my home viaVPN
> > > > connection to my office. I have enabled remote connections on the
> > > >server. I can actually connect to my localSQLServerinstance from
> > > > theServermachine while connected to theVPNbut not the other way
> > > > around. I can browse shared folders from theServermachine so myvpn
> > > > connection is good. Other machines in the office can remotely connect
> > > > to theSQLServerinstance on theservermachine.
> >
> > > > Is there some setting on theserver, such as somewhere in RRAS, that I
> > > > need to configure to allow me to connect?
> >
> > > > FYI: I am usingSQLAuthentication
> >
> > > > Thanks
> >
> > > Check outhttp://support.microsoft.com/kb/287932onthe ports that you will
> > > need to have access to for the connection. Have you tried terminal services
> > > or Remote desktop to access theserver?
> >
> > > John- Hide quoted text -
> >
> > > - Show quoted text -
> >
> > TheVPNwas configured using the RRAS console. Is there something I
> > need to configure there to allow port 1433 access viaVPN?
> >
> > Yes, I can remote desktop into theserver. That's how I am
> > configuring theVPN.
> >
> > Thanks- Hide quoted text -
> >
> > - Show quoted text -
> Ok, I finally got something to work. I was reviewing this article
> http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
> Ports value to be 1033. On a whim I decided to set my server name
> value for my connection to...
> SERVER\INSTANCENAME,1033
> And voila, it freeking worked. I don't know why, but at this point I
> don't care. I am thrilled to have a connection that I can use at
> home. I sure hope this helps out someone else in the future.
>
You had not said that you had a named instance of SQL Server!! By default
that will use a dynamic port instead of 1433 see
http://msdn2.microsoft.com/en-us/library/ms177440.aspx You have forced the
server to use a specific port (which seems to be open!!)
Ports from 1024 through 49151 are IANA registered ports, and 1033 is
registered for netinfo. IANA recommend that dynamic or Private Ports from
49152 through 65535 are used.
John