Odd wireless problem

[edwardappleby]

Hello all,

Last weekend, I purchased a NetGear wireless router (WGT624 v2). I wired it through my Vonage router (Linksys RT31P2) but hooked the PC directly into the wireless router. This set-up worked perfectly for a week.

Last night, the Internet stopped working on my laptop. I thought that there might be some problem with the wireless connection, but there was not. So, I checked my (wired) PC's connection; it didn't work either. Occasionally, the Internet would work (on both) briefly, then stop again. I assumed there might be some problem with the Internet connection. So, I re-booted the computer and all three devices several times, without any luck. Finally, I unhooked the wireless router (and returned simply to my previous set-up); the wired set-up works again (but I am now without my wireless network).

So, now, I have no idea what to do. The set-up (which is correct, as far as I can tell) worked for a week. The wireless connection is password protected (if otherwise might pose any problem -- i.e. neighbors stealing my bandwidth or whatever).

Any ideas?

[Bill_Castner]

Tell me how you set the the Netgear router's DHCP setting, LAN-side IP, Gateway and firewall.

On your now working laptop, do a Start, Run, ipconfig /all >config.txt
Use Notepad to open config.txt and post the results back to the forum.

.

[edwardappleby]

Hi Bill,

Thanks for your help. I live in Maryland, too.

<< Tell me how you set the the Netgear router's DHCP setting, LAN-side IP, Gateway and firewall. >>

They are set to factory configuration. Everything is configured to detect settings from the ISP.

<< On your now working laptop, do a Start, Run, ipconfig /all >config.txt
Use Notepad to open config.txt and post the results back to the forum.>>

I have no internet connection on the laptop now (I set-up the wireless connection again. The Internet seems to be functioning well on the wired connection (PC), but the laptop cannot successfully connect now).

The settings are
hostname lola
primary DNS (nothing listed)
node type broadcast
IP routing NO
WINS proxy NO

The wireless ethernet was disconnected.

update: The wireless connection appears to be working again. When I was toying with the configuration, I changed the access to 'shared key' instead of 'automatic.' (that was WELL AFTER the problems started though) So, I fear that my network will stop working again.
update 2: the network is still acting up... could it possibly be related to trying to use both at the same time?

Thanks.

[Bill_Castner]

Lets do this. Connect (wired) directly to the Netgear router.
Open Internet Explorer and in the address bar enter the IP of the Web-based setup program (can be found in the Manual).

1. Disable the DHCP server
2. Disable, if any, the firewall
3. Assign on the LAN side a static IP of 192.168.1.4, Subnet 255.255.255.0 for the router
4. Configure any wireless security measures you wish to use.

Save the settings.
Turn off the router.

Take a patch ethernet cable and connect from the "Uplink" port on the Linksys to a regular LAN port (not WAN and not Uplink) on the D-link router.

Turn off workstations, both routers, the modem
Power on the modem, the Linksys router, the D-Link router, the workstations.

Test.

[edwardappleby]

I believe I followed your directions correctly.

Upon rebooting, the Internet wouldn't work. The Internet connection tab indicated that I had connectivity but that it was 'limited.' I clicked repair, which did not work. I returned my wired network to its old configuration, reset everything, and only now does it work again.

By the way, I attempted the type of set-up you suggested (obviously not without the IP changes, etc) out of the box [i.e. cable modem --> wireless router --> computer and wired router), but it didn't work. Only when I switched things around -- i.e. modem --> wired --> wireless (with computer hooked directly to wireless) would it work.

[Bill_Castner]

Only when I switched things around -- i.e. modem --> wired --> wireless (with computer hooked directly to wireless) would it work.

If you look above that is exactly what I specified. The D-Link is "daisy-chained" to the original Linksys router. The original Linksys router has the modem connection, and this did not change in my plan.

What we are doing is using the D-link as a wireless access point. The fact that it is a router plays no role in this. If you, for example, set static IP addresses the Gateway IP would be that of the Linksys router, and not the D-link.

We do not need the D-link to act in a DHCP server role. The Linksys is more than happy to do the job for both wired and wirelss clients.

So, modem -->Linksys-->D-Link

Best wishes.

[edwardappleby]

Sorry for my confusion. I am still unsure of exactly what you mean, so perhaps I should explain what I did more clearly.

When you indicated to "connect (wired) directly to the Netgear router," I assumed you meant that I should directly connect the cable modem to Internet port of the wireless router. From "patch ethernet cable and connect from the "Uplink" port on the Linksys to a regular LAN port": I then connected the PC and the Linksys wired router to LAN ports in the wireless router.

My understanding of both routers (wired and wireless) is that there is one Internet port where the connection 'comes in' and several LAN ports where the connection 'goes out.' So, I don't understand how the modem can connect directly to the Linksys wired router and how I can connect the 'uplink' (unless I am misunderstanding you; I assume you meant the 'entry' point) to a LAN port on the wireless. Could you clarify? I am sorry and truly appreciate your assistance.

[Bill_Castner]

Modem to Linksys WAN port.
Linksys Uplink port to D-Link regular LAN port.

Workstations if using wired connecctions can use free regular LAN ports on either router.

---------------
Linksys - DHCP router, no change from previous settings
D-Link - DHCP is disabled

----------------
Linksys - No LAN IP or WAN changes
D-Link - given a static IP outside the Linksys DHCP scope of assigned addresses. (The default scope is 192.168.1.50 -- 192.168.1.149) I picked 192.168.1.4 arbitrarily.
Subnet Mask: 255.255.255.0
Gateway: the IP of the Linksys router. The default is 192.168.1.1
------------------
Linksys - No firewall changes
D-Link - Disable if it has the feature
-------------------

I hope that is clearer.

Bill in Maryland.

[edwardappleby]

Dear Bill,

I think I understand this time. There should be no wires connecting to the NetGear wireless router's internet port? (if the modem is connected to the wired router and the wired router connected to the wireless router via a LAN port?).

With this set-up, I cannot connect to the wireless router... with the original address (192.168.0.1) or the one we reassigned it (192.168.1.4).

[Bill_Castner]

That is because routers do not reverse forward.
This is normal.
To access the wired router setup you remove it from its existing wiring setup and connect directly with cable to the wireless router.

One thing you can try --
Enable UPnP on both the Linksys router and the D-Link router.

One your computer make sure that the Universal Plug and Play Service is strated and that its startup setting is Automatic.

Lastly open the Windows firewall. Under the Exceptions tab checkmark to make an exception for UPnP.

Finally, open "My Network Places". On the left panel you will see a control for hiding or unhiding UPnP devices on the network. You want it to show "Hide icons for networked UPnP devices".

If you are realy lucky you will eventually see icons for the modem, Linksys router and D-Link routers. Double clicking the icons will open the Web-based setup pages.

But it would be normal for the wireless router to be inaccessible other than through a direct cable connection.

[edwardappleby]

The wired PC now works properly wired through a LAN port in the wireless router, BUT the laptop (while connecting to the wireless signal) is giving me an 'invalid IP address' error.

[joee]

Did you try repairing? Possibly upgrading your NIC's drivers, viruses/worms lurking around?

[Bill_Castner]

Do a Start, Run, ipconfig /all >config.txt on the laptop.
Post the contents of config.txt back here.

[edwardappleby]

Sorry for my confusion.

The laptop problem was an error on my part, I believe...

At any rate, the laptop connects perfectly to the wireless network. I *think*, with your help and looking at a diagram on the NetGear website, that I have configured this set-up correctly. However, with the ethernet cord connecting to a LAN port in the wireless router (i.e. as both you and NetGear suggested), the Internet light is not flashing, and, thus, I cannot access the Internet through the network.

[edwardappleby]

I started over and reconfigured EVERYTHING on the network. I can now use the wireless, but it seems to drop off when another computer is using it. [It also seems to randomly drop off sometimes. The Internet on the wired PC will also stop working if the Internet is being used elsewhere on the network]

Here are the laptop settings... does anything seem odd?

192.168.15.1 = the wired router
192.168.15.99 = the wireless router
192.168.15.2-98 = assignable IPs [done by the wired router]

Windows IP Configuration



Host Name . . . . . . . . . . . . : lola

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Wireless Network Connection:



Connection-specific DNS Suffix . : hsd1.md.comcast.net.

Description . . . . . . . . . . . : Dynex Wireless G Enhanced Adapter

Physical Address. . . . . . . . . : 00-14-A5-9E-BB-28

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.15.47

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.15.1

DHCP Server . . . . . . . . . . . : 192.168.15.1

DNS Servers . . . . . . . . . . . : 68.87.73.242

68.87.71.226

Lease Obtained. . . . . . . . . . : Sunday, September 10, 2006 11:42:41 AM

Lease Expires . . . . . . . . . . : Monday, September 11, 2006 11:42:41 AM

[Chode]

Ed, here's a link to freeware that can test your wireless LAN for signal strength, interference, etc. : http://www.netstumbler.com/downloads/

It doesn't work with all wireless NICs, but it's a great utility for the money. Since wireless LANs use the 2.4 GHz band, they are subject to lots of RF interference from cordless phones or other wireless equipment (especially wireless LANs using Airgo chipsets such as NetGear's RangeMax products).

Still, I wouldn't overlook the most obvious possiblity, which is that the radio section of your D-Link router may be failing. Been there recently, myself. My D-Link wireless router made it out of warranty by about 15 minutes before the wireless failed. I'm currently running the D-Link as a router connected to a Linksys wireless access point for my household LAN. Of course, anytime you are running two routers on a network, the equipment not actually acting as a router should have DHCP disabled.

[edwardappleby]

Using the utility you suggested, the signal seems perfectly fine.

The problem is that the wired PC also 'drops' from the Internet when the Internet is being used elsewhere on the network.

[Bill_Castner]

Are alll the clients, wireless and wired, using the DHCP server on router #1 for IPs?

Because it sure sounds like both clients are using the same IP. From your Ipconfig results above, the wireless at least during the session shown was using DHCP and pulled from the first router this IP:

IP Address. . . . . . . . . . . . : 192.168.15.47

(Sort of curious that it did not pull 192.168.15.2, the first IP in your DHCP scope, but maybe it randomizes).

So, with both wired PC and wireless PC connected, do an IPCONFIG /All on both and look at the IP information being granted to each. Is the IP address the same? The Gateway, DNS servers and DHCP server address must be identical for both. The IP must be different.

[edwardappleby]

ok... here is the PC, which is hooked to the wired router

Windows IP Configuration



Host Name . . . . . . . . . . . . : LoKiMa

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : hsd1.md.comcast.net.



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : hsd1.md.comcast.net.

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection

Physical Address. . . . . . . . . : 00-11-11-2B-E4-CF

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.15.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.15.1

DHCP Server . . . . . . . . . . . : 192.168.15.1

DNS Servers . . . . . . . . . . . : 68.87.73.242

68.87.71.226

Lease Obtained. . . . . . . . . . : Sunday, September 10, 2006 11:31:32 AM

Lease Expires . . . . . . . . . . : Monday, September 11, 2006 11:31:32 AM

[Bill_Castner]

That is what I expected. And it is completely correct.

IP Address. . . . . . . . . . . . : 192.168.15.2

Your earlier wireless adapter showing was identical, other than this:

IP Address. . . . . . . . . . . . : 192.168.15.47

But that is still a valid IP.

In cases like this you do the repairman's friend. Power off the modem, both routers and the workstations.

Wait one minute.

Power on the modem
When it stabilizes power on router #1 (wired only router)
When it stabilizes power on router #2 (wireless router)
When it stabilizes power on the workstations.

.