Can you look at the output from the trace below? I am wondering what would cause a packet to bounce between routers like that and whether that would have caused certain TCP applications to fail because of TTL issues:

hqdistsra2#trace ip 10.130.210.21

Type escape sequence to abort.

Tracing the route to 10.130.210.21

1 192.168.28.81 hqcoresb
  192.168.28.65 hqcoresa
  192.168.28.81 hqcoresb

2 192.168.28.241 hqmfwansa
  192.168.28.253 hqmfwansb
  192.168.28.241 hqmfwansa

3 10.10.227.1 PacwanRB
  10.10.222.1 PacwanRA
  10.10.227.1 

4 10.6.12.2 208 CpFosterMSRA
  10.6.13.2 264 KadenaMSRA
  10.6.12.2 200 CpFosterMSRA

5 10.10.6.70 KadenaMSRB
  10.10.6.66 CpFosterMSRB
  10.10.6.70 

6 10.10.10.6 CpFosterHQRB
  10.10.10.14 CpFosterHQRA
  10.10.10.6 

7 10.182.0.234 CpFosterHQCSB 
  10.182.0.238 CpFosterHQCSB
  10.182.0.234 

8 10.182.0.67 CpFosterHQAS2

9 10.130.210.21 

-- Steve

Would you please explain the differences between ports and interfaces? Could you also explain where console ports, aux ports and switch virtual interfaces, router virtual interfaces and null interfaces fit into the whole mix? Trying to keep these straight is very hard.

-- Tony

I've wondered about this for a while now when I look at different CCIE practice lab workbooks: Just how long does it take to write a practice lab? How difficult is it?

-- Gary

My question is, which is better -- TKIP or AES? My router and NIC supports both, but I haven't found a clear answer online as to which provides better security. I know NIST went with AES replacing DES. I'm firewalled, OS as well as router. Not broadcasting my SSID.

-- Grant