Remote Desktop and Network Shares across VPN

I have two sites connected by vpn. Site A has a win 2003 server and is
running Terminal Services, DNS, DHCP and RRAS and is on 172.16.3.0 subnet.
Site B server does all the same stuff as site A but is on 172.16.2.0 subnet.
Remote Desktop connections from computers in site B work to all computers in
site A except to the server in site A. The problem is about once a week all
RD connections and network shares that are accessed from computers at site B
to the server in site A stop working. The only solution I have found is to
reboot the server in site A. This restores functionality for about a week
and then it has to be done again. The question is, what is misconfigured
with the server in site A so that it randomly takes a crap and stops letting
clients in site B connect. I should mention that when clients in site B no
longer can connect to the server in Site A, they can still ping the server
and get reply, either by ip or hostname, and all clients in site A can access
the network shares and RD to the server and clients in site B can RD to any
other computer in site A. Thank you for your help in advance

posting the results of ipconfig and routing table on the problem server may help.

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
"Brandon" <(E-Mail Removed)> wrote in message news:C7BD8E85-A648-4392-9EC4-(E-Mail Removed)...
I have two sites connected by vpn. Site A has a win 2003 server and is
running Terminal Services, DNS, DHCP and RRAS and is on 172.16.3.0 subnet.
Site B server does all the same stuff as site A but is on 172.16.2.0 subnet.
Remote Desktop connections from computers in site B work to all computers in
site A except to the server in site A. The problem is about once a week all
RD connections and network shares that are accessed from computers at site B
to the server in site A stop working. The only solution I have found is to
reboot the server in site A. This restores functionality for about a week
and then it has to be done again. The question is, what is misconfigured
with the server in site A so that it randomly takes a crap and stops letting
clients in site B connect. I should mention that when clients in site B no
longer can connect to the server in Site A, they can still ping the server
and get reply, either by ip or hostname, and all clients in site A can access
the network shares and RD to the server and clients in site B can RD to any
other computer in site A. Thank you for your help in advance