Overclock.net › Forums › Software, Programming and Coding › Networking & Security › [Updated] ASUS USB-AC53 Adapter disabling itself?
New Posts  All Forums:Forum Nav:

[Updated] ASUS USB-AC53 Adapter disabling itself?

post #1 of 6
Thread Starter 
EDIT: Go to the fifth post for the latest on the issue. It's way different than I originally realized!

I have an ASUS USB-AC53 with an BCM43526 chipset that's been having a lot of connectivity issues. See all these reviews of people saying how awful it is? http://www.amazon.com/ASUS-Wireless-AC1200-Adapter-USB-AC53/product-reviews/B00BTWJAAE/ref=cm_cr_dp_see_all_summary?ie=UTF8&showViewpoints=1&sortBy=byRankDescending
I don't even CARE that it's USB 2.0, I just want it to work without disconnecting even though I'm practically sitting on top of the router. Multiple routers, computers, configurations. Same result. It drops the connection and stops seeing access points unless the adapter is reset or it is physically removed and plugged back in.

It's the ASUS driver/software fault. No Q.A. whatsoever. It even has common spelling mistakes! sicksmiley.png Disconnecting every 5-15 minutes at times. I've been stuck with it in a hotel for 2 weeks. axesmiley.png

Anyway, check this out! Someone installed a generic/broadcom driver for it and fixed their USB-AC56!: http://www.amazon.com/review/RFG921X64NMVU/ref=cm_cr_dp_title?ie=UTF8&ASIN=B00FB45USW&channel=detail-glance&nodeID=541966&store=pc
I'm trying to do the same thing, but I have no Ethernet or any other Wifi adapter to check windows updates with, although I do believe that I will not find anything for it as I tried it some many months ago and ended up needing to get the driver from ASUS. I could be wrong though.

Broadcom doesn't make Windows drivers as far as I can tell. At least for BCM43526 they don't. I checked here to try to find a similar device with the same chipset offering a driver in hopes that it would install, but I couldn't get any of them to work. Warning: Spoiler! (Click to show)
I'm running Windows 8.1 x64. Any help would be GREATLY appreciated. smile.gif
Edited by cookieboyeli - 10/3/15 at 5:23pm
post #2 of 6
Thread Starter 
Bump

This is what I'm dealing with.
A lot of it is the Hotel Wifi but not all of it. I'm pretty sure packet loss and dropouts are from my adapter.
7% packet loss and constant .6-1 second dropouts. Packet loss ranges from 0 to 12%. Dozens of times at many hours of the day and night. I'm on the fourth floor so there shouldn't be interference from anything but other hotel routers. Dropouts range from .6 to 1 second sometimes 1 transient outage during the test, sometimes 10. It's all "random" as far as I can tell. The uplink buffer ranges from 1100ms to 1300ms, average of 1200ms. Downlink buffer between none and 240ms, average 120ms. Ping is all over the place. When it's working right it's at 18-32ms, but can go up to 60ms "if it feels like it" My ping to the router is 1-4ms, spiking to 6ms.

http://n2.netalyzr.icsi.berkeley.edu/summary/id=36ea240d-11261-01e339b7-1bac-4db1-9236

Tech support has done everything they can do on the software side, messing with router configuration, rebooting etc. with little to no improvement. Ethernet is down, they've been unable to contact the hotel tech who is supposed to fix it for 2 weeks. I'm stuck here for another week and when I go back home I'm stuck in a room without Ethernet as well.
Edited by cookieboyeli - 9/13/15 at 1:37am
post #3 of 6
Thread Starter 
New info! Packet loss is NOT between me and the router. I pinged it 100 times and got between 1-6ms 2ms average. Not exactly the modern >1-1ms but hey it's hotel Wireless G which was low end when they got it in 2008. rolleyes.gif

I read a lot of reports about packet loss and to a lesser extent high uplink buffer with AT&T's Motorola NVG510 which is surprisingly 5 years old and still by far the most common. frown.gif The hotel is using AT&T and likes to neglect technology. That's probably what they have.

Here's me pinging google.com and forgetting about it for 20 minutes. Forgot CMD cuts some off at the beginning, filled in the command.

ping google.com -t -f -l 1400

Reply from 173.194.123.32: bytes=1400 time=54ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=58ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=84ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=64ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=63ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=51ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=93ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=54ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=62ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=61ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53 Warning: Spoiler! (Click to show)
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=49ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=65ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=472ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=57ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=52ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=44ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=47ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=48ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=386ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=59ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=44ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=51ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=55ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=49ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=45ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=51ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=50ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=303ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=46ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=57ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=49ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=62ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=625ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=47ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=48ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=60ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=44ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=50ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=47ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=69ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=332ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=48ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=49ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=502ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=48ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=76ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=71ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=48ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=56ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=72ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=52ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=45ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=449ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=46ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=52ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=51ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=482ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=54ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=51ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=45ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=542ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=43ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=49ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=44ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=55ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=49ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=605ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=47ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=51ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=77ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=38ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=49ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=55ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=51ms TTL=53
Request timed out.
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=59ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=40ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=37ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=42ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=39ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=584ms TTL=53
Reply from 173.194.123.32: bytes=1400 time=41ms TTL=53

Ping statistics for 173.194.123.32:
Packets: Sent = 1335, Received = 1241, Lost = 94 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 649ms, Average = 58ms
Control-C

The random disconnects are still my main solvable issue though.
I really need a replacement driver.

EDIT: Hopefully a new driver will have some positive effect on the uplink buffer as well, although I do believe the majority of the issue is between the hotel modem and AT&T. I had a similar wired issue at my house a few years ago and it turned out to be bad coaxial cabling, bad splitters, and bad connection to the pole. Charter wasn't to blame at all, they fixed it as soon as they knew it was the issue.
After the modem the problem falls on the ISPs shoulders to fix. Tech support is now aware of all this and is getting in touch with AT&T to try and solve the issues. They're also hopefully going to communicate "This is what happens when you're cheap and don't trust your techs!" sozo.gif To the hotel! biggrin.gif
Edited by cookieboyeli - 9/13/15 at 1:50am
post #4 of 6
Thread Starter 
Bump - Dropouts are still present and bad as ever.
I've lost the connection anywhere from 5 to 16+ times a day. ... For the past two weeks.
On average it's probably around 8 times per day. So basically I've had to reset my connection 112 around times since I've been here. Feels like more than that though.
Please help me. redface.gif
Edited by cookieboyeli - 9/15/15 at 2:29am
post #5 of 6
Thread Starter 
UPDATE

My connection drops when I am uploading or downloading at the maximum bandwidth in this hotel which is around 13/0.8 (yes I'm still in the hotel...). I usually get a lot of packet loss to the router when using high amounts of bandwidth too. Within 60 seconds I might experience 3-20% packet loss - if it doesn't disconnect. It usually disconnects instantaneously upon sudden load, upload more so. Taking a speed test can actually cause the connection to drop!
When this happens, windows shows that I am connected for up to a few minutes, then the adapter disables and I CANNOT RE ENABLE IT through software, I must physically unplug and replug the device and the connection is reestablished instantly.

Tech support told me it could be an issue with the POE or power over ethernet system the router is hooked up with. A ticket was opened, but they never get anything done. They've been "trying" to fix the ethernet for over a month and the hotel has been trying to fix the internet issues with them for A YEAR now.
We have at least been able to verify that everything in the configuration is correct now and not causing an issue. At first there was some messed up NAT time server setting that caused the router to get 100ms spikes every 15 seconds and set the time to 1979!! AND a seperate issue that cuased it to reboot every 30-60 minutes which was part of the problem at first. In addition to those issues, almost every router out of the 13 here were on channel 6. Whoever set this up must have literally been retarded. Thankfully tech support agreed with me and was able to fix all these issues!

I am using the Acrylic Wi-Fi and PingPlotter programs to monitor packet loss and wireless information. There is no interference. They switched me to channel 11 which has one other access point at -90dbm which I can see (I can see 6 of the 13 access points the hotel has). There is an issue with numerous switches which they are "working on" (yet have made 0 progress when I check the ticket). But that shouldn't be causing this specific issue.

The connection does "pause" though when I use the microwave... I think I'm going to get rid of it before it gets rid of me! haha blinksmiley.gif

Does ANYONE have any ideas whatsoever as to what could be causing the adapter to disable itself and require a hard reset though? (Sometimes it needs two). It's as if the adapter is crashing and locking up.
post #6 of 6
Thread Starter 
Found the solution. https://www.youtube.com/watch?v=N9wsjroVlu8

ALFA AWUS036ACH gets 25-30 dbi better signal, no more dropouts ever, I can see access points much further away and connect to many more. Even better is the jittery 1-130ms ping to the access point is now a SOLID 0-1ms 100% of the time. It's excellent. Best Wifi AC adaptor on the planet (that you can afford). Buy it from rokland on ebay or elsewhere for $50. It's well worth it.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Networking & Security
Overclock.net › Forums › Software, Programming and Coding › Networking & Security › [Updated] ASUS USB-AC53 Adapter disabling itself?