We have a MS VPN setup through routing and remote access services over
a cable modem connection. I've found that if we access data from the
windows 2003 server we have a PAINFULY long wait as we brows from one
folder to the next. Interestingly enough, I tried browsing to our 2000
server and it moves like lightening. I can drill down and up through
the folders without even any lag.
The 2003 server is the active directory server hosting DHCP and DNS.
The 2000 server is just a member server.
I tried moving the RRAS service over to the 2000 server to see if that
made a difference (perhaps the problem was the 'hosting' server), but
there was no change.
All the IP settings look the same on both servers (with the exception
of the IP of course). The only other unusual thing I saw was the first
time I connected to test today I tried to ping server1 and it resolved
to 192.168.0.137 and I got nothing back. The server is actually set to
192.168.0.10 (again, this is the DHCP and DNS server, so I would think
the client would know that). I tried pinging 192.168.0.10 and I did get
a response. Likewise, I pinged server2 which resolved properly and at
the same rate as the server1 IP (about 31 ms). In any event, I did a
/flusdns on my client and it didn't resolve to the 137 again, but I
still have the problem. I likewise flushed on the two servers.
I've also found that if I map a drive to the share on the server1 it
makes no change in the browsing speed. If I go to a cmd prompt and do a
dir /s it lists everything pretty quickly, so I'm wondering what added
data it's choking on when browsing.
Any suggestions??? Thanks!
Mick
|
Similar Threads
Linear Mode
