Problem with my wireless Router network

remission,

I'm not surprised that the Linksys/Vonage is unreachable if the PC's receiving its IP address from the D-Link. The D-Link would have to know about a special route to the 192.168.15 network before that would work right. As it is, it probably tries to send traffic to that network out to the Internet, and since it's a "private" network, that won't work. But note that it eventually does work. That's likely because the Linksys is broadcasting a route to itself. That's probably related to the mysterious DHCP renewals from the wrong router.

If it were possible to configure the DI-514 to act as an "access point", so only the Linksys/Vonage would be serving up IP addresses and being the one and only router, none of this would be happening. If you want to bring VOIP with you after moving, you'll need something like the Linksys. But the wireless device shouldn't be another router, because if it is, the strange effects you're seeing will result. You should be able to fix that now by replacing the DI-514 with a device that can act as an access point.

(edit) Looks like another Linksys/Vonage joint offering will do exactly what you need. The WRT54GP2 has two VOIP phone jacks, three switched Ethernet ports for wired LAN devices, and an 802.11 b/g wireless device. It could replace both the DI-514 and the RT311P2.

The routing table you posted looks normal for a single network with one default gateway. If you find you can't reach anything on the Internet, even with the DHCP server in the Linksys disabled, take another look at the routing table. I suspect you'll find 192.168.15 addresses in it, confirming my hunch that the Linksys is sending routing table updates out.

Jim

Message Edited by jimw on 05-13-2005 10:23 PM

I checked the computer again when I woke up and it still wont connect to the internet unless I restart.
I checked the IP info again and this is what I got now


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\mike>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : mike-ufy48bzfsp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-50-2C-02-9B-04

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : ADMtek AN983 based ethernet adapter
Physical Address. . . . . . . . . : 00-50-BF-97-42-A8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, May 13, 2005 11:45:25 PM
Lease Expires . . . . . . . . . . : Saturday, February 24, 2007 10:07:39
PM

C:\Documents and Settings\mike>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255
Reply from 192.168.0.1: bytes=32 time<1ms TTL=255

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\mike>


It all looks to be normal, the IP address is correct for the DLINK.

I'm not sure what you mean by a routing table. Where would I look for this?


Yea Dlink said this router cannot be an access point so I should buy one, but I allready spend 40 bucks on this router and it is the 2nd one i have bought, and the Linksys Router that is wireless all in one is over 100 bucks. I think when I move I'll just get a basic phone line. It's just too much of a hassle not having phone service if the computer or somthing else messes up. Because I cannot call tech support if the phone is down .

remission,

The "ipconfig" output looks fine. Was that the output from before you restarted? It looks like it was, because the DHCP lease was obtained at 11:45 PM last night, according to the output.

What's the exact error message you receive from your Web browser when you can't connect to the Internet?

Regarding the routing table, that's the output of "netstat -r". It would be good to know if it's different from what you reported before when this problem's happening.

Let's try reaching outside the LAN, and see if we can tell where the traffic stops. That's done with a tool called "tracert". First, let's see if we can reach the D-Link's default gateway. That's done with from a cmd.exe window as follows:

tracert 69.143.32.1

If that succeeds, let's see if we can "tracert" to one of the listed DNS servers:

tracert 68.42.244.5

And if that works, let's try reaching "dslreports.com" using its IP address:

tracert 209.123.109.175

If any of those don't complete with a "Trace complete." message, report all the output that one produces, as well as the one before it.

I've tried all three of those from my location, and was able to reach all of them with "tracert". Some ISPs block that kind of traffic, which makes it harder to troubleshoot connectivity problems. Let's hope yours isn't one of them!

Jim

I tried to trace those 3 addresses you gave me, only one went through.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\mike>tracert 209.123.109.175

Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.



Then I tried the next




C:\Documents and Settings\mike>tracert 69.143.32.1

Tracing route to cdnt01-a-rtr.alxndr01.va.comcast.net [69.143.32.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 10 ms 8 ms cdnt01-a-rtr.alxndr01.va.comcast.net [69.143.32.
1]

Trace complete.

C:\Documents and Settings\mike>tracert 68.42.244.5

Tracing route to ns01.taylor01.mi.comcast.net [68.42.244.5]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.



Then I tried the last one




Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\mike>tracert 209.123.109.175

Tracing route to www.dslreports.com [209.123.109.175]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.

remission,

Well, Comcast isn't letting much of any diagnostic traffic through! While you can tracert to the D-Link's default gateway (69.143.32.1), you can't tracert through it. Let's see if you can "tracert" to the WAN IP address of the D-Link, like this...

tracert 69.143.39.116

I can't reach the D-Link from my location, but it's the only one of the four we've tried that I can't reach. It sounds like Comcast has "tracert" traffic very severly restricted.

Am I correct that all the data you reported was when the PC was otherwise working normally?

Also, have you ever tried the unpleasant experiment of leaving the Linksys powered off or disconnected from the D-Link for long enough to be able to form an opinion about whether the problem doesn't happen if the Linksys (and your VOIP phone service with it!) is completely out of the picture?

(edit) Let's add one more type of Internet traffic to our baseline data: FTP. Here's a short FTP session using the command-line FTP client. Responses that need to be typed in are shown in red.

c:\>ftp ftp.microsoft.com
Connected to ftp.microsoft.com.
220 Microsoft FTP Service
User (ftp.microsoft.com: (none)): anonymous
331 Anonymous access allowed, send identity (e-mail name) as password.
Password:
230-Welcome to ftp.microsoft.com. Please also visit http://www.microsoft.com/downloads.
230 Anonymous user logged in.
ftp> quit
221 Thank you for visiting ftp.microsoft.com.

Since the password's not echoed, it's not shown. I used my EMAIL address.

Try the FTP experiment when the connection is working, so you can see what it looks like when things are normal.

Then, when you cannot reach any Web sites with your browser (Internet Explorer, I assume), record the error message that the browser displays. Then try tracert 69.143.32.1 (the D-Link's gateway), the command-line FTP experiment to "ftp.microsoft.com", and the routing table output (from "netstat -r"). That will give us a pretty good idea as to what works and what doesn't work when the connection is down.

(edit #2) I was hoping we'd be able to make more progress on this problem over the weekend, but it looks like you may have decided to take some "time off" from it instead! Good idea! :) But I'm going to be unavailable for the early part of this week, so don't expect any replies from me until Wednesday at the earliest. Perhaps someone else will be able to lend a hand while I'm unavailable.

Jim

Message Edited by jimw on 05-14-2005 07:31 PM

Message Edited by jimw on 05-15-2005 07:08 PM