Re: Problems w. VPN connection over T-1

I think Megapath's address space is /24 for this T-1

Tunnel is established via Microsoft VPN

This is of the Cali Office
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.10.5 192.168.10.1 20
XX.XX.XX.XXX 255.255.255.255 192.168.10.5 192.168.10.1 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.10.0 255.255.255.0 192.168.10.1 192.168.10.1 20
192.168.10.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.10.16 255.255.255.255 192.168.10.20 192.168.10.20 1
192.168.10.17 255.255.255.255 192.168.10.20 192.168.10.20 1
192.168.10.18 255.255.255.255 192.168.10.20 192.168.10.20 1
192.168.10.19 255.255.255.255 192.168.10.20 192.168.10.20 1
192.168.10.20 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.10.255 255.255.255.255 192.168.10.1 192.168.10.1 20
224.0.0.0 240.0.0.0 192.168.10.1 192.168.10.1 20
255.255.255.255 255.255.255.255 192.168.10.1 192.168.10.1 1
Default Gateway: 192.168.10.5

"Asher_N" wrote:

> What is the address spece of the other office?
>
> How is the tunnel established?
>
> What do the routing tables look like?
>
>
>
> "=?Utf-8?B?QWRhbQ==?=" <Adam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> news:67FA25DA-9CA5-44D0-B3CB-2C466028324E@xxxxxxxxxxxxx:
>
> > I just setup two networks (one in Cali and the other in Mass). Both
> > networks are on T1 lines. The Mass company VPNs into the Cali office
> > to access the files and Exchange. There are 7 users in the Mass
> > office. The main problem is that when they try to use Outlook it
> > always says "Exchange is unavailable" the first time and then takes
> > 3-5 minutes to load up into Outlook if I end up clicking "Retry", but
> > this is not always the case.
> >
> > When I ping the main server NETBIOS name while I am VPN'd into it, it
> > will give me the public IP. I added a host file entry for the NETBIOS
> > name to point directly to the LAN IP. However, of course, when I check
> > the name it shows the FQDN (and since the Cali server hosts their own
> > e-mail) it will point back to the public IP it seems.
> >
> > Is there a way to correct this problem? I know that RPC always worked
> > faster before it was blocked. RPC over HTTPS is problematic since they
> > always have to login. It seems when I do other VPNs into Outlook its a
> > bit faster. Any suggestions would be appreciated...
> >
> > NETBIOS name: server1
> > FQDN: server1.domain.com
> >
> > Private scheme: 192.168.10.1 - 192.168.10.254
> > server1 IP: 192.168.10.1
> > router IP: 192.168.10.5
> >
> > Ports: 80, 443, 25, 110, and 1723 are open
> >
>
>
.

Loading