Problems with network when dialed up

[Kyle Dillard]

Ok, ran into a weird situation last week that I've seen
several times before and now I'm curious.

I have a user on the LAN that sometimes dials up to
another network via a program called PAL. As soon as the
user connects, all local LAN traffic dies.... so she cant
print.

I've noticed there is a "USE DEFAULT GATEWAY ON REMOTE
NETWORK" under the dialup adapters TCP/IP options. When
I uncheck that I can print now but the program I launch
on the DIALUP side dies? Any ideas?

 

[SteveC]

Ok, ran into a weird situation last week that I've seen
several times before and now I'm curious.

I have a user on the LAN that sometimes dials up to
another network via a program called PAL. As soon as the
user connects, all local LAN traffic dies.... so she cant
print.

I've noticed there is a "USE DEFAULT GATEWAY ON REMOTE
NETWORK" under the dialup adapters TCP/IP options. When
I uncheck that I can print now but the program I launch
on the DIALUP side dies? Any ideas?

Hello,

In a nutshell, you're trying to connect to network A, and the default
gateway used isn't aware of network A, so the connection fails.

The remote default gateway isn't aware of your LAN, so won't tell the
PC how to reach resources on your network.

Your default gateway isn't aware of the remote LAN, so won't tell the
PC how to reach the remote network.

It may be possible to resolve this by defining static routes on the
PC. It depends on the network addressing schemes used in the local
network and the remote network

regards,

SteveC
======
If at first you don't succeed, forget skydiving