By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,225 Members | 1,051 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,225 IT Pros & Developers. It's quick & easy.

Slow connect to local server if VPN active

P: n/a
Does anyone know how to solve this?

I am running IBM DB2 on a Linux server on a private LAN.
I am accessing it via ODBC from a Windows 2000 client
I also use the Windows 2000 machine as a VPN client
If the VPN client is not active then the Windows 2000 machine can
connect quickly to the server.
However if the VPN client is active then it seems to take forever for
the Windows 2000 machine to connect to the server.
The server is specified as a static ip address (192.168.n.n)

Any ideas?

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies

P: n/a
I've been having a lot of trouble with VPNs lately in similar
situations. I had a network engineer buddy of mine explain to me that
most VPNs have some type of firewall built into them, and the firewalls
cause both long waits and "you can't get there from here" problems.

Which VPN are you using? Does it have a built in firewall?

Nov 12 '05 #2

P: n/a
Hi Lou, thanks for the response

No idea what VPN it is; it's the standard Microsoft one that is within
Microsoft Windows 2000. It probably does include a firewall, I guess.
My point is that I don't understand why the VPN is even being included
in the conversation when I have told DB2 the static IP address on the
LOCAL network; why is it even talking to the WAN?

Nov 12 '05 #3

P: n/a
Windows 2000 is good news. Windows XP with SP2 installed will make your
hair grey or fall off your head.

When you fire up the VPN it starts trying to tunnel everything TCP/IP.
With the Windows 2000 version you can bypass with a proxy. Have a look
at this:

Internet options (reachable from IE Tools, Internet options or from
your Windows settings menu).
Tab: Connections
Button: LAN Settings

You can set a proxy server for your LAN traffic.

The approach I use on XP is to install the ancient NetBEUI protocol on
all PCs and allow my mapped drives, etc. to communicate via it instead
of TCP/IP. Obviously this is not an approach for your ODBC connection
to Linux, but at least my PCs can talk to each other with all these
bloody firewalls.

Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.