V
vseven
O.k....I've been getting this error occasionally on a slower link
between two offices and I want to figure out how to fix it. I'm not
sure if its a PC issue or a Cisco router issue. I have three networks
across two domains. All my PC's are located in Domain B but
authenticate to domain A and the servers in question are in Domain A.
The two domains are connected with a Cisco 2821 router and all traffic
from the B side is allowed onto the A side but not the other way
around. On the B side there are two networks seperated by a point to
point T1. So it kinda looks like this:
Remote Network (B) --- P2P ---- Local Network (B) -- Cisco
Router -- Local Network (A)
The connection from the local B to local A works great and the only
time I get a error is this same message when using the wireless system
on local B. But when copying files from the remote B network up to the
local A network I get this error a lot, especailly from Windows 2000
clients. The network is definately valid, you can browse it imediately
afterward without a problem. I do NOT get the error when copying from
remote B to local B which is why I think the timeouts are being caused
by the router. I've upgraded the routers firmware to the lastest
available and had the same issue. Any ideas or what I can check next?
-Allan
between two offices and I want to figure out how to fix it. I'm not
sure if its a PC issue or a Cisco router issue. I have three networks
across two domains. All my PC's are located in Domain B but
authenticate to domain A and the servers in question are in Domain A.
The two domains are connected with a Cisco 2821 router and all traffic
from the B side is allowed onto the A side but not the other way
around. On the B side there are two networks seperated by a point to
point T1. So it kinda looks like this:
Remote Network (B) --- P2P ---- Local Network (B) -- Cisco
Router -- Local Network (A)
The connection from the local B to local A works great and the only
time I get a error is this same message when using the wireless system
on local B. But when copying files from the remote B network up to the
local A network I get this error a lot, especailly from Windows 2000
clients. The network is definately valid, you can browse it imediately
afterward without a problem. I do NOT get the error when copying from
remote B to local B which is why I think the timeouts are being caused
by the router. I've upgraded the routers firmware to the lastest
available and had the same issue. Any ideas or what I can check next?
-Allan