tracert utility for OS/2?

[AntiGates]

Hi, I'm having problems with my connect speed with Comcast, and I know
the first thing they are gonna ask me is what tracert reports, and
since they only support Windows, the second I tell them I'm not running
windows, and there fore do not have tracert, they will claim they can't
help me.

So, is there any tracert like utility for OS/2?

T.I.A.

[Bob Eager]

Post by AntiGates
Hi, I'm having problems with my connect speed with Comcast, and I know
the first thing they are gonna ask me is what tracert reports, and
since they only support Windows, the second I tell them I'm not running
windows, and there fore do not have tracert, they will claim they can't
help me.
So, is there any tracert like utility for OS/2?

Yes. TRACERTE !!

[AntiGates]

Post by Bob Eager
Yes. TRACERTE !!

Thanks Bob, but in trying the command >>tracerte www.comcast.net<< I get
an output of:

tracerte to www.comcast.net (63.240.76.72), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *

all the way to

30 * * *

with no useful information in place of any of the * as it says i should
in OS/2's TCPIP help.

What am i doing wrong?

[Jeroen Besse]

Post by AntiGates

Post by Bob Eager
Yes. TRACERTE !!

Thanks Bob, but in trying the command >>tracerte www.comcast.net<< I get
tracerte to www.comcast.net (63.240.76.72), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
all the way to
30 * * *
with no useful information in place of any of the * as it says i should
in OS/2's TCPIP help.
What am i doing wrong?

Probably the 1st device (your router?) blocks traceroute packets (or
their returns).

[William L. Hartzell]

Post by AntiGates

Post by Bob Eager
Yes. TRACERTE !!

Thanks Bob, but in trying the command >>tracerte www.comcast.net<< I get
tracerte to www.comcast.net (63.240.76.72), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
all the way to
30 * * *
with no useful information in place of any of the * as it says i should
in OS/2's TCPIP help.
What am i doing wrong?

Try 64 hops and 56 byte packets. But there are some on the backbone
like MCI that block the ICMP messages this generates. Also, down you
firewall as you may be the one blocking ICMP messages.

[AntiGates]

Post by William L. Hartzell

Post by AntiGates

Post by Bob Eager
Yes. TRACERTE !!

Thanks Bob, but in trying the command >>tracerte www.comcast.net<< I
tracerte to www.comcast.net (63.240.76.72), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
all the way to
30 * * *
with no useful information in place of any of the * as it says i
should in OS/2's TCPIP help.
What am i doing wrong?

Try 64 hops and 56 byte packets. But there are some on the backbone
like MCI that block the ICMP messages this generates. Also, down you
firewall as you may be the one blocking ICMP messages.

Thanks to everyone who suggested help....pulling my router out of the
loop solved the tracerte reporting problem, And got me good info.

now if I can just get Comcast to figure out why my newly promised 2 Mb/s
speed increase ai'nt happening, I'll be all set.

Thanks again.

[Allodoxaphobia]

Post by AntiGates
now if I can just get Comcast to figure out why my newly promised 2 Mb/s
speed increase ai'nt happening, I'll be all set.

Comcast here, too. I think you'll notice they say "Up To xxx Mb/s" in
their marketing drivel. If a gaggle of teenagers on the same cable in your
neighborhood are all stealing music and viewing porn at the same time,
there's no way you'll see 'top speeds'.

Just like the manufacturer of the NiMH batteries I use in my digital
camera claims: "Up to 2500 mAh capacity". When they finally go dead,
Dead, DEAD -- they'll still meet spec's...

Jonesy -- (who just saw 3.2 Mb/s on his Comcast pipe.)

[Rich Walsh]

Post by William L. Hartzell

Post by AntiGates
Thanks Bob, but in trying the command >>tracerte www.comcast.net<< I get
tracerte to www.comcast.net (63.240.76.72), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
all the way to
30 * * *
with no useful information in place of any of the * as it says i should
in OS/2's TCPIP help.

Try 64 hops and 56 byte packets. But there are some on the backbone
like MCI that block the ICMP messages this generates. Also, down you
firewall as you may be the one blocking ICMP messages.

There may be something wrong with comcast.net (or their backbone provider).
www.comcast.net resolves to 3 different IPs. When I trace any of them, I
go through sprintlink.net & then att.net. The last reported hop (either
nbr 15 or 19 depending on the destination) is to attens.net; therafter,
it's nothing but stars. (FWIW... Two of the attens.net routers are in
NY, the other is in LA.)

[Richard Steiner]

Post by AntiGates
So, is there any tracert like utility for OS/2?

I seem to remember that the TRACERTE utility bundled with OS/2 Warp 4
may have had some issues -- you might find this OS/2 port of the BSD
traceroute command to be more useful:

http://hobbes.nmsu.edu/pub/os2/apps/internet/util/tracerte.zip

I also like the mtr command (a cross between ping and traceroute):

http://hobbes.nmsu.edu/pub/os2/apps/internet/util/mtr-0-51-bin.zip

[Shmuel (Seymour J.) Metz]

Post by Richard Steiner
I seem to remember that the TRACERTE utility bundled with OS/2 Warp 4
may have had some issues

Perhaps, but it's appeared to work when I've used it. If you recall
the details, I'd be interested.

OTOH, the OS/2 whois client is hopelessly out of date, and I've
switched to bwwhois.

[Richard Steiner]

Here in comp.os.os2.misc,

Post by Shmuel (Seymour J.) Metz

Post by Richard Steiner
I seem to remember that the TRACERTE utility bundled with OS/2 Warp 4
may have had some issues

Perhaps, but it's appeared to work when I've used it. If you recall
the details, I'd be interested.

I don't remember why the bundled tracerte didn't work; I just remember
that some issues existed, that I ran into something myself (I think the
first line of the display always had asterisks in it or something), and
I've noticed that I have a third-party tracerte installed here.

A Google Groups search should turn up the gory details.

Post by Shmuel (Seymour J.) Metz
OTOH, the OS/2 whois client is hopelessly out of date, and I've
switched to bwwhois.

I don't really whois very often, but the version that I use was written
by dink. The doc says

whois v1.2 : by dink (http://ozbbs.ml.org/dink)

and it can be obtained here:

http://hobbes.nmsu.edu/pub/os2/apps/internet/misc/whois12.zip

[Shmuel (Seymour J.) Metz]

Post by Richard Steiner
I don't really whois very often, but the version that I use was
written by dink. The doc says
whois v1.2 : by dink (http://ozbbs.ml.org/dink)

That's the one that I used to use; it doesn't support referrals due to
the registrar/registry reorganizations.

WHOIS.DOC 226 03/29/98 3:50:18p
WHOIS.EXE 7411 03/29/98 3:50:18p

[Rich Walsh]

Post by Richard Steiner
I seem to remember that the TRACERTE utility bundled with OS/2 Warp 4
may have had some issues -- you might find this OS/2 port of the BSD
http://hobbes.nmsu.edu/pub/os2/apps/internet/util/tracerte.zip
http://hobbes.nmsu.edu/pub/os2/apps/internet/util/mtr-0-51-bin.zip

I tried the traceroute cited above & it gave the same results as IBM's
version for www.comcast.net: nothing after the packets hopped off AT&T's
network.

Then I tried mtr - impressive. It could trace all the way to the end.
The results were surprising (should they be?):

13. gar4-p300.la2ca.ip.att.net
14. idf26-gsr12-1-pos-7-0.rwc1.attens.net <- traceroutes died after this one
15. rwcsbix12-3-1.attbi.com <- I assume this is where comcast.net starts
16. 192.168.64.6
17. 192.168.64.73 <- do other big providers route stuff through their "LAN"?
18. www.comcast.net