Page 1 of 3 123 LastLast
Results 1 to 10 of 23

Thread: Limited or No Connectivity WinXP SP2 Bug

  1. #1
    Variable Bitrate Bailey's Avatar
    Join Date
    Nov 2004
    Location
    NYC
    Posts
    274

    Limited or No Connectivity WinXP SP2 Bug

    I'm sure some of you have heard of this problem. There is a NAT bug in the SP2 for WinXP which Microsoft has addressed but not fixed yet. It causes a wireless (and sometimes wired!) connection to not be able to acquire an IP address, claiming the "Limited or No Connectivity" error message. MS deployed a hotfix which doesn't work. Many people have tried fixing it different ways but I have tried them all, and I have resorted to the last step: downgrading to WinXP SP1. I have just nlite'd an ISO and I'm going to install it in a minute.

    I have wasted an entire day trying to fix it. Things I have tried to fix it:

    Micro$oft's hotfix
    Some .reg file I found
    Cleaning/resetting winsock
    Setting LAN IP manually
    Setting nic speed manually
    Shutting down all devices for several minutes, restarting router, ap, computers (in that order)

    Last step - Uninstalling SP2

  2. #2
    Maximum Bitrate fantomas's Avatar
    Join Date
    Nov 2003
    Location
    CT
    Posts
    754
    welcome to the wonderful world of windows. i installed sp 2 back in august and completely lost my network. i ended up having to reinstall windows to get everything working again. i have wasted many days on this operating system.
    rebuilding carpc... kinda..

  3. #3
    Raw Wave rando's Avatar
    Join Date
    Mar 2004
    Location
    Redondo Beach, CA
    Posts
    1,973
    I've never had any problems with XP SP2 -- using wired or wireless networks. It just works.

  4. #4
    Newbie
    Join Date
    Dec 2004
    Posts
    7
    I have been using XP SP2 & have no issues. You just need to disable the firewall that comes along.

  5. #5
    Constant Bitrate
    Join Date
    Oct 2004
    Posts
    131
    I've had great luck with sp2. I get those limited connectivity messages, but usually cause I'm pushing the limits of my wifi networks around home. When it gets a better signal, it works fine. I think the linksys software that came with all my cards works better at keeping a connection, but then I have too many things running and it took too long to connect to "open" aps.

    Dave

  6. #6
    Variable Bitrate Bailey's Avatar
    Join Date
    Nov 2004
    Location
    NYC
    Posts
    274
    Quote Originally Posted by big_cali_dave
    I've had great luck with sp2. I get those limited connectivity messages, but usually cause I'm pushing the limits of my wifi networks around home. When it gets a better signal, it works fine. I think the linksys software that came with all my cards works better at keeping a connection, but then I have too many things running and it took too long to connect to "open" aps.

    Dave
    This isn't an issue with the signal. It's an issue with the software used to control it. The strength of the signal could be 100% but it still gives an error.

    Downgrading to WinXP SP1 fixed the problem.

  7. #7
    Maximum Bitrate
    Join Date
    Nov 2003
    Posts
    509
    Its more of a driver issue, my dlink network card stopped working after i got SP2, and the only driver on dlinks website was the driver that came with the card. my buddy installed the G network card driver (this was a B) on the same card and it worked fine

  8. #8
    Newbie
    Join Date
    Jan 2005
    Posts
    55
    its not a serious problem.

    it happens because the network card doesn't acquire the full network address usually or it cna be caused from spyware.

    Usually you can fix it quick by right clicking on the network connection and clicking repair. if that doens't get it their is something called VBSockFix which will get it all.

  9. #9
    Raw Wave Laidback's Avatar
    Join Date
    Oct 2003
    Location
    Madrid
    Posts
    1,984
    Quote Originally Posted by marley1
    if that doens't get it their is something called VBSockFix which will get it all.
    And where would that be?

  10. #10
    _
    Join Date
    Mar 2004
    Location
    Little Elm, Texas
    Posts
    13,500
    Quote Originally Posted by lara
    I have been using XP SP2 & have no issues. You just need to disable the firewall that comes along.
    not true!

    at work we have just gotten in something around 50 new computers. We immediately turn off the firewall since we can't have it on while the computers are on the network.....it poses a problem for us trying to see the computer....After booting them all up and starting to install the needed software, we get the SAME error message. We were thinking that it was a problem with the network.....but I guess not....I will sure be forwarding this on to the guys at work!
    Jan Bennett
    FS: VW MKIV Bezel for 8" Lilliput - 95% Finished

    Please post on the forums! Chances are, someone else has or will have the same questions as you!

Page 1 of 3 123 LastLast

Similar Threads

  1. Bug Tracking (sorry long but please read)
    By liquid_smoke in forum Software & Software Development
    Replies: 23
    Last Post: 04-22-2005, 04:12 PM
  2. WinXP SP1 vs SP2
    By egeekial in forum Software & Software Development
    Replies: 1
    Last Post: 12-12-2004, 01:14 PM
  3. GS Reciever, WinXP SP2, and Hibernation
    By captain_jim1 in forum GPS
    Replies: 10
    Last Post: 09-19-2004, 04:12 PM

Bookmarks

Posting Permissions

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