Computers won't connect to wirless network

[evitaler]

Hi there!

I have a wireless network in my home. I had it working just great for a month, using WPA2 AES authentication. It stopped working recently. I can still access the internet by connecting to my router with the Cat5 cable. The weirdest part for me is that my USB wireless card detects the network and is at full signal strength. I have disabled authentication and my router is now set up for open access, but it still won't connect.

Details

Router: Netgear WGR614 v9
USB Card: Dynex DX-BUSB

Two computers are having the same problem and it seemed to start around the same time. One is a laptop and one is a desktop, both running XP. When I hook up the USB wireless card, both computers detect the network at full signal strength. I have tried this on both computers using the native Windows XP wireless utility, and using the Dynex utility which came with the USB card.

Like I said, the router (at least the 'wired' portion) is still letting me get to the internet. I disable authentication, and made the changes on my computers as well (for open access). It just won't connect to the wireless internet.

Any help is greatly appreciated!

[evitaler]

Anybody have any ideas?

I noticed that sometimes when I startup my computer, the wireless networking is disabled.

I tried a trick of disabling the Microsoft Service Windows Zero Configuration but that did not help.

[giradman]

Well, just for starters (and you likely have already tried this suggestion) - when my laptops lose connection w/ my Linksys 'wireless' router - I unplug the power from both the cable modem (Road Runner) & the router; wait a minute or so, then first plug in the modem (wait a while), and finally plug in the router - often just letting then reset will do the 'trick' for me - if of no help, please reply back - there are plenty of 'network' people here to help - good luck! :happy:

[Snurfen]

I'd also have a look on page 42 of the manual, and go through the setup routine. You really don't want an open wireless router these days, so many peeps just can't resist hoping on an open router and having a play.

Click here (http://64.233.169.104/search?q=cache:n-hoYnrUwk4J:ftp://downloads.netgear.com/files/wgr614_ref_manual.pdf+Netgear+WGR614+manual&hl=en&ct=clnk&cd=8&gl=uk#42) for manual

[evitaler]

Thanks so far.

Yep, I tried the unplug and reset trick with both the router & the cable modem.

I know an open network is really bad, but at the time, it was the only way to get my network to connect.

I will uninstall and re-install the dynex CD, but I think the problem is with the computers.. Yes, it's weird that two computers have the problem, which would indicate a router or USB adapter problem, but both computers indicate they are receiving the signal full strength; they just don't connect!

I will report back.

[evitaler]

It seems I get full signal strength, but the computers go back and forth between Acquiring Network Address and Limited or No Connectivity!!!

I reset router to defaults. I re-installed USB adapter on both computers, and am now using a PCI adapter on the desktop.. same issue.

[RDG]

Are you set up to pull DHCP? I had a similar issue when setting up my girlfriend's wireless to mine. She had a static IP set. If you run ipconfig /all from a command prompt do you get an IP / sub / gateway at all?

[evitaler]

Ok I am going to focus on the desktop computer as it's more important to me.

This is the result of ipconfig /all:




Windows IP Configuration



Host Name . . . . . . . . . . . . : my name
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-15-F2-44-8C-A1


Ethernet adapter Wireless Network Connection 4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR 108 Mbps Wireless PCI Adapter WG311T
Physical Address. . . . . . . . . : 00-0F-B5-FE-D6-38
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.147.43
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

[Snurfen]

Try this quick fix:

Right click the Wireless Lan connection and disable it, then right click and re-enable it.

[RDG]

A 169.254... IP can indicate your DHCP isn't working correctly. If you reset your router at all, you have to configure your SSID, encryption type and keyphrase. Hook up thru your Cat5e connection to reconfigure these, and adjust your wireless' profile with the correct SSID, encryption type and keyphrase.

[Snurfen]

Oddly enough RDG, that was going to be the thrust of my last post, however, by reviewing the manual, there is a rather odd statement on page 23 about 169.254.x.x being a possibly valid IP address. Odder than odd, I have to admit!

(I actually went back and edited out my statement in my last post about 169.254.... being the classic "I can't see a network" error). Hmmmmm.

[RDG]

A 169.254.x.x being valid...that is rather odd! Every time I've run across one, means there's an issue of some type. I've never had to use a Netgear router, and I suppose they could be right about that, why would you want to use a 169.254.x.x as an IP anyway? Could there be a firmware issue with the router, maybe a checking their website to upgrade firmware?? Hmmm.. is right.

[z1p]

Well netgear(NG) can be a bit of a pain. Don't know about 169 being good sometimes, but it looks like in this case it definitely isn't as there is no default gateway set...

If this was one machine I'd say start with resetting the network stacks, but since you are seeing the problem on a couple of machines, I'd go with a factory reset and start from there.

How old is the router? If you are using the same wireless adapter on both machines, I'd check its driver too.