Results 1 to 7 of 7
  1. #1
    New Lounger
    Join Date
    Dec 2009
    Posts
    17
    Thanks
    0
    Thanked 1 Time in 1 Post
    My wife has a Samsung N120 Netbook (running XP SP3) which has very unreliable wireless connectivity.

    Regardless of the specific wireless network it randomly drops the connection. Usually a reboot resolves the issue but not always and it is sometimes necessary to reboot multiple times.

    As I said, the issue is network independent and has happened at two separate locations which both show no issues for other users.

    When the connection went down a few minutes ago, we ran "ipconfig /renew /all" and got the following message:
    "The operation failed as no adaptor is in the state permissible for this operation."

    She is also unable to even ping the router (which is simultaneously working fine for other wired and wireless devices).

    The issue is unrelated to the distance from the router as we've seen it happen when they're both on the same desk side-by-side.

    Samsung pushed an update to the network card's drivers last week which had no impact.

    One other possibly pertinent piece of information is that in the "Select a Network" wireless tool, 5 bars of signal strength are shown for our home network (to which we were just connected).

    We are open to all suggestions!

  2. #2
    Super Moderator Deadeye81's Avatar
    Join Date
    Dec 2009
    Location
    North Carolina, USA
    Posts
    2,654
    Thanks
    7
    Thanked 113 Times in 97 Posts
    Hi Melvyn, and welcome to the Lounge!

    Has the Samsung always had this difficulty or is it a more recent development? Does it happen to still be under warranty?

    Did Samsung provide a wholly new driver for your wireless card or was it just an update to fix specific problems?

    If you can gather the wireless card model number and brand, you might be able to download and install a new driver from the wireless card manufacturer rather than from Samsung. I would check in Device Manager for that information. If you find the information on the card vague, you could download System Information for Windows Freeware version (SIW), which should identify all your hardware in detail.

    It may be worthwhile to download and install updated chipset drivers for your motherboard from Intel, and also a BIOS update, particularly if this problem has been with you from the day you purchased the netbook.

    If the above does not help, then you may need a new wireless card, or possibly a connector is not firmly connected, which can cause a failure when things heat up.
    Deadeye81

    "We make a living by what we get, we make a life by what we give." Sir Winston Churchill

  3. #3
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,203
    Thanks
    49
    Thanked 989 Times in 919 Posts
    Maybe the wireless card is being powered down by Windows. Try setting the wireless card so that Windows does not turn it off - in the card properties.

    cheers, Paul

  4. #4
    New Lounger
    Join Date
    Dec 2009
    Posts
    17
    Thanks
    0
    Thanked 1 Time in 1 Post
    Sorry for the delayed response and thank you both for your quick offers of help.

    I'll answer each question in turn.

    Quote Originally Posted by Gerald Shepard View Post
    Has the Samsung always had this difficulty or is it a more recent development? Does it happen to still be under warranty?
    It was fine to start with and this is a reasonably recent development.

    Quote Originally Posted by Gerald Shepard View Post
    Did Samsung provide a wholly new driver for your wireless card or was it just an update to fix specific problems?
    It was a standard update through the Samsung Update Plus tool.

    Quote Originally Posted by Gerald Shepard View Post
    If you can gather the wireless card model number and brand, you might be able to download and install a new driver from the wireless card manufacturer rather than from Samsung.
    The card is the Atheros AR5007EG Wireless Network Adapter. According to this site we have the most current version of the driver (7.7.0.523).

    Quote Originally Posted by P T View Post
    Maybe the wireless card is being powered down by Windows. Try setting the wireless card so that Windows does not turn it off - in the card properties.
    The Advanced tab of the properties window for the card has 6 different "Poser Save" properties which can be edited:
    • Power Save Legacy Algorithm (set to "PS non Poll")
    • Power Save Mode (set to "Normal")
    • Power Save Policy (Background) (set to "Legacy Power Save")
    • Power Save Policy (Best Effort) (set to "Legacy Power Save")
    • Power Save Policy (Video) (set to "Legacy Power Save")
    • Power Save Policy (Voice) (set to "Legacy Power Save")

    I tried setting the Power Save Mode property to "Off" but it made no difference.

    One new piece of information I can add is that once the machine has successfully connected it will usually stay connected as long as it is in constant use. If we stop using it for a few minutes or if it is put on standby and then we try to resume, it will get stuck on "Acquiring Network Address" until the attempt to do so times-out.

  5. #5
    New Lounger
    Join Date
    Dec 2009
    Posts
    17
    Thanks
    0
    Thanked 1 Time in 1 Post
    Problem solved!

    I found this thread:
    http://www.avforums.com/forums/lapto...g-nc-10-a.html

    and followed the advice to uninstall the driver for the network card and install a very old driver instead (v5.3.0.56 from 2007!). It worked!

    A product bought at the end of 2010 with drivers from April 2010 could only be made fully-functional by removing those drivers and using 3yr old software in its place. Crazy but true!

  6. #6
    Super Moderator Deadeye81's Avatar
    Join Date
    Dec 2009
    Location
    North Carolina, USA
    Posts
    2,654
    Thanks
    7
    Thanked 113 Times in 97 Posts
    Melvyn,

    Thanks for posting your solution! Even though the faulty driver came installed on your Samsung Netbook, this driver experience you've had should cause everyone to think twice about installing the most recent drivers just because they are available. Best to leave the new driver alone unless there is a clear need to solve a functionality issue.

    A three year old driver solved the issue; who would have thunk it?
    Deadeye81

    "We make a living by what we get, we make a life by what we give." Sir Winston Churchill

  7. #7
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,203
    Thanks
    49
    Thanked 989 Times in 919 Posts
    A three year old driver solved the issue; who would have thunk it?
    Was my next suggestion. ;-))

    cheers, Paul

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •