Announcement

Collapse
No announcement yet.

Limited or No Connectivity WinXP SP2 Bug

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • 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
    http://www.cardomain.com/id/seanklsc

  • #2
    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..

    Comment


    • #3
      I've never had any problems with XP SP2 -- using wired or wireless networks. It just works.
      2004 4runner

      Comment


      • #4
        I have been using XP SP2 & have no issues. You just need to disable the firewall that comes along.

        Comment


        • #5
          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

          Comment


          • #6
            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.
            http://www.cardomain.com/id/seanklsc

            Comment


            • #7
              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

              Comment


              • #8
                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.

                Comment


                • #9
                  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?
                  Laidback


                  The ultimate CarPC - Wow!

                  Comment


                  • #10
                    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!

                    Comment


                    • #11
                      Originally posted by marley1
                      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.
                      again, not true, the computers we have at work have NO spyware when we get them, this even happens to comuters that we put a new image on, which we know is 100% free of spyware.....

                      but I will be looking into the VBSockFix for sure though!
                      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!

                      Comment


                      • #12
                        its located here

                        http://www.spychecker.com/program/winsockxpfix.html

                        i didn't say it was only caused by spyware, its caused sometimes by that, other times when it doesn't grba a full netwrok address.

                        usually repairing the connection will do it.

                        Comment


                        • #13
                          repairing the connection has never worked for us in this instance.....usually just letting it sit for a bit repairs it better than anything....lol
                          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!

                          Comment


                          • #14
                            so repairing and letting sit or running the socket fix is the same thing.

                            lettting it sit gives it more time to repair itself or acquire a new ip/dns...

                            i hav ehte problem alot when im working on clients computer, plugging em in fast to our switches and kvm at work sometimes doesn't get em to connect right away.

                            generally i have to either repair the connection, assign manual ip if im too lazy to reall fix it(or when im just gonna be formatting it anyway and need to just backup a few things), releasing the sockets(socketfix) or when i restart.

                            it can be caused by others, there is the known bug for it but i dont really consider it a bug

                            Comment


                            • #15
                              This is a very annoying bug. I work with quite a few desktops and laptops on a daily basis (all different), and many of them experience these issues. Usually if I disable/re-enable it in device manager it will work (60%). Im working on a fix though...
                              -------------------------
                              carputer: in progress
                              Laptop install

                              Comment

                              Working...
                              X