The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Samsung Chronos with Intel 6235 takes long time to connect in Windows 8.1

    Discussion in 'Samsung' started by rpeters83, Oct 18, 2013.

  1. rpeters83

    rpeters83 Notebook Consultant

    Reputations:
    0
    Messages:
    245
    Likes Received:
    5
    Trophy Points:
    31
    It seems that ever since I updated to 8.1 this started happening. I have Intel version 15.9.1.2 drivers and the AP is an ASUS RT-N66U. All other devices connect fine on both bands. As of recently, if I boot up, it won't connect, but then once I log in, it seems to connect for a few seconds, then disconnects for a few minutes, then connects. After it finally connects, it's stable.

    I have the same issue when I'm resuming from sleep. It won't connect. If I try to manually connect it will show that no connections are available. If/when a list of APs does show up, and I try to connect, it takes a minute or two for it to finally connect. Again, once it finally connects, it's stable.

    Is there a way to completely remove all my wireless information? Did 8.1 remove the right-click on a AP to "forget" it? Odd.

    I've tried both MS and Intel drivers. I've also disabled power management on the device. I've also just tried the newer Intel drivers for 8.1. Oddly, it says version 16 on the website but only installs version 15.10...

    Any ideas? Thanks.
     
  2. rpeters83

    rpeters83 Notebook Consultant

    Reputations:
    0
    Messages:
    245
    Likes Received:
    5
    Trophy Points:
    31
    Anyone? It really seems to be just this laptop, and the issue is 100% consistent: boot up, ~ minute before it finally connects. Thanks.
     
  3. hfm

    hfm Notebook Prophet

    Reputations:
    2,264
    Messages:
    5,296
    Likes Received:
    3,045
    Trophy Points:
    431
    You can forget the networks with a shell command:
    netsh wlan delete profile name=[profile name]

    Profile name is probably the ssid. Use 'netsh wlan show profiles' if you aren't sure.

    I have the same router and a gamer 7 with the 6235.. 5ghz is still a little flaky sometimes after waking from sleep. Once it connects it's solid and lighting fast though.

    Definitely deleting the profile and reconnecting can help especially if you upgraded to the latest firmware on the router or changed drivers.

    Don't forget to reset to default in the rt-n66u by holding reset down for 10 secs if you upgrade firmware.
     
  4. rpeters83

    rpeters83 Notebook Consultant

    Reputations:
    0
    Messages:
    245
    Likes Received:
    5
    Trophy Points:
    31
    Interesting. So you have a Samsung laptop with the same wifi card, and you don't have issues where it takes an extra minute to connect from a cold boot? I've previously tried clearing any old wifi profiles and tried several versions of drivers and there is no difference.

    For me, if I wake it from sleep, it's perfect and connects immediately (I have it set to allow the computer to put the card to sleep). My only issue is from a cold boot.

    Also, it is not the AP in my case, as I've tried another AP on my network as well as duplicated the issue on a company wireless network.

    So, my next guess is to do a refresh on windows 8 and see if there might be something there. Previously I noticed that Intel had installed their own PRO set wireless services, which I thought would be interfering with it at boot, but even after uninstalling those, it made no difference.

    The only reason it's annoying is because I have apps that launch on startup that are failing because there's no network connection, forcing me to restart them. I see no oddities in the event log either and, again, don't recall this happening prior to 8.1.
     
  5. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,841
    Likes Received:
    2,165
    Trophy Points:
    581
    Have you tried the latest WiFi driver from Intel? They have spent the past 6 months or so slowly trying to resolve connection issues with the 6235. More in this thread. Uninstall the Intel driver / Proset package before installing the latest.

    Last week I was having similar problems with the slow WiFi connection on startup / resume. I traced the problem to the WLAN AutoConfig service being slow to put it boots on. I can't remember what, if anything, I did but this week it's connecting quickly. Make sure that service has the Startup type of Automatic and not Automatic (Delayed Start).

    John
     
  6. rpeters83

    rpeters83 Notebook Consultant

    Reputations:
    0
    Messages:
    245
    Likes Received:
    5
    Trophy Points:
    31
    Thanks. I believe I checked that service and it was Automatic, but I'll verify.

    In regards to the latest driver, I tried that, but it kept saying 15.10 was the latest, even though I installed 16.X from Intel's site. I remember Merlin on smallnetbuilder mention that driver package supports more than just the 6235 and the latest for my card WAS 15.10.

    Thanks for that thread link. I don't believe I saw that before. Thanks.
     
  7. rpeters83

    rpeters83 Notebook Consultant

    Reputations:
    0
    Messages:
    245
    Likes Received:
    5
    Trophy Points:
    31
    So this is interesting. I did a factory (day 1) reset of the machine (I had to, due to another issue I had) and the wireless connects instantly.

    I think the 8.1 update hosed things up for this card.
     
  8. rpeters83

    rpeters83 Notebook Consultant

    Reputations:
    0
    Messages:
    245
    Likes Received:
    5
    Trophy Points:
    31
    Just some more notes. I did a factory reset, then a Windows 8 refresh, then a 8.1 update from the store.

    I had some issues with wireless at first, as it installed microsoft's own 15.10 driver and it was having trouble finding the gateway, though it had a valid configuration. Very strange. Then I went with Intel's 15.5 and it got BETTER, but still had some issues.

    I'm currently on Intel's 15.10 and it seems to be better. It's now connecting at startup after a cold boot. I also removed the Intel services that were installed and SO FAR it's solid.
     
    John Ratsey likes this.