Access connecting to MS-SQL thru Cisco VPN client and PIX

[Haggart]

I have a workstation (XP Pro) being used as a test server for a trial version of Microsoft SQL. This test server also houses an EasyPHP setup. Several local workstations have been able to connect to the test server either via the web site server (IP or by name) or through ODBC into the SQL server.
A problem occurs went VPN clients try to connect to the test server. The EasyPHP/web side works fine (they can connect with IP or by name) but the ODBC connection fails. ODBC errors are 17 - no server or denied access, and 1326 - no user or denied access.
Any thoughts on why the database can't be found? Thanks.

 

[ArtieChoke]

I'm assuming all your local computers are part of a domain. Are the VPN computers also members of the domain? If not, they will not get trusted access to the databases. I'm not even sure if they can get access via SQL Server security - that might be something to try if you're not going to let the remote computers join the domain.

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[Haggart]

Yes, the local systems are part of a domain (SBS 2003) and any VPN clients much logon to the domain to access the server and network in general.

 

[ArtieChoke]

Are the VPN client machines registered with the domain? If you connect with one, can you see it via network neighborhood, etc.?

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[Haggart]

VPN clients don't see any local machines via the network neighorhood (or the like).

VPN clients do receive a challenge box and ask for user name and password. But, the servers DHCP (SBS2003) doesn't show any VPN machines because the PIX hands out VPN client IPs.

I logged in as a VPN client and tried to setup a ODBC connection through "Data Sources (ODBC)", under admin tools. I get this error message during setup:
"Workgroup is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The list of servers for this workgroup is not currently available"

Hope this helps.

 

[ArtieChoke]

What OS are the clients using? Even that won't matter, as I've used both XP home and pro and get the same situation. The client machines must be a member of the domain before they can access databases via ODBC. The VPN login does not give them that level of access. It's a pain, I know! Have you looked into terminal services for the vpn machines?

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[Haggart]

Thanks for checking this out ArtieChoke.
The VPN client's O/S is XP Pro.
Still, it's strange. The VPN clients must log into the network domain. If they don't provide a domain user name and password, they can't log into Outlook or the file server. The Access database file that uses the ODBC link sits on the file server. So, you have to log on to the file server (hence the domain) to access the file that uses the ODBC link.
Maybe the VPN isn't setup right and is blocking some part of the two way traffic?

 

[ArtieChoke]

That's the way it is at my work also. You can see email via Outlook and file shares. Note: you still have to sign in to both, even though you've signed into VPN, since you are not really logged onto the NT domain, just the VPN server. You won't be able to get database access via ODBC unless the computers are in the NT domain.

"I think we're all Bozos on this bus!" - Firesign Theatre