Is it possible to utilize a VPN connection and still access the database
via. ODBC or will I be forced to use on of the Replication Technologies.

A. The situation at the Office:
====================
1. A Windows 2000 Server running the SQL database as a Service
2. Clients are connected through the LAN and use ODBC to connect to the
database

B. The situation for Home users:
======================
1. The users log into the Server from home over a VPN connection. I
understand that the result is similar to actually sitting at the office
(Like PCAnywhere or Laplink)
2. We want them to then access the SQL database using ODBC.

Anybody have success with this? If so, how do we make it work?

Thanks,
Dean Miessner
Custom Computer Services, LLC
770-653-4393

In article <443bc9d4$1@forums-1-dub>, customcomputerse (AT) bellsouth (DOT) net
says...
But slower, especially on intial connection.


It works; I've done it. But you need to specify some extra options in
the tcp/ip config line of the ODBC DSN setup. It's been a couple of
years since I've done it, but IIRC, you need the HOST=, PORT= and
DOBROADCAST=none entries. Possibly a couple more. Give it a try and
see what you get.

....

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Hello Dean,

yes, it's possible, but it is - for us - much too slow.

background:
Site A: SQL Server, Cisco router, SDSL 512/512 kBit
Site B: ADSL 1024/128 kBit, (Cisco VPN Client) and Cisco Router

I think the reaction time is the real problem; if I copy a file I feel
the transfer speed is ok, but changing a directory in Explorer takes a
long time.

We are now installing a Windows Terminal Server for the out-of-office
users and upgrading the ADSL line to SDSL 2 MBit.

In the System-DSN you have only to add "HOST=x.x.x.x" at Network - TCP/IP.

Michael




customcomputerse (AT) bellsouth (DOT) net schrieb:

I regularly install client server ASA8.03 across a VPN. Your comms link
will probably be the performance limiting factor, but all depend on the
volume of traffic using the VPN between the HQ and remote locations.

Here is a copy of the ODBC reg I currently use:


[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\****]
"Driver"="C:\\Program Files\\Sybase\\SQL Anywhere 8\\win32\\dbodbc8.dll"
"Description"="**** **** ****"
"DatabaseName"="****"
"EngineName"="****"
"AutoStop"="Yes"
"Integrated"="No"
"Debug"="No"
"LivenessTimeout"="0"
"DisableMultiRowFetch"="No"
"CommLinks"="SharedMemory,TCPIP{host=192.168.0.1;d obroadcast=None}"
"Compress"="No"
"IdleTimeout"="0"
"SuppressWarnings"="Yes"
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
"****"="Adaptive Server Anywhere 8.0"

I reccomend use of Terminal Server solution if you find the VPN
clinet/server link to slow.

Snelbert



"Sybase newsgroups" <ns_dkerber (AT) ns_WarrenRogersAssociates (DOT) com> wrote in
message news:MPG.1ea5892b16dda22d9897df (AT) forums (DOT) sybase.com...

No problem , don't mention it!