ODBC over a Private WAN

[NoeNoa]

My company is looking to expand through a partnership with another firm. A second call center is to be established at a secondary location that will be accessing our DATA over a Private T1. We currently use MSAccess in a true client to sever architect, MSSQL2000 being the server. Every client has a local copy of the "front-end" (MSAccess2000) and uses a local system DNS to access our SQL server over the LAN. Originally I thought we could simply use VPN over the T1 and therefore the DNS on the secondary call centers machines would continue to work as our do on the LAN.

However, security issues being a concern, we have decided to move a second MSSQL server outside of our Domain on a separate segment. VPN is unnecessary over the private T1 and using this logic, every workstation would have to run a VPN from their client. Not such a great plan.

There has to be a better way. Any advice out there on what direction I should take?

 

[terosoft]

Maybe you can use IP tunneling instead.

Check this:

http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_zebedee

Although this example is for an Interbase/Firebird database, the program being used seems to work with anything.



Gerardo Czajkowski