[foo84r]

I'm unable to perform a traceroute from my iBook. When I am directly connected to the modem I can traceroute fine. But, when I am connected wirelessly or wired behind a router I am not. I have also tested this same traceroute with a wireless Windows computer that was behind the same router and that worked fine. So... why is the Windows computer able to do a trace but not the Mac?

The firewall is not enabled on the Mac. The Mac was also placed in the DMZ of the router.

[zzarg]

what happens with the tracert ? Does it get to the router and stop, or does it not even leave your machine ? Do you get an error message ?
Have you tried tracing to your own IP or the router IP ?
Do you have any firewall s/w running that may be preventing egress on the Mac ?
How are you doing the tracert - from Terminal, or via Network Utility
Are you connected via Ethernet or via Airport ?
Have you checked the router settings to make sure it's not blocking anything ?

I have noticed since 10.3.7 some network operations (tracert and ping) take a while to give an initial response, but when they do start displaying then they're okay

[foo84r]

There's no error message. The trace reaches the router and stops. trace to localhost/127.0.0.1 & to the router work fine.

trace behind router
---:~---$ traceroute www.google.com
traceroute to www.google.akadns.net (64.233.161.99), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 2.779 ms 8.102 ms 1.894 ms
2 *^C

trace to PC/localhost
---:~ ---$ traceroute 192.168.0.103
traceroute to 192.168.0.103 (192.168.0.103), 30 hops max, 40 byte packets
1 192.168.0.103 (192.168.0.103) 20.798 ms 0.172 ms 0.111 ms

trace to router
---:~ ---$ traceroute 192.168.0.1
traceroute to 192.168.0.1 (192.168.0.1), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 2.721 ms 2.025 ms 7.402 ms
2 192.168.0.1 (192.168.0.1) 10.581 ms 6.045 ms 2.085 ms

---:~ ---$ traceroute localhost
traceroute to localhost (127.0.0.1), 30 hops max, 40 byte packets
1 localhost (127.0.0.1) 0.82 ms 0.126 ms 0.093 ms

I've checked the fw on the mac & ensured that it's turned off. I've even check ipfw thru the terminal:

---:~ ---# $sudo ipfw list
65535 allow ip from any to any

I've tried both traceroute thru the network util and terminal. The list above is thru terminal.

I've tried both ethernet & airport. Ethernet connected to the modem works fine. I've tried with two routers (D-LINK & Netgear)

All router settings have been checked. As sated before the mac was even placed in the DMZ. When there is no router present a traceroute displays faster then on a windows PC. Pings display fine with or without the router.

This is not a router issue. The Windows PC traces fine behind the router. The only thing I can think of is there is an issue in the way the mac is creating the packet and the router(s) is/are having an issue reading this packet information & not forwarding it on.

[MrBS]

Windows traceroute is icmp (like pings) while unix traceroute is udp. It sounds like your router's not letting the responses back to your box, make sure udp forwarding is set up.

~BS

[foo84r]

Shouldn't UDP be allowed when you place a computer in the DMZ of the router. I've placed the mac in the DMZ. With trace route there shouldn't be a specific port that should be allowed. I have not seen a router to where you can setup allow ALL UDP traffic thru? The only broad range access would be DMZ and to reply to all ping traffic.

Maybe I should try an apple router!