Can't ping 1 stupid address with IP RANGE

[Dirtbike]

We attemped to install yet another router between our 2 sites. We tried an Adtran this time. Seamingly everything is ok. We're routing between 192.168.1.X and 192.168.2.x networks. When the 192.168.2.135 machine pings 192.168.1.9 everything is OK, when we change the IP to 192.168.2.160 the connectivity fails. No ping by IP or name. there seams to be a range of IP's within our 192.168.2.x/24 network that simply won't connect to the network.

I've verified we're consistantly using a 255.255.255.0 subnet. Any suggestions you could offer would be greatly appreciated.

Scott in Charlotte, NC

 

[bcastner]

It sure sounds like a subnet mask issue. The other possibility is a WINS configuration error. Finally, consider the possibility that the firewall is configured t accept only a certain IP subnet.

 

[Dirtbike]

We got with our UNIX weenie and he said the default route was missing. When we got a default route loaded out problem went away. Thanks. I personally think we still have SOME issues
the .39 is the DHCP server for the 192.168.2.x network. The 192.168.2.135 is a host that is experiencing dropped TELNET connections to 192.168.1.9.
Tracing route to 192.168.2.39 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 8 ms 192.168.2.1
3 7 ms 7 ms 7 ms 192.168.2.39

Trace complete.

H:\>tracert 192.168.2.1

Tracing route to 192.168.2.1 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 192.168.2.1

Trace complete.

H:\>tracert 192.168.2.135

Tracing route to 192.168.2.135 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 7 ms 192.168.2.1
3 442 ms 1638 ms 1638 ms 192.168.2.135

Trace complete.

H:\>

 

[bcastner]

While I do not like it, this entry:
3 442 ms 1638 ms 1638 ms 192.168.2.135

May not really be indicative of a problem.

 

[Dirtbike]

Check out these tracert outputs
H:\>tracert 192.168.2.142

Tracing route to 192.168.2.142 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 192.168.2.1
3 * * * Request timed out.
4 ^C
H:\>tracert 192.168.2.143

Tracing route to 192.168.2.143 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 8 ms 192.168.2.1
3 8 ms 7 ms 7 ms 192.168.2.1
4 * * * Request timed out.
5 ^C
H:\>tracert 192.168.2.144

Tracing route to 192.168.2.144 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 192.168.2.1
3 7 ms 7 ms 8 ms 192.168.2.1
4 * * * Request timed out.
5 * * ^C
H:\>tracert 192.168.2.135

Tracing route to 192.168.2.135 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 7 ms 7 ms 192.168.2.1
3 * 1224 ms * 192.168.2.135
4 1411 ms 1638 ms 1637 ms 192.168.2.135

Trace complete.

H:\>tracert 192.168.2.135

Tracing route to 192.168.2.135 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 192.168.2.1
3 181 ms 1637 ms 1638 ms 192.168.2.135

Trace complete.

Why do I get an bounce within the 192.168.2.1 router?

Thanks for all the help.

Scott

 

[bcastner]

Set the time to live value higher on your ping statement.