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.

DHCP/APIPA Help Requested

Discussion in 'Networking (Hardware & Software)' started by Sloppyunderfoot, 2007/02/26.

  1. 2007/02/26
    Sloppyunderfoot

    Sloppyunderfoot Inactive Thread Starter

    Joined:
    2007/02/26
    Messages:
    6
    Likes Received:
    0
    I have spent hours over the past few days looking for solutions to resolving 169.x.x.x ips on computers that are directly connected to a cable modem without any router. The last time I faced this issue we ended up moving the NIC card to another PCI slot and we did succeed in getting a valid ip. I've used the following link http://kb.resnet.purdue.edu/viewarticle.php?articleid=1385&refid=4 many times however, it rarely helps. If anyone has a great link, can assist me in understanding more about 169 addresses, dhcp, apipa, or can shed some light on this issue in any way, I would be most appreciative. Thank you.
     
    Sloppyunderfoot,
    #1
  2. 2007/02/27
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    You may want to post some adittional information on your setup. How are those machines configured to get their IP address?
     
    Arie,
    #2


  3. to hide this advert.

  4. 2007/02/27
    mflynn

    mflynn Inactive

    Joined:
    2002/08/14
    Messages:
    4,141
    Likes Received:
    9
    No details!

    The 169.xx... series is Windows default IP range and will be used when windows has not been told explicidly what IP to use, or when DHCP is off or damaged or not installed.

    Can be used for some things, BUT! Usually means something ain't right!!

    Get me the following info and perhaps I can tell you.

    Download the below extract and place in Windows\system32 folder
    http://www.dynawell.com/reskit/microsoft/win2000/sclist.zip

    Then paste the following to the CMD prompt (like sc query but cleaner for pasting)

    %SystemRoot%\system32\cmd.exe /c %windir%\system32\sclist.exe > "%USERPROFILE% "\Desktop\Svclist.txt
    hit enter

    There will apear on your desktop a file Svclist.txt

    %SystemRoot%\system32\cmd.exe /c %windir%\system32\tasklist.exe /svc > "%USERPROFILE% "\Desktop\Tasklist.txt
    hit enter

    There will apear on your desktop a file Tasklist.txt

    Then paste the following to the CMD prompt

    %SystemRoot%\system32\cmd.exe /c %windir%\system32\ipconfig.exe > "%USERPROFILE% "\Desktop\Ipcfg.txt

    There will apear on your desktop a file Ipcfg.txt

    Now paste all back to us. With the exception edit the ipcfg.txt and edit your "Internet/WAN" ip to read like 201.241.xx.xx etc so that we will not disclose it.

    Once we are through you can delete these .txt files ffrom the Desktop.

    Mike
     
    mflynn,
    #3
  5. 2007/02/27
    mflynn

    mflynn Inactive

    Joined:
    2002/08/14
    Messages:
    4,141
    Likes Received:
    9
    Sloppy

    Thought I would post plan 9. Because if I don't see your replies from above tonight I will not see them at all. As I will not be back after tonight.

    If the above info that you are to post back, does not help someone else here help you then do the below.

    In case the NIC driver and/or NIC registry settings are hopelessly scrambled up do the below.

    If this is an onboard NIC

    1. in Local Area connection remove all protcols clients and services empty the box.

    2. in device manager uninstall the NIC. Shut down immediately. Do not let windows come back up before step 3 below.

    3.Power on enter the BIOS a turn onboard NIC/LAN off.

    4. Back in windows run a registry cleaner to clean up while windows has no NIC installed.

    5. Reboot once more.

    Then back to BIOS and reenable the NIC.

    Windows should reinstall the NIC fresh on the way back up.

    If it is a PCI NIC then do all the above except where you shutdown to do the BIOS you remove the case and the NIC. Boot up with no NIC clean registry. Reboot once more before shutting down to reinstall the NIC.

    Good luck,
    Mike
     
    mflynn,
    #4
  6. 2007/02/28
    bbbobins

    bbbobins Banned

    Joined:
    2007/02/01
    Messages:
    129
    Likes Received:
    0
    Greeting Mr Mflyn

    Thank you thank you thank you

    I paste what you say to cmd and for now I know what is taskmgr each svchost is doing. I tried before could not find it.

    Great news for me I make shortcut and paste to it. IT WORKS

    I hope you will return I have gained knowledge from you.

    I use how to remove norton with remarkable results. My friends too used it and are happy.

    Are you go to another site? I would like to know where.

    BOB
     
    bbbobins,
    #5
  7. 2007/03/01
    Sloppyunderfoot

    Sloppyunderfoot Inactive Thread Starter

    Joined:
    2007/02/26
    Messages:
    6
    Likes Received:
    0
    Dhcp/apipa

    My post was really a general request. Just wondering if there could be a "formula" put together of steps one could take for resolving 169.x.x.x addresses. I have found a few items to try but I find that they rarely solve the problem. I don't have direct access to customer's computers so this makes it even more difficult. I am basically assisting people to get online after troubleshooting cablemodem problems. 9 out of 10 times the problem isn't the modem but a DHCP/TCP/IP/APIPA kind of deal. Sometimes I find that NIC drivers are corrupted but not always. Just trying to learn what I can do to help some folks out. Thanks very much for all your comments.
     
    Sloppyunderfoot,
    #6
  8. 2007/03/01
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    You'll get an APIPA address when no DHCP server is available on the network. So most of the times this will be a DHCP or TCP/IP problem.
     
    Arie,
    #7
  9. 2007/03/02
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    This is a common problem when a cable modem is connected directly to a NIC, after t-shooting problems. The best way to handle is to power down the modem for at least 10 seconds so the capacitor clears. Power down the pc. Power up the modem and wait until it synches. Then boot the pc.

    If the pc is assigned a private address (169.x.x.x) then that means that networking is not loading fast enough or is being hampered by another application loading at boot such as antivirus, antispyware or other app w/ low level drivers that "hook" into networking. Or DHCP is not loading, or if using a static ip DHCP is loading and conflicting w/ it. Or cat5 cable is bad. Or lots of other causes, but usually always DHCP not loading before 3rd party backgrounding apps.

    To test if a 3rd party app (or other driver) gets in the way boot in safe mode w/ networking.
     
    TonyT,
    #8
  10. 2007/03/17
    Sloppyunderfoot

    Sloppyunderfoot Inactive Thread Starter

    Joined:
    2007/02/26
    Messages:
    6
    Likes Received:
    0
    Again, thanks to everyone for your assistance. TonyT - your response definitely requires more attention. 99% of the situations I deal with are with dynamic ip's. I'll try seeing what happens by booting into safe mode with networking so all those lovely 3rd party apps/drivers don't load and see what happens. At least the problem will be recognized (I hope) and then the user can deal with it in the fashion they chose. Thanks.
     
    Sloppyunderfoot,
    #9

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.
    Accept Learn More...