Intermittent Ability to Connect to Wireless Network

Toggle sidebar Toggle sidebar
Shivvlan

Shivvlan

Honorable
Apr 7, 2013
9
0
10,510
Hi; I just recently got a new computer and got a new wireless card to go with it. Since I've installed it, however, I've had nothing but trouble attempting to connect to my wireless network. The card can see the network, with 5 bars; but when I click 'Connect' it waits for about 3 seconds, then throws up the 'Windows is unable to connect' dialog (in the network connections window it seems to sit permanently on the message 'acquiring authentication'). The thing is, if i KEEP just hitting connect it will, eventually (the longest it took was 1hour and a half), connect; but it will still throw up the 'Windows is unable to connect' dialog, even if it has connected.
So far I have uninstalled the drivers and re-installed them in safe mode; made sure I had the latest drivers from the website. I've rebooted everything even remotely associated with the connection. I've checked the card is seated correctly, I've checked the settings, set a static IP, disabled IPv6, flushed everything in every way and given it some very serious looks. Nothing seems to work to get this thing to connect consistently, and to be honest I'm a little confused as to how it will randomly connect while still throwing the error if I try for long enough.

The computer is running Windows 7 home; the Wireless adapter is a TL-WN851ND; and the router is a Dynalink RTA1025WE (which apparently only ever existed in New Zealand).
This is the only device in the house that has an issue connecting, we have three laptops, one LAN connected desktop, another wireless desktop, netbooks, ipads, phones, games consoles etc all which connect with no issue what-so-ever (NOT all at the same time).

Oh, I also have zero issue with the network once I manage to get connected. Once connected the signal is 5-bars, fast and has no dropping or stuttering. The only issue is getting connected in the first place.

To be honest, networking is not my forte; so, I'm at a complete loss. Help?
 
Sort by date Sort by votes
Shivvlan

Shivvlan

Honorable
Apr 7, 2013
9
0
10,510


Yes, all the drivers are up-to-date. When i first installed the driver and had the issue I went straight to the adapters website and downloaded their most recent drivers in the hopes of it being an easy fix. The adapter did come with a software bundle as well as the driver, but it was buggy immediately so I completely uninstalled it (and the driver) and re-installed the driver I got from the website instead, without the utility.

I'm not sure how to check if the install is corrupted? I have uninstalled the driver and re-installed it twice now, though.
 
Upvote 0 Downvote
Shivvlan

Shivvlan

Honorable
Apr 7, 2013
9
0
10,510


No, I haven't done anything to the wifi channel. As I said, once the computer is connected I have no issues at all; it's getting connected in the first place that is the issue.

 
Upvote 0 Downvote
Shivvlan

Shivvlan

Honorable
Apr 7, 2013
9
0
10,510


Wouldn't that be cause issues for our other devices as well? I would assume that we would have trouble connecting for more than just the new wireless card, which we don't; and also that the new wireless card would occasionally connect immediately, which it doesn't.
 
Upvote 0 Downvote
Shivvlan

Shivvlan

Honorable
Apr 7, 2013
9
0
10,510


I'd love to give it a try, but I cannot find a way to change that setting at all. As far as I can tell most wireless adapters have an option in the advanced properties from the device manager, but mine doesn't appear to, and the TP-Link website only has information regarding it's utility program, which didn't work for me so I'm not using it.

 
Upvote 0 Downvote
remixedcat

remixedcat

Honorable
Nov 3, 2012
184
0
10,710
The router's WLAN channel is what would need to be changed.

I had an LG Optimus that only would stay connected to my old Netgear if I had it on ch 9.

(I now have an Amped R20000G and still have it on 9 and have gotten a new phone though)
 
Upvote 0 Downvote
Shivvlan

Shivvlan

Honorable
Apr 7, 2013
9
0
10,510


I have not had the chance to change the channel on the router; however, I have had one small victory that hasn't 100% fixed the problem, but has made it a little better.
Last night I ran a chkdsk and sfc then used the command "netsh winsock reset catalog" to reset the winsock; after the reboot my computer connected instantly. Pushing it a little further I disconnected on purpose and tried to reconnect, but couldn't; but, after a reboot the computer connected immediately again. So, it seems now I need to reboot my computer every time I want to connect; but I still cannot get a connection whenever I try to connect.

One step at a time, I guess; but now I'm unsure what to do to make it connect without a reboot?
 
Upvote 0 Downvote
Shivvlan

Shivvlan

Honorable
Apr 7, 2013
9
0
10,510


Yes. I did that in between the scans and netsock commands. The commands didn't work because I kept getting back the 'Media disconnected' error. Right now, while I'm connected, the (ipconfig /all) is returning the correct information; but, when I disconnect, and can't reconnect, the wireless adapter changes to 'media disconnected'; which I'm assuming is why I can't establish a connection. I'm throwing some google-fu at that subject now, actually, but not getting far.

 
Upvote 0 Downvote
Shivvlan

Shivvlan

Honorable
Apr 7, 2013
9
0
10,510


I don't have another one to try; but there is another desktop computer in the house using a different model TP-Link Wireless adapter that has no issues connecting to the network at all. I'd try using it in my computer, but I've been informed I can pry it from the owners cold dead hands. lol
 
Upvote 0 Downvote
remixedcat

remixedcat

Honorable
Nov 3, 2012
184
0
10,710
Have you tried to repair windows to eliminate the possibility of something getting corrupt? Also be sure your OS is up-to-date.

If you've tried everything you can in Windows then the card is bad and needs RMAed.
 
Upvote 0 Downvote
Shivvlan

Shivvlan

Honorable
Apr 7, 2013
9
0
10,510


Like I said originally, the computer is brand new, it was literally built a week ago; I've install and upgraded everything on it and I ran a check and repair last night with everything else.
So yeah; I guess if there are no other ideas about what could be wrong I'll have to get onto the place I bought it from. I've tried talking to TP-Link directly, but I can't seem to get them to understand that re-installing the driver 600 times isn't going to help.

Well, thank you for your help.

To recap for anyone who may find this thread with similar issues, my partial fix was opening the command prompt in Admin mode and using:

"chkdsk /f /r"
"sfc.exe /scannow"
(these two will hopefully find and repair any errors)

"ipconfig /release" (to release current IP)
"ipconfig /renew" (to renew the IP)

"netsh winsock reset catalog" (to reset winsock entries)
"netsh int ip reset reset.log hit" (to reset TCP/IP stack)
Reboot.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom