Recurrent wireless connection problems

[darkyear]

I built a desktop computer in August. I often move it between two different houses, which means two different wireless connections. At one house the connection works perfectly, and I never have any problems. At the other I used to have recurrent disconnects (the status would go from "Identifying..." to "Unidentified Network", but the name of the network (Netgear) was known), but the computer would usually stay connected and run well. I used to unplug every single cable from the router and modem and wait a while before plugging them back in, and that used to work. Now nothing works. I can "ipconfig /all" or "ipconfig /renew" in Command Prompt, and I will connect to the internet. However, when I do this, the internet is extremely slow with frequent disconnects and will often not load pages fully. I think it must be an IP problem because IPCONFIG kind of fixes it.

There are 3 more computers in the house (2 laptops and the desktop that is directly connected to the modem), and none of them have the problem. My computer still has the problem even when the two laptops are not present. I have looked all over the internet for months for solutions, but nothing has worked permanently for me, so I finally decided to ask a question myself.

I have tried this in CMD:

PING 192.168.1.1

PING yahoo.com

NBTSTAT -n

IPCONFIG /ALL

and I got these results:

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Nick>PING 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

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

C:\Users\Nick>PING yahoo.com

Pinging yahoo.com [206.190.60.37] with 32 bytes of data:
Reply from 206.190.60.37: bytes=32 time=66ms TTL=51
Reply from 206.190.60.37: bytes=32 time=66ms TTL=51
Reply from 206.190.60.37: bytes=32 time=85ms TTL=51
Reply from 206.190.60.37: bytes=32 time=67ms TTL=51

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

C:\Users\Nick>NBTSTAT -n

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Wireless Network Connection 2:
Node IpAddress: [192.168.1.3] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
GOLLUM <00> UNIQUE Registered
WORKGROUP <00> GROUP Registered
WORKGROUP <1E> GROUP Registered
GOLLUM <20> UNIQUE Registered

C:\Users\Nick>IPCONFIG /ALL

Windows IP Configuration

Host Name . . . . . . . . . . . . : Gollum
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR8121/AR8113 PCI-E Ethernet Cont
roller
Physical Address. . . . . . . . . : 00-22-15-1B-FA-44
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek 8185 Extensible 802.11b/g Wireles
s Device
Physical Address. . . . . . . . . : 00-06-4F-6A-17-7D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b5a5:fd2:c874:bed9%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, January 16, 2009 7:15:00 PM
Lease Expires . . . . . . . . . . : Saturday, January 17, 2009 7:15:19 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:284a:161c:3f57:fefc(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::284a:161c:3f57:fefc%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{E283261C-6147-473A-83A7-5E64995C6
849}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6TO4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Nick>

Any help would be GREATLY appreciated! I am probably going to get an ulcer if I don't get this resolved soon.

[johnwill]

Truthfully, I'd put wireless interference at the top of the list, even though the other wireless stations are working.


Some things you can try here.

1. For wireless connections, change the channel on the router, I like channels 1, 6, and 11 in the US.
2. For wireless connections, try moving either the wireless router/AP or the wireless computer. Even a couple of feet will sometimes make a big difference.
3. Update the firmware to the latest version available on the manufacturer's site.
4. Reset the router to factory defaults and reconfigure.
5. Update the network drivers (wired and wireless) on your computer to the latest available.

Many times these measures will resolve a lot of intermittent issues.