Possible Routing Issues...

We have many Windows 2003 and Windows 2000 Servers. We have 3 sites, labeled
Corp, A and B.

Our problem is that everyone once in a while, about 1 time a week or so,
sites A and B will be unable to reach some or all of our servers. If Corp
connects to that server and pings to site A and B then A and B can connect.

Any ideas. All of our routing looks good, but maybe not.

hi,
it seems that you have some vpn connection on Corp ->A and Corp ->B with
dial on demand interface wich is configured to demand dial only from Corp.
--
Dragos CAMARA
MCSA Windows 2003 server


"icestormz" wrote:

> We have many Windows 2003 and Windows 2000 Servers. We have 3 sites, labeled
> Corp, A and B.
>
> Our problem is that everyone once in a while, about 1 time a week or so,
> sites A and B will be unable to reach some or all of our servers. If Corp
> connects to that server and pings to site A and B then A and B can connect.
>
> Any ideas. All of our routing looks good, but maybe not.

If your using VPN make sure keep alives are enabled.

I had that problem with VOIP.
I would go to make a call and the VPN wouldn't be up.
Keep alives keep the VPN tunnels up.

"Dragos CAMARA" wrote:

> hi,
> it seems that you have some vpn connection on Corp ->A and Corp ->B with
> dial on demand interface wich is configured to demand dial only from Corp.
> --
> Dragos CAMARA
> MCSA Windows 2003 server
>
>
> "icestormz" wrote:
>
> > We have many Windows 2003 and Windows 2000 Servers. We have 3 sites, labeled
> > Corp, A and B.
> >
> > Our problem is that everyone once in a while, about 1 time a week or so,
> > sites A and B will be unable to reach some or all of our servers. If Corp
> > connects to that server and pings to site A and B then A and B can connect.
> >
> > Any ideas. All of our routing looks good, but maybe not.