[Homer1583]

I've been researching this problem of mine for about a month and everything I've tried hasn't worked, so I figure it's finally time to post on a forum.

Alright first off, near the dining room is the main desktop computer using Windows XP. It is hooked up to a Linksys WRT54G router. In my bedroom is my desktop also using XP. For years it has been getting wireless internet with no problem. I can't remember the exact model, but it has a Linksys G wireless card. I got it the same time as the router (7 years ago). The signal strength has never been strong in the bedroom. Typically it's in the 24-36 mbps range (2 to 3 bars) and for signal strength Windows typically calls it "Low" or "Fair." Despite this, the internet always works at full speed and never dips in and out.

Enter the new laptop. About a month ago I got a brand new laptop using Windows 7 with a Ralink N wireless adapter. In the bedroom, it just refuses to hold a steady connection. If I'm lucky once in a while I'll get a steady connection for an hour or so, but typically it doesn't happen. The laptop always connects to the network without a problem, but what usually happens is it will then dip in and out of loading web pages. The icon in the tray would get that yellow warning sign indicating no connection. So I run windows diagnostics and it says "Windows can't communicate with the primary dns server."

So I've tried fixing this in every way I know how... I unplugged the modem and router then replugged later but this didn't fix anything. I've updated the router's firmware but it also hasn't been a fix. I've ran inSSIDer, seeing that no other signals are close enough/strong enough to interfere with mine. I made windsurfer tin foil parabolas to help direct the signal to no avail. I even managed to move the router closer to the bedroom. The most I could move it was about 10 feet, but this is a small house and that 10 feet has been a huge difference. Now the signal in the bedroom is strong. It's the strongest it's ever been. The desktop still connects without a flaw. But even this 10 extra feet still hasn't helped the laptop consistently load web pages. The connectivity problem doesn't even seem to have improved.

So why not try Googling for "Windows can't communicate with the primary dns server"? I've tried that but I can't trust their answers because my situation has a bit of a curve ball. When I move the laptop into the dining room or the living room right across, it connects completely and gets fast internet and does not at all dip in and out.

So when the laptop is 15-20 feet down the hall in the bedroom, even with a strong signal, it can't connect with the primary DNS servers and load web pages. But when it's only within about 10 feet of the router in its sights, it can connect fine.

Is this issue something that can be fixed? Or do I just have a ****** wireless adapter? Thanks in advance for the help.

[pedroguy]

Hi:Let's see if this wi-fi test gives us any different results
Wifi test exe. Hint from Johnwill

Download and run Xirrus Wi-Fi Inspecto from
www.xirrus.com/library/wifitools.php
on the problem machine. Post a screen shot of the main screen here.



To post a screen shot of the active window, hold the Alt key and press the PrtScn key. Open the Windows PAINT application and Paste the screen shot. You can then use PAINT to trim to suit, and save it as a JPG format file. To upload it to the forum, open the full reply window and use the Manage Attachments button
to upload it here.

Note that this application requires NET Framework to run. If you get an error about a missing function, download and install NET Framework.

Then,when you have the "disconnect" let's see this
From a Johnwill post on the Networking Forum


Try these simple tests.

Hold the Windows key and press R, then type CMD (COMMAND for W98/WME) to open a command prompt:

In the command prompt window that opens, type type the following commands one at a time, followed by the Enter key:

NOTE: For the items below surrounded with < >, see comments below for the actual information content, they are value substitutions from the previous IPCONFIG command output! Do NOT type <computer_IP_address> into the command, that won't work. Also, the < and > in the text is to identify the parameters, they are also NOT used in the actual commands.

Do NOT include the <> either, they're just to identify the values for substitution.

IPCONFIG /ALL

PING <computer_IP_address>

PING <default_gateway_address>

PING <dns_servers>

PING 74.125.45.100

PING yahoo.com

Right click in the command window and choose Select All, then hit Enter to copy the contents to the clipboard.
Paste the results in a message here.

<computer_IP_address> - The IP Address of your computer, obtained from the IPCONFIG command above. (For Vista/Win7, the IPv4 Address)

<default_gateway_address> - The IP address of the Default Gateway, obtained from the IPCONFIG command above.

<dns_servers> - The IP address of the first (or only) address for DNS Servers, obtained from the IPCONFIG command above.

If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.



Generally this is an interference issue,and changing the channel would be one of the first things we suggest.But let's see.
Because it is a new laptop,I would think the adapter would be ok,obviously it works closer to the router,but you could go to the laptop makers web site and see if they have a more current driver for your adapter,just to cover that base.

[Homer1583]

First the screenshots. The first is in the living room with working internet, the second is in the bedroom when the internet dipped out.





The cmd stuff. By the way this was done in the living room with full connectivity.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Adam>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : AdamLaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ph.cox.net

Wireless LAN adapter Wireless Network Connection 4:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 40-61-86-9C-57-14
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . : ph.cox.net
Description . . . . . . . . . . . : 802.11bgn 1T1R Mini Card Wireless Adapter
#2
Physical Address. . . . . . . . . : 40-61-86-9C-57-15
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::2d21:a6b1:b1df:7c48%16(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, July 19, 2010 12:36:09 AM
Lease Expires . . . . . . . . . . : Tuesday, July 20, 2010 12:36:09 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 373318022
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-BB-95-3B-40-61-86-AE-9E-0B

DNS Servers . . . . . . . . . . . : 68.105.28.12
68.105.29.12
68.105.28.11
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 40-61-86-AE-9E-0B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2c58:f17:bb18:9399(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::2c58:f17:bb18:9399%17(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.ph.cox.net:

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

C:\Users\Adam>ping 192.168.1.101

Pinging 192.168.1.101 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Adam>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

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

C:\Users\Adam>ping 68.105.28.12

Pinging 68.105.28.12 with 32 bytes of data:
Reply from 68.105.28.12: bytes=32 time=28ms TTL=59
Reply from 68.105.28.12: bytes=32 time=11ms TTL=59
Reply from 68.105.28.12: bytes=32 time=13ms TTL=59
Request timed out.

Ping statistics for 68.105.28.12:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 28ms, Average = 17ms

C:\Users\Adam>ping 74.125.45.100

Pinging 74.125.45.100 with 32 bytes of data:
Reply from 74.125.45.100: bytes=32 time=83ms TTL=54
Reply from 74.125.45.100: bytes=32 time=81ms TTL=54
Reply from 74.125.45.100: bytes=32 time=79ms TTL=54
Reply from 74.125.45.100: bytes=32 time=83ms TTL=54

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

C:\Users\Adam>ping yahoo.com

Pinging yahoo.com [67.195.160.76] with 32 bytes of data:
Reply from 67.195.160.76: bytes=32 time=82ms TTL=54
Reply from 67.195.160.76: bytes=32 time=79ms TTL=54
Reply from 67.195.160.76: bytes=32 time=82ms TTL=54
Reply from 67.195.160.76: bytes=32 time=81ms TTL=54

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

C:\Users\Adam>

---------------------------------

And yes I've checked my laptop's website for drivers but there weren't any.

And I forgot to mention I tried changing channels. When I first opened the wireless setup page, it was on channel 9. I changed it to 6. No improvement. I changed to 11. No improvement.

[JohnWill]

Well, if the router and adapter are 7 years old, I'd start by upgrading the firmware on the router!


Some things you can try here, listed in the order you should try them.

1. For wireless connections, remove all the stored wireless profiles and search for networks. You'll have to enter the encryption key again, which is sometimes the issue for connection problems.
2. For wireless connections, change the channel on the router, I like channels 1, 6, and 11 in the US.
3. 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.
4. Update the network drivers (wired and wireless) on your computer to the latest available.
5. Update the firmware to the latest version available on the manufacturer's site.
6. Reset the router to factory defaults and reconfigure.

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

[pedroguy]

Hi:A couple of things puzzle me,but maybe I am easily puzzled.
Both wi-fi tests show the same signal strength,so perhaps not a signal issue.
Ping to the ipaddress fails.
Pings to the dns server are inconsistent.Time out and a 25% loss,
And yet other pings look good.
I agree with John.Those recommendations do solve many connection issues.
If after following those suggestions,still a problem,might I suggest disabling all firewalls,windows default and all antivirus suite apps running.
Then perhaps change the dns server.Like so:
https://store.opendns.com/setup/oper.../windows-vista
Other than that,I have no other ideas.

[Homer1583]

Originally Posted by JohnWill

Well, if the router and adapter are 7 years old, I'd start by upgrading the firmware on the router!


Some things you can try here, listed in the order you should try them.

1. For wireless connections, remove all the stored wireless profiles and search for networks. You'll have to enter the encryption key again, which is sometimes the issue for connection problems.
2. For wireless connections, change the channel on the router, I like channels 1, 6, and 11 in the US.
3. 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.
4. Update the network drivers (wired and wireless) on your computer to the latest available.
5. Update the firmware to the latest version available on the manufacturer's site.
6. Reset the router to factory defaults and reconfigure.

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

1. Tried it, no improvement
2. Tried it, nothing. I tried it on channels 6, 9, and 11 and neither made a difference.
3. As I said in my post, I tried this and it still isn't helping.
4. My wireless drivers are up to date
5. Did it, no change
6. Tried it, no change

Remember, the wireless works fine on the laptop if it's close enough to the router. Only when it's down the hall in the bedroom does it get spotty. But the desktop always in that bedroom gets internet perfectly.

[Homer1583]

Originally Posted by pedroguy

Hi:A couple of things puzzle me,but maybe I am easily puzzled.
Both wi-fi tests show the same signal strength,so perhaps not a signal issue.
Ping to the ipaddress fails.
Pings to the dns server are inconsistent.Time out and a 25% loss,
And yet other pings look good.
I agree with John.Those recommendations do solve many connection issues.
If after following those suggestions,still a problem,might I suggest disabling all firewalls,windows default and all antivirus suite apps running.
Then perhaps change the dns server.Like so:
https://store.opendns.com/setup/oper.../windows-vista
Other than that,I have no other ideas.

Later today I'll try the Xirrus test again and your link here to change the DNS servers.

[JohnWill]

Well, the laptop may simply have lousy range, some models are better than others. You might consider opening the access door on the bottom and checking if the antennas are connected properly to the wireless card, that's happened more than once.

[dant22185]

You might also consider trying a new adapter all together (USB). If the built in one has a lousy range like John suggested it may, then at least you could rule it out by trying a new connection method. I understand this might create a problem if you don't have one just simply lying around but it could at least give you a further understanding of what is going on.

I installed one for a client that was having similar problems with their old USB adapter on their new desktop computer with windows 7. It solved the issue right away. Here is what I purchased from best buy. Not very bad for price and does what it needs to do perfectly.

http://www.bestbuy.com/site/NETGEAR+...&skuId=6825233

[Homer1583]

Originally Posted by JohnWill

Well, the laptop may simply have lousy range, some models are better than others. You might consider opening the access door on the bottom and checking if the antennas are connected properly to the wireless card, that's happened more than once.

And this would cause the internet to work fine when close to the router, but crappy when only 10-20 feet away?

[pedroguy]

Surprisingly ,sometimes just a few feet makes a difference.I was setting up a network here on the Island.
In the laundry room,no wireless connectivity,move the router,or laptop,10 feet and bingo,wireless.So,yes it is possible.

[JohnWill]

Correct, the other issue could be wireless interference, that's why we were looking at the WiFi scanner. You might try changing the channel on the router, say to 3 or 9, and see if that makes a difference.

[TerryNet]

The purpose of the antenna is to allow radio communication over (relatively) long distances. If it is disconnected or only loosely connected your range will be severely reduced.

[Homer1583]

Originally Posted by dant22185

You might also consider trying a new adapter all together (USB). If the built in one has a lousy range like John suggested it may, then at least you could rule it out by trying a new connection method. I understand this might create a problem if you don't have one just simply lying around but it could at least give you a further understanding of what is going on.

I installed one for a client that was having similar problems with their old USB adapter on their new desktop computer with windows 7. It solved the issue right away. Here is what I purchased from best buy. Not very bad for price and does what it needs to do perfectly.

http://www.bestbuy.com/site/NETGEAR+...&skuId=6825233

I might do something like this. The only thing is I'm going back to school in a month, so if I order something on newegg for much cheaper, it'll arrive in a week or so, then it'll only be useful for a few weeks.

But later I'll try opening this case and seeing if the adapter itself is in good shape.

[Homer1583]

Originally Posted by JohnWill

Correct, the other issue could be wireless interference, that's why we were looking at the WiFi scanner. You might try changing the channel on the router, say to 3 or 9, and see if that makes a difference.

To you and Terry, I see. A little later I'll try taking a look and seeing if its loose. I could also try changing the channel to 3. I've played with the channels before, but my understanding is that for changing channels to matter, there has to be other networks in close range that have the same channel. Would you say any of the other networks in my Xirrus snapshot are close enough to interfere with my network? Especially considering that the wireless desktop works fine?