Network Traffic Does not work with one network

[Live2 Bicycle]

I have an office in Atlanta and one in Tenn. I can talk from My pc (192.168.68.202) to server (192.168.241.1) down there just fine. There is another network setup in our computer room with a server (192.168.25.100) that can't communicate with the same server in Atl (192.168.241.1) that I can.

When I do a trace rt from my pc is goes:

1 <1 ms <1 ms <1 ms 192.168.68.202

2 <1 ms <1 ms <1 ms 192.168.0.254

3 65 ms 70 ms 68 ms 192.168.1.10

4 85 ms * 146 ms 192.168.196.202

5 163 ms 169 ms 172 ms 192.168.241.1

When I do it from the server in the computer room I get:

1 192.168.24.254) 0.406 ms 0.327 ms 0.298 ms

2 192.168.0.254) 0.518 ms 0.420 ms 0.371 ms

3 192.168.1.10) 47.363 ms 71.395 ms 48.617 ms

4 * * *

5 * * *

6 * * *

7 * * *

8 * * *

9 * * *

10 * * *

11 * * *

12 * * *

What should I be looking for to trouble shoot this? I am not sure where to start.

[scottmac]

Firewall?

Split route (out on one path, return on another with a stateful inspection device)?

Bad return path? (can you verify that the other end is receiving the traffic and responding ... but the response is not making it back)

Are you blocking ICMP such that a router loop ("TTL Expired") is not being reported? (This is also the mechanism that Traceroute uses ... look at the ACLs on the router and / or firewall at and beyond 192.168.1.10 ... the PC is apparently taking a totall different path and may not be getting blocked).

Can you ping / trace back from the (original) destination router to the (original) source?

Check your subnet masks.

Do a "show frame-relay pvc" on the wan router to verify that that PVC is up and active.

There's some to start with, I'm sure others will have some additional suggestions....

Good Luck

Scott

[a.awan]

Do you have a routing protocol configured in your network or are you relying on static routes? I would make sure that all your network hops have a route back to your computer room subnet.

[arien76]

add an entry of the required ip into the the router of your computer room.

check the connection whether it is logical or physical.

[vcjones]

Before you spend a lot of time looking for obscure causes, check the most likely, which is that: router 192.168.196.202 lacks a route back to network 192.168.241.0.

Good luck and good hunting!

Vincent C Jones

www.networkingunlimited.com

[Live2 Bicycle]

It turned out the rule on the firewall did not compile correclty. the 196.202 was the culprit, thanks!