DigitalDaz
02-01-2010, 12:23
Tracing route to 188.165.165.230 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 174 ms 100 ms 11 ms sw1.tc.lon.ovh.net [195.66.224.220]
5 17 ms 19 ms 16 ms 20g.vss-2-6k.routers.chtix.eu [94.23.122.109]
6 * * * Request timed out.
7 * * * Request timed out.
8 ^C
Hop 6 should definitely be your server main IP if you are not using Virtual MACs. Rule out this problem first.
I have just traced one of my RIPE ips that is not allocated to any VM and thats exactly what I got and expected. The trace times out AFTER it hits my main server IP
If you have MSN add me at darren@kickingaddiction.com
1 <1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 * * * Request timed out.
4 174 ms 100 ms 11 ms sw1.tc.lon.ovh.net [195.66.224.220]
5 17 ms 19 ms 16 ms 20g.vss-2-6k.routers.chtix.eu [94.23.122.109]
6 * * * Request timed out.
7 * * * Request timed out.
8 ^C
Hop 6 should definitely be your server main IP if you are not using Virtual MACs. Rule out this problem first.
I have just traced one of my RIPE ips that is not allocated to any VM and thats exactly what I got and expected. The trace times out AFTER it hits my main server IP
If you have MSN add me at darren@kickingaddiction.com