intel(r) pro 100/ ve network connection - limited or no connectivity

Discussion in 'Windows - General discussion' started by santz, Jul 6, 2006.

  1. santz

    santz Member

    Joined:
    Jul 6, 2006
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    11
    I need some help from you guys..

    I've recently installed windows xp on my girlfriends computer, installed sp2 and now there are two computers down the bottom right with the tital intel(r) pro/100 ve network connection
    and they have the yellow sign meaning limited or no connectivity.

    her internet runs through broadband and since the lan is there it is running very very slowly if at all. i've tried closing the lan connection and then she can't connect to the internet at all through her broadband

    can anyone help us out? how to fix the problem
     
  2. dolphin2

    dolphin2 Guest

    Go to Start > Run. Enter "cmd" (without the quotes) in the box and click OK. In the window that comes up, type "ipconfig /all" (again, without the quotes). Jot down what the results are and post back.
     
  3. lifelike

    lifelike Member

    Joined:
    Dec 21, 2005
    Messages:
    69
    Likes Received:
    0
    Trophy Points:
    16
    With the LAN connection enabled and if you are connected directly to your cable modem, and you pull a 169. IP address when you run ipconfig /all, try unscrewing the coax cable, and type ipconfig /release in the dos prompt. you should get an IP address of 0.0.0.0 then type ipconfig /renew and you should get an IP address beginning with 192. if this works, you should contact your ISP. If you release you IP address, and still have a 169, this is generally caused by a winsock error. to fix this in Windows XP Service Pack 2, in the DOS prompt, type "netsh int ip reset temp.txt" you will drop to a new prompt, this will reset your tcp/ip stacks. Then type "netsh winsock reset catalog" you will be told to reboot. do so, and once back to the desktop, go back to Start => Run => "cmd" => Ok and type in the prompt ipconfig /release ; ipconfig /renew This should give you a valid IP address.
     
  4. dolphin2

    dolphin2 Guest

    @lifelike
    Better to take things one step at a time, otherwise some people get information overload!
     
  5. lifelike

    lifelike Member

    Joined:
    Dec 21, 2005
    Messages:
    69
    Likes Received:
    0
    Trophy Points:
    16
    @dolphin2
    I appreciate constructive criticism, but wouldn't it be better saved until we knew whether or not this person got the "information overload"?
    However, I see what you are saying, the text does kind of run togeather.
     
  6. santz

    santz Member

    Joined:
    Jul 6, 2006
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    11
    alright i tried what you guys said..

    i went with the longer process that you put up..

    i tried the first half.. and everything was going as you had said it should..
    but when i got to the ipconfig/renew
    after a long pause a message came up saying unable to contact dhcp server - request timed out or something similar..

    so i then tried the second set of instructions
    and at the same place the same message came up


    i also forgot to mention in my first post that the pc in question isn't part of a network.. it's just a home pc by itself..
    not sure if that helps at all..
     
  7. lifelike

    lifelike Member

    Joined:
    Dec 21, 2005
    Messages:
    69
    Likes Received:
    0
    Trophy Points:
    16

    if you have a spare ethernet cord at home, you could try swapping ethernet cords. also, its possible (though a little unlikely) that the ethernet port on the modem went bad. More than likely, your NIC is bad.
    If you have a USB cable, run the USB from the modem to the PC. You may have to install the drivers for that particular model of modem, but that will likely get you online.
     
  8. Morph416

    Morph416 Active member

    Joined:
    Jan 14, 2004
    Messages:
    1,855
    Likes Received:
    0
    Trophy Points:
    66
    DHCP server is a setting that's activated in your router or modem.

    I'd suggest that you check your router's ISP settings and make sure they are correct. You'll have to login to the router via any internet browser. The IP to login will be your Gateway IP from the cmd you entered before to view all the IP addys.

    Or, a slimmed down version: start, run, cmd.. then ipconfig

    edit: some modems have online browser settings, some use telnet from the DOS window. Grab your manual for the modem...you'll need it. Also don't forget that you have the support from your ISP's department that'll help get you back online. They can connect to your modem from their end and find out exactly why you can't connect.

     
    Last edited: Jul 11, 2006
  9. lifelike

    lifelike Member

    Joined:
    Dec 21, 2005
    Messages:
    69
    Likes Received:
    0
    Trophy Points:
    16
    santz said that the PC in question isn't part of a network, router settings are a moot point.

    If he contacts his ISP, likely they will tell him that the problem is on his end. When an ISP telnets into a UBR to test connectivity, they see a PC's 169 IP address as being a modem in synch, but with no host connected. Generally, if they are nice, they will walk you through resetting your winsock, but will more than likely either refer you to Microsoft or tell you that your NIC is bad.
     
  10. ddp

    ddp Moderator Staff Member

    Joined:
    Oct 15, 2004
    Messages:
    39,167
    Likes Received:
    136
    Trophy Points:
    143
    disconnect power & coax/telephone line to cable modemfor about 10-15 seconds. reconnect power & line. at the msdos prompt do the ipconfig/release than the ipconfig/renew. try another net cable between modem & computer & maybe netcard if not using usb.
     
  11. Morph416

    Morph416 Active member

    Joined:
    Jan 14, 2004
    Messages:
    1,855
    Likes Received:
    0
    Trophy Points:
    66
    @lifelike:

    Confusing as it was, this part of the first post is what I read first:

    "since the lan"...though broadband is a 'lan' connection, I thought he was referring to the home network.

    Other than that, modems (with ddp's suggestion) suffer from even the slightest voltage glitches during power brown/blackouts. Brown outs may not even be detected thru any other household electronics unless it's severe enough to cause dimming lights. So, taking ddp's suggestion, you should try unplugging the modem for at least five minutes..then try again. Note: you won't get any IP addys from a DHCP server request to the modem if those settings have been altered in anyway. For that you may have to get into the modem's setting configuration menu.

    Would you know if her ISP uses a static, or dynamic IP address?

     

Share This Page