Josh Perry
System Admin
NetConnect
http://www.netcnct.net/
joshp@netcnct.net
----------
> From: Andrew <redshift@istar.ca>
> To: NTisp Mailing List <ntisp@emerald.iea.com>
> Subject: Tracert timeout on first hop
> Date: Friday, April 25, 1997 6:36 PM
>
> Hi folks
>
> Wondering if someone can help with a little configuration issue?
>
> I have a PPro180 server running NT4.0 connected to a Livingston PM2e-R.
>
> NTserver on 204.50.3.1
> PM2 on 204.50.3.2
> Upstream gateway 207.107.201.69
>
> When I do a tracert from either the NT console or a dial in user I get
the
> following :
> -----
> c:\tracert www.microsoft.com
> Tracing route to www.microsoft.com [207.68.137.59]
> over a maximum of 30 hops:
>
>
> 1 * * * Request timed out.
> 2 60 ms 60 ms 60 ms 207.107.201.69
> 3 60 ms 70 ms 60 ms core-spc-van-1-fddi3/0.Sprint-Canada.Net
> [204.50.251.49]
> 4 70 ms 60 ms 70 ms sl-sea-5-H11/0-T3.sprintlink.net
> [144.228.95.37]
> 5 61 ms 70 ms 70 ms sl-sea-6-F0/0.sprintlink.net
[144.228.90.6]
> 6 60 ms 81 ms 70 ms sl-mic-3-h0-T3.sprintlink.net
> [144.228.96.22]
> 7 70 ms 60 ms 81 ms 207.68.145.46
> 8 70 ms 70 ms 80 ms 207.68.137.59
>
> Trace complete.
> ----
>
> The first hop times out *every time*.
>
> If I Telnet to the PM2 and do the same trace there is no delay on the
first
> hop. So from that I figure it's a routing problem whit NT (?).
>
> Here's my NT route table :
>
> -------
> C:\route print
> Active Routes:
>
>
>
> Network Address Netmask Gateway Address Interface
Metric
>
> 0.0.0.0 0.0.0.0 204.50.3.2 204.50.3.1
1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
> 204.50.3.0 255.255.255.0 204.50.3.1 204.50.3.1
1
> 204.50.3.1 255.255.255.255 127.0.0.1 127.0.0.1
1
> 204.50.3.255 255.255.255.255 204.50.3.1 204.50.3.1
1
> 207.107.201.0 255.255.255.0 204.50.3.2 204.50.3.1
2
> 207.107.201.68 255.255.255.252 204.50.3.2 204.50.3.1
1
> 224.0.0.0 224.0.0.0 204.50.3.1 204.50.3.1
1
> 255.255.255.255 255.255.255.255 204.50.3.1 204.50.3.1
1
>
> -------
> I added 207.107.201.68 (my WAN network segment) manually and deleted
> 207.107.201.0. And tried that no difference. As you can see 207.107.201.0
> is part of the route table again. NT put it back in without even asking!
> ;-)
>
> Any Ideas on the first hop delay would be greatly appreciated!
>
> Thanx
>
> Andrew Barton
> RedShift Information Technology
>
>
>
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com