** Tracert command **

auos

Hi,

My client is assigned with this following information

IP Address = 10.13.2.63/24
Default Gateway = 10.13.2.254

And when I run command

C:\> tracert 10.4.8.62

I get this following result

Tracing route to 10.4.8.62 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.13.2.253
2 <1 ms <1 ms <1 ms 10.13.1.249
3 5 ms 5 ms 5 ms 10.254.1.78
4 6 ms 5 ms 5 ms 10.200.64.254
5 5 ms 14 ms 5 ms 10.4.8.62

My question is why a tracert command did not show my default gateway as first hop. As I now my default gateway is interface that I go throw him.

BR,
Auos

gojericho0

What device does this address belong to?

10.13.2.253

LBC90805

Are you sure you didn't configure your degfault gateway to .253? Might have just made a numeric typo!

dtlokee

It is possible the router has a secondary IP address on the interface for the .254 address but rturns the TTL expired message from the .253?

auos

I am sure about addressing

marco71

auos wrote:

I am sure about addressing

then, please post output for:
ipconfig /all and
route print
to eliminate any suspicion

auos

marco71 wrote:

auos wrote:

I am sure about addressing

then, please post output for:
ipconfig /all and
route print
to eliminate any suspicion

Dear marco71,

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : lt-a004924
Primary Dns Suffix . . . . . . . : aws.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : aws.com
aws.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : aws.com
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-14-38-1C-CA-4E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.13.2.63
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.13.2.254
DHCP Server . . . . . . . . . . . : 192.168.165.1
DNS Servers . . . . . . . . . . . : 192.168.163.1
192.168.163.20
Lease Obtained. . . . . . . . . . : Saturday, June 21, 2008 8:26:39 AM
Lease Expires . . . . . . . . . . : Monday, July 21, 2008 8:26:39 AM

Ethernet adapter Wireless Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Network
Connection
Physical Address. . . . . . . . . : 00-15-00-10-39-16

C:\>route print
=============================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 14 38 1c ca 4e ...... Broadcom NetXtreme Gigabit Ethernet - Packet Sch
eduler Miniport
0x3 ...00 15 00 10 39 16 ...... Intel(R) PRO/Wireless 2200BG Network Connection
- Packet Scheduler Miniport
=============================================================
=============================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.13.2.254 10.13.2.63 20
10.13.2.0 255.255.255.0 10.13.2.63 10.13.2.63 20
10.13.2.63 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.13.2.63 10.13.2.63 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.13.2.63 10.13.2.63 20
255.255.255.255 255.255.255.255 10.13.2.63 10.13.2.63 1
255.255.255.255 255.255.255.255 10.13.2.63 3 1
Default Gateway: 10.13.2.254
=============================================================
Persistent Routes:
None

astorrs

Could 10.13.2.254 be a secondary ip on the same interface as 10.13.2.253. I haven't tested before but I could see the router returning only the primary interface since its on the same subnet. Do you have access to this router (.254)?

marco71

Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.13.2.63
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.13.2.254
DHCP Server . . . . . . . . . . . : 192.168.165.1

my assumption is that DHCP server (192.168.165.1) assign an incorrect (or a forced intermediary node) gateway (10.13.2.254 instead 10.13.2.253), but somehow the routes are passing by (10.13.2.254 could be a transparent bridge used for filtering)

try to assign manually the ip address and the gateway (.253) and see what happens