1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved Cannot connect to the internet

Discussion in 'Networking (Hardware & Software)' started by ldeoprecor, 2009/12/24.

  1. 2009/12/24
    ldeoprecor

    ldeoprecor Inactive Thread Starter

    Joined:
    2009/02/12
    Messages:
    18
    Likes Received:
    0
    Hey everyone,

    I'm running Vista Home Premium SP2 and I've been plagued by internet problems for the past few days. I have verified that my ISP connection is sound by testing the connection on two different computers.

    What I see is that the Local Area Connection is enabled, but there is no packet flow whatsoever and it says that IPv4 and IPv6 are both not connected.

    ipconfig /all gives me the following

    I can ping 127.0.0.1, but ipconfig /release gives me the following:

    I've tried a new NIC without any change and I'm positively stumped. Any thoughts or help are much appreciated.
     
  2. 2009/12/24
    sp3851

    sp3851 Well-Known Member

    Joined:
    2009/11/08
    Messages:
    280
    Likes Received:
    4
    Have you tried to disable then enable the Local Area Connection. Sometimes this is all it takes.
     

  3. to hide this advert.

  4. 2009/12/24
    ldeoprecor

    ldeoprecor Inactive Thread Starter

    Joined:
    2009/02/12
    Messages:
    18
    Likes Received:
    0
    That was probably the first thing that I tried. I only wish that something that simple would solve this.
     
  5. 2009/12/24
    sp3851

    sp3851 Well-Known Member

    Joined:
    2009/11/08
    Messages:
    280
    Likes Received:
    4
    Have you been running Vista and the problem just occured or Have you upgraded to Vista from XP ?
     
  6. 2009/12/24
    ldeoprecor

    ldeoprecor Inactive Thread Starter

    Joined:
    2009/02/12
    Messages:
    18
    Likes Received:
    0
    I've been running Vista. What is odd is that the internet was previously working. I had a wireless connection that suddenly couldn't detect any networks, so I tried using the ethernet connection. That also worked for one night and then refused to work the next day. I hadn't installed any new software so I don't know what would have caused this.
     
  7. 2009/12/24
    sp3851

    sp3851 Well-Known Member

    Joined:
    2009/11/08
    Messages:
    280
    Likes Received:
    4
    ldeoprecor:

    Please add your system specs and Nic card type and manufacture - 32 or 64 bit.
     
  8. 2009/12/24
    ldeoprecor

    ldeoprecor Inactive Thread Starter

    Joined:
    2009/02/12
    Messages:
    18
    Likes Received:
    0
  9. 2009/12/24
    sp3851

    sp3851 Well-Known Member

    Joined:
    2009/11/08
    Messages:
    280
    Likes Received:
    4
  10. 2009/12/24
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107
    ldeoprecor, please enter your System Details. It helps us in answering your questions!
     
  11. 2009/12/24
    ldeoprecor

    ldeoprecor Inactive Thread Starter

    Joined:
    2009/02/12
    Messages:
    18
    Likes Received:
    0
    I just ran a virus scan, and nothing came up. This is a newly reformatted computer, so I would hope that spyware etc wouldn't be an issue.

    I tried resetting Winsock using netsh in cmd and that didn't help. I'm not sure what the Winsock fix would do in addition to that. Also, the link provided points to XP fixes. Would an XP fix work for x64 Vista?
     
  12. 2009/12/25
    sp3851

    sp3851 Well-Known Member

    Joined:
    2009/11/08
    Messages:
    280
    Likes Received:
    4
  13. 2009/12/25
    ldeoprecor

    ldeoprecor Inactive Thread Starter

    Joined:
    2009/02/12
    Messages:
    18
    Likes Received:
    0
    I tried resetting winsock using netsh winsock reset but that doesn't seem to be the issue. I suppose that I could just reformat and hope for the best, but I would like to know what exactly caused this.
     
  14. 2009/12/27
    Scott Smith

    Scott Smith Inactive Alumni

    Joined:
    2002/01/12
    Messages:
    1,950
    Likes Received:
    4
    I had the same problem with a Win7 machine recently and I can't tell you how I fixed it (Because I don't know) but I can give you some clues that might help turn a light on for you or someone reading this.

    Right after you connect to a new network there is a screen that pops up to ask you if it's a Home Network, Work, or Public. It did not pop up and therefore my suspicion is with that service.

    Mine would say connected but local only on WiFi or Wired connection.
    At Ipconfig/ All the adapter would have a 169. address. If you forced a static address it still would not work plus the adapter properties would lock up (Not Responding) when you tried to make a change.

    Hope that helps.
     
  15. 2009/12/27
    improvepctools

    improvepctools Inactive

    Joined:
    2009/12/27
    Messages:
    3
    Likes Received:
    0
    Have you tried another router? Or maybe try to connect another computer to the netword to see if you have internet.
     
  16. 2009/12/27
    daney

    daney Inactive

    Joined:
    2008/05/13
    Messages:
    2
    Likes Received:
    0
    Can I suggest you disconnect everything, including the modem and take the lot to your technician and ask for a bench test. This will enable the technician to locate the problem. If he is a good techy, you will soon be up and running.
    Sometimes it is better to spend a few bucks and have the system running efficiently than to try self repair. It sounds as though there could be a combination of problems which need to be addressed.
     
  17. 2009/12/27
    ldeoprecor

    ldeoprecor Inactive Thread Starter

    Joined:
    2009/02/12
    Messages:
    18
    Likes Received:
    0
    I ended up simply reformatting and that "solved" the problem. I can only assume that the problem was being caused by the networking software not properly communicating with the NIC.

    I'm still not sure what could have caused it, especially since resetting winsock and reinstalling adapter drivers did nothing. I guess you could say that this was resolved.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.