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.

    Cable dies, only solution is to shut down computer.

    Discussion in 'Networking and Wireless' started by dthm, Feb 4, 2007.

  1. dthm

    dthm Notebook Enthusiast

    Reputations:
    0
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    5
    Hi all,

    Recently I've been experiencing issues with my cable connection.
    The problem arises after my computer has been idling for awhile, then I can no longer load websites and the Local Area Connection Status says packets received is 0. I experience this problem two or three times a day.

    The only way to solve this problem is to shut down my computer, unplug my modem, and wait for a minute before I switch my computer bag on.

    I called my ISP provider and they couldn't pinpoint my problem, so I'm wondering if the connection issue that I'm experiencing is hardware related. Thank you.
     
  2. WackyT

    WackyT Notebook Deity

    Reputations:
    906
    Messages:
    1,389
    Likes Received:
    1
    Trophy Points:
    56
    If you need to reboot your cable modem in order to get back online, I'd have to say it's a cable company problem.
     
  3. LIVEFRMNYC

    LIVEFRMNYC Blah Blah Blah!!!

    Reputations:
    3,741
    Messages:
    2,382
    Likes Received:
    0
    Trophy Points:
    55
    I had the same problem with my RCN cable when I first got my HP Desktop, only to realize that it was most likely the bundled Norton Virus 2006 that was the problem. I always suspected it.

    I say this because after I did a recovery from recovery discs, I quickly removed Norton and loaded avast instead. I never had the problem again since.

    So if your using Norton, there could be a huge chance of it being the problem.