Slow local performance on remote VPN site

WS2003 domain, 2 AD Sites connected by new site-to-site RRAS L2TP/IPSec VPN.
Main office endpoint is ISA2004 on WS2003 R2, branch office endpoint is
WS2003 R2 SP2. Each site has (at least 1) DC & DNS server. At (small) branch
office, these are on the RRAS server.

When branch office server was on the main office's LAN, it was as fast as
any other similar machine on the network. Once it was on its own AD site,
with only a VPN connection, the server became very slow. Even browsing local
drives on that server takes a long time. Can take a couple minutes for
Explorer to move from a folder to a subfolder.

Performance aside, we have connectivity between the 2 sites.

Other, likely-related symptoms: DFS referrals that should go to the branch
office server often go to the main office servers. Roaming profiles, which
should be loading from a local copy of a DFSR-replicated user profile share,
load only the cached copy. If you look in System Properties/Advanced/User
Profiles, Type is "Roaming" but Status is "Local". In DNS, AD Sites &
Services, and querying WMI, branch office server and its clients are in the
correct AD Site.

Nothing in Event Logs that points me to the cause.

My gut tells me this is a routing problem. I'm not catching it, but maybe I
don't know what I'm looking for.

Main office LAN: 192.168.0.x
Main office internal IP: 192.168.0.234
Main office VPN interface: 172.16.100.222
Main office external IP (on perimeter network) 192.168.1.101

Branch office internal IP: 10.10.11.221
Branch office LAN: 10.10.11.x
Branch office VPN interface: 172.16.100.223

Here are the routing tables from both RRAS servers:

Main office--

IPv4 Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 12 17 5a ad 77 ...... Linksys EG1032 v3 Instant Gigabit Desktop
Network Adapter Driver - Packet Scheduler Miniport
0x10004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x30003 ...00 0f 1f f8 c2 c0 ...... Intel(R) PRO/1000 MT Network
Connection - Packet Scheduler Miniport
0x40006 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 20
[VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
10.10.11.0 255.255.255.0 0.0.0.0 172.16.100.223 1
10.10.11.0 255.255.255.0 172.16.100.222 172.16.100.223 1
[VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
[VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
[VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101
20
[Branch Office Ext IP] 255.255.255.255 192.168.1.1
192.168.1.101 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.16.0.1 255.255.255.255 127.0.0.1 127.0.0.1 50
172.16.0.2 255.255.255.255 172.16.0.1 172.16.0.1 1
172.16.0.5 255.255.255.255 172.16.0.1 172.16.0.1 1
172.16.0.6 255.255.255.255 172.16.0.1 172.16.0.1 1
172.16.0.14 255.255.255.255 172.16.0.1 172.16.0.1 1
172.16.0.17 255.255.255.255 172.16.0.1 172.16.0.1 1
172.16.100.222 255.255.255.255 172.16.100.223 172.16.100.223 1
172.16.100.223 255.255.255.255 127.0.0.1 127.0.0.1 50
172.16.255.255 255.255.255.255 172.16.100.223 172.16.100.223 50
192.168.0.0 255.255.255.0 192.168.0.234 192.168.0.234 10
192.168.0.234 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.0.255 255.255.255.255 192.168.0.234 192.168.0.234 10
192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 20
192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101 20
[VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
224.0.0.0 240.0.0.0 172.16.100.223 172.16.100.223 50
224.0.0.0 240.0.0.0 192.168.0.234 192.168.0.234 10
224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101 20
255.255.255.255 255.255.255.255 172.16.100.223 172.16.100.223 1
255.255.255.255 255.255.255.255 192.168.0.234 192.168.0.234 1
255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101 1
Default Gateway: 192.168.1.1
================================================== =========================
Persistent Routes:
None


Branch Office--

IPv4 Route Table
================================================== =========================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x10003 ...00 04 23 bd 5d a4 ...... Intel(R) PRO/1000 MT Dual Port Server
Adapter
0x10004 ...00 0d 56 fe 01 b5 ...... Intel(R) PRO/1000 XT Network Connection
0x20005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
================================================== =========================
================================================== =========================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 [ExternalDG] [ExternalIP] 20
10.2.0.0 255.255.255.0 172.16.100.223 172.16.100.222 1
10.10.11.0 255.255.255.0 10.10.11.221 10.10.11.221 20
10.10.11.5 255.255.255.255 127.0.0.1 127.0.0.1 50
10.10.11.221 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.10.11.221 10.10.11.221 20
[ExternalIPBlock] 255.255.255.0 [ExternalIP] [ExternalIP]
20
[ExternalIP] 255.255.255.255 127.0.0.1 127.0.0.1 20
xx.255.255.255 255.255.255.255 [ExternalIP] [ExternalIP] 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
172.16.100.222 255.255.255.255 127.0.0.1 127.0.0.1 50
172.16.100.223 255.255.255.255 172.16.100.222 172.16.100.222 1
172.16.255.255 255.255.255.255 172.16.100.222 172.16.100.222 50
192.168.0.0 255.255.255.0 172.16.100.223 172.16.100.222 1
[MainOfficeExtIP] 255.255.255.255 [ExtDG] [ExtIP] 20
224.0.0.0 240.0.0.0 10.10.11.221 10.10.11.221 20
224.0.0.0 240.0.0.0 [ExtIP] [ExtIP] 20
224.0.0.0 240.0.0.0 172.16.100.222 172.16.100.222 50
255.255.255.255 255.255.255.255 10.10.11.221 10.10.11.221 1
255.255.255.255 255.255.255.255 [ExtIP] [ExtIP] 1
255.255.255.255 255.255.255.255 172.16.100.222 172.16.100.222 1
Default Gateway: [ExtDG]
================================================== =========================
Persistent Routes:
None

TIA!

--
Jeff Vandervoort
JRVsystems




Jeff Vandervoort

This post has the same issue,

Solved: slow network performance over wan
http://chicagotech.net/netforums/viewtopic.php?t=712

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Jeff Vandervoort" <jeffv @ jrvsystems dot com> wrote in message
news:(E-Mail Removed)...
> WS2003 domain, 2 AD Sites connected by new site-to-site RRAS L2TP/IPSec
> VPN. Main office endpoint is ISA2004 on WS2003 R2, branch office endpoint
> is WS2003 R2 SP2. Each site has (at least 1) DC & DNS server. At (small)
> branch office, these are on the RRAS server.
>
> When branch office server was on the main office's LAN, it was as fast as
> any other similar machine on the network. Once it was on its own AD site,
> with only a VPN connection, the server became very slow. Even browsing
> local drives on that server takes a long time. Can take a couple minutes
> for Explorer to move from a folder to a subfolder.
>
> Performance aside, we have connectivity between the 2 sites.
>
> Other, likely-related symptoms: DFS referrals that should go to the branch
> office server often go to the main office servers. Roaming profiles, which
> should be loading from a local copy of a DFSR-replicated user profile
> share, load only the cached copy. If you look in System
> Properties/Advanced/User Profiles, Type is "Roaming" but Status is
> "Local". In DNS, AD Sites & Services, and querying WMI, branch office
> server and its clients are in the correct AD Site.
>
> Nothing in Event Logs that points me to the cause.
>
> My gut tells me this is a routing problem. I'm not catching it, but maybe
> I don't know what I'm looking for.
>
> Main office LAN: 192.168.0.x
> Main office internal IP: 192.168.0.234
> Main office VPN interface: 172.16.100.222
> Main office external IP (on perimeter network) 192.168.1.101
>
> Branch office internal IP: 10.10.11.221
> Branch office LAN: 10.10.11.x
> Branch office VPN interface: 172.16.100.223
>
> Here are the routing tables from both RRAS servers:
>
> Main office--
>
> IPv4 Route Table
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 12 17 5a ad 77 ...... Linksys EG1032 v3 Instant Gigabit Desktop
> Network Adapter Driver - Packet Scheduler Miniport
> 0x10004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> 0x30003 ...00 0f 1f f8 c2 c0 ...... Intel(R) PRO/1000 MT Network
> Connection - Packet Scheduler Miniport
> 0x40006 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> ================================================== =========================
> ================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101 20
> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101
> 20
> 10.10.11.0 255.255.255.0 0.0.0.0 172.16.100.223 1
> 10.10.11.0 255.255.255.0 172.16.100.222 172.16.100.223 1
> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101
> 20
> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
> [Branch Office Ext IP] 255.255.255.255 192.168.1.1 192.168.1.101
> 20
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 172.16.0.1 255.255.255.255 127.0.0.1 127.0.0.1 50
> 172.16.0.2 255.255.255.255 172.16.0.1 172.16.0.1 1
> 172.16.0.5 255.255.255.255 172.16.0.1 172.16.0.1 1
> 172.16.0.6 255.255.255.255 172.16.0.1 172.16.0.1 1
> 172.16.0.14 255.255.255.255 172.16.0.1 172.16.0.1 1
> 172.16.0.17 255.255.255.255 172.16.0.1 172.16.0.1 1
> 172.16.100.222 255.255.255.255 172.16.100.223 172.16.100.223 1
> 172.16.100.223 255.255.255.255 127.0.0.1 127.0.0.1 50
> 172.16.255.255 255.255.255.255 172.16.100.223 172.16.100.223 50
> 192.168.0.0 255.255.255.0 192.168.0.234 192.168.0.234 10
> 192.168.0.234 255.255.255.255 127.0.0.1 127.0.0.1 10
> 192.168.0.255 255.255.255.255 192.168.0.234 192.168.0.234 10
> 192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101 20
> 192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1 20
> 192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101 20
> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
> 224.0.0.0 240.0.0.0 172.16.100.223 172.16.100.223 50
> 224.0.0.0 240.0.0.0 192.168.0.234 192.168.0.234 10
> 224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101 20
> 255.255.255.255 255.255.255.255 172.16.100.223 172.16.100.223 1
> 255.255.255.255 255.255.255.255 192.168.0.234 192.168.0.234 1
> 255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101 1
> Default Gateway: 192.168.1.1
> ================================================== =========================
> Persistent Routes:
> None
>
>
> Branch Office--
>
> IPv4 Route Table
> ================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> 0x10003 ...00 04 23 bd 5d a4 ...... Intel(R) PRO/1000 MT Dual Port Server
> Adapter
> 0x10004 ...00 0d 56 fe 01 b5 ...... Intel(R) PRO/1000 XT Network
> Connection
> 0x20005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> ================================================== =========================
> ================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 [ExternalDG] [ExternalIP] 20
> 10.2.0.0 255.255.255.0 172.16.100.223 172.16.100.222 1
> 10.10.11.0 255.255.255.0 10.10.11.221 10.10.11.221 20
> 10.10.11.5 255.255.255.255 127.0.0.1 127.0.0.1 50
> 10.10.11.221 255.255.255.255 127.0.0.1 127.0.0.1 20
> 10.255.255.255 255.255.255.255 10.10.11.221 10.10.11.221 20
> [ExternalIPBlock] 255.255.255.0 [ExternalIP] [ExternalIP]
> 20
> [ExternalIP] 255.255.255.255 127.0.0.1 127.0.0.1 20
> xx.255.255.255 255.255.255.255 [ExternalIP] [ExternalIP] 20
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 172.16.100.222 255.255.255.255 127.0.0.1 127.0.0.1 50
> 172.16.100.223 255.255.255.255 172.16.100.222 172.16.100.222 1
> 172.16.255.255 255.255.255.255 172.16.100.222 172.16.100.222 50
> 192.168.0.0 255.255.255.0 172.16.100.223 172.16.100.222 1
> [MainOfficeExtIP] 255.255.255.255 [ExtDG] [ExtIP] 20
> 224.0.0.0 240.0.0.0 10.10.11.221 10.10.11.221 20
> 224.0.0.0 240.0.0.0 [ExtIP] [ExtIP] 20
> 224.0.0.0 240.0.0.0 172.16.100.222 172.16.100.222 50
> 255.255.255.255 255.255.255.255 10.10.11.221 10.10.11.221 1
> 255.255.255.255 255.255.255.255 [ExtIP] [ExtIP] 1
> 255.255.255.255 255.255.255.255 172.16.100.222 172.16.100.222 1
> Default Gateway: [ExtDG]
> ================================================== =========================
> Persistent Routes:
> None
>
> TIA!
>
> --
> Jeff Vandervoort
> JRVsystems
>

Thanks, but actually, that's not the same issue at all. It's certainly not
the same symptoms.

Performance across the WAN is normal (considering available bandwidth).
Performance on the remote LAN is the problem, along with performance on the
local server. It can take a couple MINUTES to open a folder on the local
drive of the server, while logged on to the console of the server.

But only when the server is on the remote site. When it's on the main office
site, performance, including local file access, is normal. When the machine
is moved to the remote site, and the VPN link is introduced, the problem is
LOCAL performance on the remote site.

--
Jeff Vandervoort
JRVsystems
"Robert L (MS-MVP)" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> This post has the same issue,
>
> Solved: slow network performance over wan
> http://chicagotech.net/netforums/viewtopic.php?t=712
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Jeff Vandervoort" <jeffv @ jrvsystems dot com> wrote in message
> news:(E-Mail Removed)...
>> WS2003 domain, 2 AD Sites connected by new site-to-site RRAS L2TP/IPSec
>> VPN. Main office endpoint is ISA2004 on WS2003 R2, branch office endpoint
>> is WS2003 R2 SP2. Each site has (at least 1) DC & DNS server. At (small)
>> branch office, these are on the RRAS server.
>>
>> When branch office server was on the main office's LAN, it was as fast as
>> any other similar machine on the network. Once it was on its own AD site,
>> with only a VPN connection, the server became very slow. Even browsing
>> local drives on that server takes a long time. Can take a couple minutes
>> for Explorer to move from a folder to a subfolder.
>>
>> Performance aside, we have connectivity between the 2 sites.
>>
>> Other, likely-related symptoms: DFS referrals that should go to the
>> branch office server often go to the main office servers. Roaming
>> profiles, which should be loading from a local copy of a DFSR-replicated
>> user profile share, load only the cached copy. If you look in System
>> Properties/Advanced/User Profiles, Type is "Roaming" but Status is
>> "Local". In DNS, AD Sites & Services, and querying WMI, branch office
>> server and its clients are in the correct AD Site.
>>
>> Nothing in Event Logs that points me to the cause.
>>
>> My gut tells me this is a routing problem. I'm not catching it, but maybe
>> I don't know what I'm looking for.
>>
>> Main office LAN: 192.168.0.x
>> Main office internal IP: 192.168.0.234
>> Main office VPN interface: 172.16.100.222
>> Main office external IP (on perimeter network) 192.168.1.101
>>
>> Branch office internal IP: 10.10.11.221
>> Branch office LAN: 10.10.11.x
>> Branch office VPN interface: 172.16.100.223
>>
>> Here are the routing tables from both RRAS servers:
>>
>> Main office--
>>
>> IPv4 Route Table
>> ================================================== =========================
>> Interface List
>> 0x1 ........................... MS TCP Loopback interface
>> 0x2 ...00 12 17 5a ad 77 ...... Linksys EG1032 v3 Instant Gigabit Desktop
>> Network Adapter Driver - Packet Scheduler Miniport
>> 0x10004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>> 0x30003 ...00 0f 1f f8 c2 c0 ...... Intel(R) PRO/1000 MT Network
>> Connection - Packet Scheduler Miniport
>> 0x40006 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>> ================================================== =========================
>> ================================================== =========================
>> Active Routes:
>> Network Destination Netmask Gateway Interface
>> Metric
>> 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101
>> 20
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
>> 10.10.11.0 255.255.255.0 0.0.0.0 172.16.100.223
>> 1
>> 10.10.11.0 255.255.255.0 172.16.100.222 172.16.100.223
>> 1
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
>> [Branch Office Ext IP] 255.255.255.255 192.168.1.1
>> 192.168.1.101 20
>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>> 1
>> 172.16.0.1 255.255.255.255 127.0.0.1 127.0.0.1
>> 50
>> 172.16.0.2 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.0.5 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.0.6 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.0.14 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.0.17 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.100.222 255.255.255.255 172.16.100.223 172.16.100.223
>> 1
>> 172.16.100.223 255.255.255.255 127.0.0.1 127.0.0.1
>> 50
>> 172.16.255.255 255.255.255.255 172.16.100.223 172.16.100.223
>> 50
>> 192.168.0.0 255.255.255.0 192.168.0.234 192.168.0.234
>> 10
>> 192.168.0.234 255.255.255.255 127.0.0.1 127.0.0.1
>> 10
>> 192.168.0.255 255.255.255.255 192.168.0.234 192.168.0.234
>> 10
>> 192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101
>> 20
>> 192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1
>> 20
>> 192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101
>> 20
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101
>> 20
>> 224.0.0.0 240.0.0.0 172.16.100.223 172.16.100.223
>> 50
>> 224.0.0.0 240.0.0.0 192.168.0.234 192.168.0.234
>> 10
>> 224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101
>> 20
>> 255.255.255.255 255.255.255.255 172.16.100.223 172.16.100.223
>> 1
>> 255.255.255.255 255.255.255.255 192.168.0.234 192.168.0.234
>> 1
>> 255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101
>> 1
>> Default Gateway: 192.168.1.1
>> ================================================== =========================
>> Persistent Routes:
>> None
>>
>>
>> Branch Office--
>>
>> IPv4 Route Table
>> ================================================== =========================
>> Interface List
>> 0x1 ........................... MS TCP Loopback interface
>> 0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>> 0x10003 ...00 04 23 bd 5d a4 ...... Intel(R) PRO/1000 MT Dual Port Server
>> Adapter
>> 0x10004 ...00 0d 56 fe 01 b5 ...... Intel(R) PRO/1000 XT Network
>> Connection
>> 0x20005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>> ================================================== =========================
>> ================================================== =========================
>> Active Routes:
>> Network Destination Netmask Gateway Interface
>> Metric
>> 0.0.0.0 0.0.0.0 [ExternalDG] [ExternalIP]
>> 20
>> 10.2.0.0 255.255.255.0 172.16.100.223 172.16.100.222
>> 1
>> 10.10.11.0 255.255.255.0 10.10.11.221 10.10.11.221
>> 20
>> 10.10.11.5 255.255.255.255 127.0.0.1 127.0.0.1
>> 50
>> 10.10.11.221 255.255.255.255 127.0.0.1 127.0.0.1
>> 20
>> 10.255.255.255 255.255.255.255 10.10.11.221 10.10.11.221
>> 20
>> [ExternalIPBlock] 255.255.255.0 [ExternalIP]
>> [ExternalIP] 20
>> [ExternalIP] 255.255.255.255 127.0.0.1 127.0.0.1
>> 20
>> xx.255.255.255 255.255.255.255 [ExternalIP] [ExternalIP]
>> 20
>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>> 1
>> 172.16.100.222 255.255.255.255 127.0.0.1 127.0.0.1
>> 50
>> 172.16.100.223 255.255.255.255 172.16.100.222 172.16.100.222
>> 1
>> 172.16.255.255 255.255.255.255 172.16.100.222 172.16.100.222
>> 50
>> 192.168.0.0 255.255.255.0 172.16.100.223 172.16.100.222
>> 1
>> [MainOfficeExtIP] 255.255.255.255 [ExtDG] [ExtIP] 20
>> 224.0.0.0 240.0.0.0 10.10.11.221 10.10.11.221
>> 20
>> 224.0.0.0 240.0.0.0 [ExtIP] [ExtIP] 20
>> 224.0.0.0 240.0.0.0 172.16.100.222 172.16.100.222
>> 50
>> 255.255.255.255 255.255.255.255 10.10.11.221 10.10.11.221
>> 1
>> 255.255.255.255 255.255.255.255 [ExtIP] [ExtIP] 1
>> 255.255.255.255 255.255.255.255 172.16.100.222 172.16.100.222
>> 1
>> Default Gateway: [ExtDG]
>> ================================================== =========================
>> Persistent Routes:
>> None
>>
>> TIA!
>>
>> --
>> Jeff Vandervoort
>> JRVsystems
>>
>
>

Didn't get to spend any time on this today, but have some more symptoms--

There are NO clients on the remote site at this time. Yesterday, Sunday,
there were very few clients at either site. Yet ISA reports showed 100MB of
data transferred from the branch office to the main office, and about 5 MB
from main office to branch office.

Branch office server provides NO services to main office, but it does have
several DFS/DFSR shares. Strong suspicion is that DFS referrals for user
profiles or LiveUpdate (only things I can think of off-hand that would have
changed over the weekend) from the main office were going to the branch
office.

DFSR shares changed on Sunday at the main office, but any traffic should
have been in the other direction--replicating main office changes back to
branch office.

Also had some extremely slow performance issues at the main office today
during user logons that seemed to clear up when I disconnected the
site-to-site VPN. Had a user report that the problem was evident Friday,
though I was not aware of it then. However, we've not had slow response of
Explorer on local drive accesses at the main office that I'm aware of, as we
had on the remote site.

--
Jeff Vandervoort
JRVsystems
"Robert L (MS-MVP)" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> This post has the same issue,
>
> Solved: slow network performance over wan
> http://chicagotech.net/netforums/viewtopic.php?t=712
>
> --
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on
> http://www.HowToNetworking.com
> "Jeff Vandervoort" <jeffv @ jrvsystems dot com> wrote in message
> news:(E-Mail Removed)...
>> WS2003 domain, 2 AD Sites connected by new site-to-site RRAS L2TP/IPSec
>> VPN. Main office endpoint is ISA2004 on WS2003 R2, branch office endpoint
>> is WS2003 R2 SP2. Each site has (at least 1) DC & DNS server. At (small)
>> branch office, these are on the RRAS server.
>>
>> When branch office server was on the main office's LAN, it was as fast as
>> any other similar machine on the network. Once it was on its own AD site,
>> with only a VPN connection, the server became very slow. Even browsing
>> local drives on that server takes a long time. Can take a couple minutes
>> for Explorer to move from a folder to a subfolder.
>>
>> Performance aside, we have connectivity between the 2 sites.
>>
>> Other, likely-related symptoms: DFS referrals that should go to the
>> branch office server often go to the main office servers. Roaming
>> profiles, which should be loading from a local copy of a DFSR-replicated
>> user profile share, load only the cached copy. If you look in System
>> Properties/Advanced/User Profiles, Type is "Roaming" but Status is
>> "Local". In DNS, AD Sites & Services, and querying WMI, branch office
>> server and its clients are in the correct AD Site.
>>
>> Nothing in Event Logs that points me to the cause.
>>
>> My gut tells me this is a routing problem. I'm not catching it, but maybe
>> I don't know what I'm looking for.
>>
>> Main office LAN: 192.168.0.x
>> Main office internal IP: 192.168.0.234
>> Main office VPN interface: 172.16.100.222
>> Main office external IP (on perimeter network) 192.168.1.101
>>
>> Branch office internal IP: 10.10.11.221
>> Branch office LAN: 10.10.11.x
>> Branch office VPN interface: 172.16.100.223
>>
>> Here are the routing tables from both RRAS servers:
>>
>> Main office--
>>
>> IPv4 Route Table
>> ================================================== =========================
>> Interface List
>> 0x1 ........................... MS TCP Loopback interface
>> 0x2 ...00 12 17 5a ad 77 ...... Linksys EG1032 v3 Instant Gigabit Desktop
>> Network Adapter Driver - Packet Scheduler Miniport
>> 0x10004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>> 0x30003 ...00 0f 1f f8 c2 c0 ...... Intel(R) PRO/1000 MT Network
>> Connection - Packet Scheduler Miniport
>> 0x40006 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>> ================================================== =========================
>> ================================================== =========================
>> Active Routes:
>> Network Destination Netmask Gateway Interface
>> Metric
>> 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.101
>> 20
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
>> 10.10.11.0 255.255.255.0 0.0.0.0 172.16.100.223
>> 1
>> 10.10.11.0 255.255.255.0 172.16.100.222 172.16.100.223
>> 1
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101 20
>> [Branch Office Ext IP] 255.255.255.255 192.168.1.1
>> 192.168.1.101 20
>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>> 1
>> 172.16.0.1 255.255.255.255 127.0.0.1 127.0.0.1
>> 50
>> 172.16.0.2 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.0.5 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.0.6 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.0.14 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.0.17 255.255.255.255 172.16.0.1 172.16.0.1
>> 1
>> 172.16.100.222 255.255.255.255 172.16.100.223 172.16.100.223
>> 1
>> 172.16.100.223 255.255.255.255 127.0.0.1 127.0.0.1
>> 50
>> 172.16.255.255 255.255.255.255 172.16.100.223 172.16.100.223
>> 50
>> 192.168.0.0 255.255.255.0 192.168.0.234 192.168.0.234
>> 10
>> 192.168.0.234 255.255.255.255 127.0.0.1 127.0.0.1
>> 10
>> 192.168.0.255 255.255.255.255 192.168.0.234 192.168.0.234
>> 10
>> 192.168.1.0 255.255.255.0 192.168.1.101 192.168.1.101
>> 20
>> 192.168.1.101 255.255.255.255 127.0.0.1 127.0.0.1
>> 20
>> 192.168.1.255 255.255.255.255 192.168.1.101 192.168.1.101
>> 20
>> [VPNClientIP] 255.255.255.255 192.168.1.1 192.168.1.101
>> 20
>> 224.0.0.0 240.0.0.0 172.16.100.223 172.16.100.223
>> 50
>> 224.0.0.0 240.0.0.0 192.168.0.234 192.168.0.234
>> 10
>> 224.0.0.0 240.0.0.0 192.168.1.101 192.168.1.101
>> 20
>> 255.255.255.255 255.255.255.255 172.16.100.223 172.16.100.223
>> 1
>> 255.255.255.255 255.255.255.255 192.168.0.234 192.168.0.234
>> 1
>> 255.255.255.255 255.255.255.255 192.168.1.101 192.168.1.101
>> 1
>> Default Gateway: 192.168.1.1
>> ================================================== =========================
>> Persistent Routes:
>> None
>>
>>
>> Branch Office--
>>
>> IPv4 Route Table
>> ================================================== =========================
>> Interface List
>> 0x1 ........................... MS TCP Loopback interface
>> 0x10002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>> 0x10003 ...00 04 23 bd 5d a4 ...... Intel(R) PRO/1000 MT Dual Port Server
>> Adapter
>> 0x10004 ...00 0d 56 fe 01 b5 ...... Intel(R) PRO/1000 XT Network
>> Connection
>> 0x20005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>> ================================================== =========================
>> ================================================== =========================
>> Active Routes:
>> Network Destination Netmask Gateway Interface
>> Metric
>> 0.0.0.0 0.0.0.0 [ExternalDG] [ExternalIP]
>> 20
>> 10.2.0.0 255.255.255.0 172.16.100.223 172.16.100.222
>> 1
>> 10.10.11.0 255.255.255.0 10.10.11.221 10.10.11.221
>> 20
>> 10.10.11.5 255.255.255.255 127.0.0.1 127.0.0.1
>> 50
>> 10.10.11.221 255.255.255.255 127.0.0.1 127.0.0.1
>> 20
>> 10.255.255.255 255.255.255.255 10.10.11.221 10.10.11.221
>> 20
>> [ExternalIPBlock] 255.255.255.0 [ExternalIP]
>> [ExternalIP] 20
>> [ExternalIP] 255.255.255.255 127.0.0.1 127.0.0.1
>> 20
>> xx.255.255.255 255.255.255.255 [ExternalIP] [ExternalIP]
>> 20
>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>> 1
>> 172.16.100.222 255.255.255.255 127.0.0.1 127.0.0.1
>> 50
>> 172.16.100.223 255.255.255.255 172.16.100.222 172.16.100.222
>> 1
>> 172.16.255.255 255.255.255.255 172.16.100.222 172.16.100.222
>> 50
>> 192.168.0.0 255.255.255.0 172.16.100.223 172.16.100.222
>> 1
>> [MainOfficeExtIP] 255.255.255.255 [ExtDG] [ExtIP] 20
>> 224.0.0.0 240.0.0.0 10.10.11.221 10.10.11.221
>> 20
>> 224.0.0.0 240.0.0.0 [ExtIP] [ExtIP] 20
>> 224.0.0.0 240.0.0.0 172.16.100.222 172.16.100.222
>> 50
>> 255.255.255.255 255.255.255.255 10.10.11.221 10.10.11.221
>> 1
>> 255.255.255.255 255.255.255.255 [ExtIP] [ExtIP] 1
>> 255.255.255.255 255.255.255.255 172.16.100.222 172.16.100.222
>> 1
>> Default Gateway: [ExtDG]
>> ================================================== =========================
>> Persistent Routes:
>> None
>>
>> TIA!
>>
>> --
>> Jeff Vandervoort
>> JRVsystems
>>
>
>