VPN and SQL

We have Windows 2003 STD server as a VPN server but we
have separate SQL server running on Windows NT. we have
two remote office which have to be connected to to the
database server via the VPN server.

We have develop a system that uses Sql Server 7.0 as
database.

details are as follows:

TCLSERVER = Database server running on NT
(Not physically connected to internet with
internal 101.101.0.1)

MailServer (domain=TCLMAilServer) = VPN Server
(Physicall connected to internet with address
203.160.172.232)

We have to remote office PC running Win XP pro connected
to internet via DSL with Static IP.

We install the developed system to the remote office
however we cannot use them because the database is in the
main office.

can you suggest options/solutions.

thanks!

If you already have a VPN server set up you can just set up a vpn connection from the xp clients at the remote office to connect to the VPN server at the main office. They will then be able to use the database but it's probably going to be sloooooow. A hardware VPN solution such as a SonicWall would help the speed depending on your ISP speed. A Terminal Server at the main office would be your best bet for database applications run remotely. If using the windows VPN scenario you will want to make a change to allow your remote users to still access the internet through their regular ISP while the VPN is active. Configure the VPN then go to it's properties, networking tab, TCP/IP, then click advanced. Uncheck "use default gateway on remote network checkbox"

Bradley Fox
Sr. Network Administrator
MCSE - W2K

>>> disk0nek<(E-Mail Removed)> 07/29/04 01:57AM >>>
We have Windows 2003 STD server as a VPN server but we
have separate SQL server running on Windows NT. we have
two remote office which have to be connected to to the
database server via the VPN server.

We have develop a system that uses Sql Server 7.0 as
database.

details are as follows:

TCLSERVER = Database server running on NT
(Not physically connected to internet with
internal 101.101.0.1)

MailServer (domain=TCLMAilServer) = VPN Server
(Physicall connected to internet with address
203.160.172.232)

We have to remote office PC running Win XP pro connected
to internet via DSL with Static IP.

We install the developed system to the remote office
however we cannot use them because the database is in the
main office.

can you suggest options/solutions.

thanks!

"disk0nek" <(E-Mail Removed)> wrote in message
news:64d601c47530$e41b7060$(E-Mail Removed)...
> have separate SQL server running on Windows NT. we have
> two remote office which have to be connected to to the
> database server via the VPN server.

> TCLSERVER = Database server running on NT
> (Not physically connected to internet with
> internal 101.101.0.1)
> We have to remote office PC running Win XP pro connected
> to internet via DSL with Static IP.
>
> We install the developed system to the remote office
> however we cannot use them because the database is in the
> main office.

When you bring the VPN up, the client simply accesses the SQL by the IP# of
the SQL Server. VPN works the same as if it was on the local LAN in this
respect. There are of course ways to get naming to work, but using the IP#
is by far the most dependable.

BTW - The IP# of the SQL Server (101.101.0.1) that you are using as a
private IP# is not an RFC Private Address. If you do not legitimately own
this address set then you may have problems in other situations later on
because you have created an "address conflict" situation between the private
side of your system and whoever actually owns that address out on the
Internet. It is very possible that this will hamper your efforts in this
situation because the "remote client" you are using *is* on the Internet and
is trying to connect to an address that is "expected" to be out in
"Internet-land" rather than on a private system.

I don't know enough about your system's design to be any more specific than
that.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com