Hi, we have some interesting problems with our network. My room mate is directly connected to our Ubee broadband gateway/router/modem, 192.168.0.1, and his desktop IP is 192.168.0.4.
I'm behind a second router, 192.168.2.11, and my address assigned by the first router is 192.168.0.5. The second router has DHCP enabled and is an effort to have a private, secure, network distinct from the ISP direct connect network. The Internet works fine usually but there are some issues (saved for later).
I have many questions, for example, a tracert from any computer in either network usually starts at 10.65.192.1, which is RoadRunners network. But the first hop can take a long time and may timeout. A tracert to 192.168.0.1 from my computer is instant, and the first hop is my router's IP of 192.168.2.11 to the second hop of 192.168.0.1, which is the ISP's router/gateway.
So given that background, does this tracert from a wireless client of the first network with and address of 192.168.0.5 make sense? IOW, why is my roommate's desktop with an address of 192.168.0.4 answering? Why wouldn't the gateway at 192.168.0.1 answer?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\WirelessClient>tracert 192.168.0.6
Tracing route to 192.168.0.6 over a maximum of 30 hops
1 User-PC [192.168.0.4] reports: Destination host unreachable.
Trace complete.
C:\Users\WirelessClient>tracert 192.168.0.7
Tracing route to 192.168.0.7 over a maximum of 30 hops
1 User-PC [192.168.0.4] reports: Destination host unreachable.
Trace complete.
C:\Users\WirelessClient>tracert 192.168.0.8
Tracing route to 192.168.0.8 over a maximum of 30 hops
1 User-PC [192.168.0.4] reports: Destination host unreachable.
Trace complete.
C:\Users\WirelessClient>tracert 192.168.0.9
Tracing route to 192.168.0.9 over a maximum of 30 hops
1 User-PC [192.168.0.4] reports: Destination host unreachable.
Trace complete.
There are more questions but this is a good start if anyone is interested enough to answer. Thanks.