Unable to access remote machine after network upgrade

[n.dave]

Our networks have Mac OSX 10.4 Tiger computers.
Before our company did the switch and router upgrades, I am able to access a remote machine at IP 210.201.12.20 (altered IP for posting)

After traceroute, I get these results for good and bad machines for comparison.



Good machine:

Admin$: root$ traceroute 210.201.12.20

traceroute to 210.201.12.20 (210.201.12.20), 64 hops max, 40 byte packets

1 210.209.12.1 (210.209.12.1) 1.238 ms 0.551 ms 0.425 ms

2 210.209.254.1 (210.209.254.1) 1.678 ms 1.241 ms 1.097 ms

3 210.209.254.2 (210.209.254.2) 1.174 ms 0.949 ms 0.994 ms

4 210.241.50.33 (210.241.50.33) 194.156 ms 184.046 ms 203.759 ms

5 210.240.1.2 (210.240.1.2) 208.150 ms 199.042 ms 172.366 ms

6 210.255.255.1 (210.255.255.1) 148.200 ms 172.827 ms 189.678 ms

7 210.253.1.3 (210.253.1.3) 200.725 ms 184.572 ms 215.703 ms

8 app.com (210.201.12.20) 179.973 ms 172.189 ms 177.798 ms





Bad machine:

admin$ traceroute 210.201.12.20

traceroute to 210.201.12.20 (210.201.12.20), 64 hops max, 40 byte packets

1 210.209.12.1 (210.209.12.1) 1.562 ms 0.553 ms 0.440 ms

2 210.209.254.1 (210.209.254.1) 1.533 ms 1.201 ms 1.028 ms

3 210.209.254.2 (210.209.254.2) 6.138 ms 0.954 ms 0.907 ms

4 210.241.50.33 (210.241.50.33) 69.614 ms 19.054 ms 23.255 ms

5 210.240.1.10 (210.240.1.10) 35.453 ms 48.921 ms 48.752 ms

6 * * *

7 * * *

8 * * *

9 * * *

10 * * *



------------

Note:


On Intel Mac terminal (Tiger 10.4.11), I ran these commands:

sudo arp -d –a

sudo lookupd –flushcache

And reboot

With no success,
Thanks for any suggestion.

Dave

[kupertini]

The routing has changed after the router with the IP address 210.241.50.33. The default gateways for the machines seem to be the same before (good) and after (bad) so ARP isn't the issue.

New routing may not necessarily be bad. They could be part of the design. Traceroute may be blocked as part of that new design too.

Can you ping the target IP address or get to it on port 80 with telnet (I'm assuming this is a webserver IP)?

[n.dave]

I cannot ping the target IP nor get to it on port 80.

[n.dave]

Yes, it is a web server.

[kupertini]

Can the webserver get access to other devices on the network, both on its local subnet and beyond?

It could be:

1. a routing issue on the network
2. an incorrect gateway on the webserver
3. access controls preventing access to the webserver

Can you ping the webserver from the last known good hop 210.240.1.10? There could be access controls preventing the Macs from getting access, but allows the routers to get access.

Does device 210.240.1.2 still exist? It seemed to have known the way to the webserver before after the key 210.241.50.33 device. Try to ping the webserver from there.

Sometimes the ping port 80 traffic reaches the webserver, but doesn't return on the correct path. Have you tried tcpdump to see whether your packets are coming through?

[Poundjd]

The problem most likely exists at 210.241.50.33, it sends to 1.2 on the good trace and 1.10 on the bad trace..... look at it's configuration....
-jeff