Unable to access SQL server via VPN connection

[web4fun]

INFO:

Client PC running WinXP w/SP2 and Cisco VPN Client 4.8.00.0440

SQL Server 2000 with both SQL and Windows Authentication enabled.

PROBLEM:

I have a remote user that accesses our network via VPN and after authenticating through the VPN the user is unable to login to any of our SQL Servers.

Could the problem be a name resolution problem? After authenticating on the VPN, the users should be on our network.

Could this be a blocked port somewhere on the client side as we've checked our Firewall and other remote users aren't having any problems?

I am going to have the user try just SQL Server authentication to narrow down the scope as a work-around but any suggestions would be greatly appreciated.

Thanks in advance.

 

[onpnt]

More than likely a blocked port (or range) in your group settings on the concentrator and or an ip range setting not allowing the user to get to the address of the server all together.

Are there other users in the same group policy that can remotely access the instances via vpn connectivity?

_{____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done}

 

[web4fun]

Yeah...we had thought about a problem with a blocked port on the concentrator...but we've checked that and everyone is in the same group policy and other remote folks don't have a problem. That being said, this remote users that is having the problem logs onto a completely different network and then VPNs into our network...so I'm suspecting a problem perhaps with the other network/firewall.

 

[onpnt]

Is the network trusted? Can he/she ping the SQL Server box?





_{____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done}

 

[web4fun]

No the network is not trusted...I'm having the user check the standard connectivity test; i.e. ping..etc. Also suggested that they attempt to connect to the SQL server using IP Address or FQDN.

 

[onpnt]

I'm guessing using SQL Server authentication will work as long as they can see the server. After reading they are not on your network I'm sure that is the cause of the failure. My network setup knowledge isn't that great but I believe if the other network is trusted and they have an account on the instance they should authenticate fine. Like I said I've never really dealt with these types of setups and I'm pulling it from the cob webs in the back of my head ;-)

_{____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done}

 

[web4fun]

Yeah...I'm pretty confident as well that the workaround using SQL Server authentication will work as well. The thing is this user's PC which is a laptop does travel to our home office frequently, thus he has a user account on our domain and his laptop is a member of the domain so not sure why it's not working for this user..especially since the VPN tunnel should allow access to all of our network resources...just as if he/she were sitting in the building. Thanks for the suggestions.