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 Series 3 Wireless Issue

    Discussion in 'Networking and Wireless' started by huai, Nov 2, 2011.

  1. huai

    huai Notebook Consultant

    Reputations:
    5
    Messages:
    238
    Likes Received:
    2
    Trophy Points:
    31
    I bought a Samsung series 3 two weeks ago. It has an Intel Centrino N130 wireless module.

    I can't get online when a network requires you to open a proxy page in your browser and sign in / accept the terms (like you often see in coffee shops). I can see that network status is connected. I get a bubble popup that says "click here to open a browser to provide additional information." However if I open a browser window it never loads anything, just sits there indefinitely loading. I have confirmed this behavior on 4 different such networks and had my friends being able connect (so it's not the network).

    Opening the connection status and clicking diagnose under Win 7 tells me that the laptop cannot reach the DNS server. Same error in every case.

    Looking at the IPV4 properties, I see that both IP Address and DNS server is set to be obtained automatically.

    Networks without a login page work just fine whether open or encrypted.

    I'm going to download the latest drivers from Intel tonight to see if that helps. Does anyone have any other suggestions?
     
    huai, Nov 2, 2011
    #1
  2. huai

    huai Notebook Consultant

    Reputations:
    5
    Messages:
    238
    Likes Received:
    2
    Trophy Points:
    31
    Tried flushing DNS, renewing my IP address, all to no avail.

    Looks like the culprit is a recent IE9 patch. Firefox works just fine. Farewell IE. Count me a firefox user.
     
    huai, Nov 3, 2011
    #2