Results 1 to 11 of 11

Thread: Automatic Private Address

  1. #1
    Regular Member polishmafia4u's Avatar
    Join Date
    Aug 2002
    Location
    CA
    Posts
    353

    Automatic Private Address

    ok i used cable nut and something screwed up. i dont know what happened buy now when i try to connect to the net it wont find the page. the reason is cause i am using an Automatic Private Address. this used to never happen before today and ive used cable nuts tons of times. the only way i can get online is if i click repair in my network connections window or i wait 5 mins so the network tries to find the server again. i have 2 backups of the registry and tried to restore both to no avail. nothing works. any suggestions on what to do? ive found that i can add a reg key to fix this but the thing is, it used to work fine until today without the reg key. any suggestion?
    Comp 1: 1.4 Ghz P4, 128 MB RDRAM, Rage ATI 16 mB video card, XP Pro, Cox HSI 3000/256
    Comp 2: 466Mhz Intel Celeron, 256 RAM, TDK 48x12x48 CD-RW, Win 98 SE, Cox HSI 3000/256

  2. #2
    SG Enthusiast Brandon_k_W's Avatar
    Join Date
    Apr 2002
    Location
    Sacramento, California
    Posts
    1,580
    Microsoft added Automatic Private IP Addressing (APIPA) to Windows XP to let machines on the same subnet communicate with one another when no DHCP server is available (e.g., when the server crashes). If the DHCP server isn't available to issue an address or renew a lease, APIPA assigns a random IP address from the range 169.254.0.1 through 169.254.255.254 to the host. Although this feature can be useful, it can also prevent systems administrators from detecting problems in a timely manner.

    To disable APIPA, you can edit the registry to change the IP address to 0.0.0.0 when no DHCP server is available. Start a registry editor and go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces subkey. Select the string that identifies your adapter, and create a new DWORD Value. Name the entry IPAutoconfigurationEnabled, and set the value to 0. If you have multiple adapters, repeat the process for each adapter under the Interfaces subkey.
    © Copyright 2005, Brandon_k_W Inc. ® ™

  3. #3
    Regular Member polishmafia4u's Avatar
    Join Date
    Aug 2002
    Location
    CA
    Posts
    353
    yeah but the DHCP server IS available cause every time i click repair or wait 5 min as microsoft say, the network connection thing checks and it find the right address and i can surf, so this wont help cause having an ip of 0.0.0.0 still wont help my problem cause ill have to still click repair everytime if i wanna sure the net.
    Comp 1: 1.4 Ghz P4, 128 MB RDRAM, Rage ATI 16 mB video card, XP Pro, Cox HSI 3000/256
    Comp 2: 466Mhz Intel Celeron, 256 RAM, TDK 48x12x48 CD-RW, Win 98 SE, Cox HSI 3000/256

  4. #4
    SG Enthusiast Brandon_k_W's Avatar
    Join Date
    Apr 2002
    Location
    Sacramento, California
    Posts
    1,580
    Have you tried entering the IP address manually ?? Maybe that will work ???
    © Copyright 2005, Brandon_k_W Inc. ® ™

  5. #5
    Regular Member polishmafia4u's Avatar
    Join Date
    Aug 2002
    Location
    CA
    Posts
    353
    there is a lot of stuff in there. what do i enter for preffered dns server and the other stuff?
    Comp 1: 1.4 Ghz P4, 128 MB RDRAM, Rage ATI 16 mB video card, XP Pro, Cox HSI 3000/256
    Comp 2: 466Mhz Intel Celeron, 256 RAM, TDK 48x12x48 CD-RW, Win 98 SE, Cox HSI 3000/256

  6. #6
    SG Enthusiast Brandon_k_W's Avatar
    Join Date
    Apr 2002
    Location
    Sacramento, California
    Posts
    1,580
    Click on the Local Area Connection, then click on the Support Tab, then click on Details, it will give all the info there, including the Subnet Mask, Default Gateway, etc.
    © Copyright 2005, Brandon_k_W Inc. ® ™

  7. #7
    Regular Member polishmafia4u's Avatar
    Join Date
    Aug 2002
    Location
    CA
    Posts
    353
    i have all the info but for WINS server there are no numbers listed.
    Comp 1: 1.4 Ghz P4, 128 MB RDRAM, Rage ATI 16 mB video card, XP Pro, Cox HSI 3000/256
    Comp 2: 466Mhz Intel Celeron, 256 RAM, TDK 48x12x48 CD-RW, Win 98 SE, Cox HSI 3000/256

  8. #8
    SG Enthusiast Brandon_k_W's Avatar
    Join Date
    Apr 2002
    Location
    Sacramento, California
    Posts
    1,580
    i do not have WINS IPs either. i just enter the information that is shown in the TCP/IP Properties Window (pic below)

    © Copyright 2005, Brandon_k_W Inc. ® ™

  9. #9
    Regular Member polishmafia4u's Avatar
    Join Date
    Aug 2002
    Location
    CA
    Posts
    353
    thanks dude it works. im still trying to figure out why this happened though. all i did was apply the cablenut settings and then everything got screwed. dont know why.even restoring the registry didnt help. any ideas? also, since it is DHCP and cox does change the ip every so often, when they change it, what do i need to do, cause im guessing that ill know when they change it cause i wont be able to connect to the net. do i jsut click repair in the network connections box so that the comp gets the new ip info and then just replace the old info with the new? or will i always be able to connect using this ip? thanks a ton
    Comp 1: 1.4 Ghz P4, 128 MB RDRAM, Rage ATI 16 mB video card, XP Pro, Cox HSI 3000/256
    Comp 2: 466Mhz Intel Celeron, 256 RAM, TDK 48x12x48 CD-RW, Win 98 SE, Cox HSI 3000/256

  10. #10
    SG Enthusiast Brandon_k_W's Avatar
    Join Date
    Apr 2002
    Location
    Sacramento, California
    Posts
    1,580
    I'm sure that it is a small problem and can easily be fixed. Just use google and in the search bar, type something like "Disabling automatic private IP addressing"

    and it's strange that restoring your registry didn't do any good, since cablenut's tweaks only affect the registry. Just another Microsoft problem that can be added to the infinite laundry list of problems it already has.
    © Copyright 2005, Brandon_k_W Inc. ® ™

  11. #11
    Regular Member polishmafia4u's Avatar
    Join Date
    Aug 2002
    Location
    CA
    Posts
    353
    yeah seriously i was like, no big deal, ill just restore my registry and...WTF. so i said ok not a prob, i got another backup and...WTF again. and so i said, ok last hope, i even tried system restore and...nothing. i was hella surprised. it was weird tho cause i never had a prob with cable nut before. i used it tons of times, then all of a sudden i tried Lobo's numbers(not trying to blame you) and BLAM i get screwed lol. well, off to google to do a little seraching.
    Comp 1: 1.4 Ghz P4, 128 MB RDRAM, Rage ATI 16 mB video card, XP Pro, Cox HSI 3000/256
    Comp 2: 466Mhz Intel Celeron, 256 RAM, TDK 48x12x48 CD-RW, Win 98 SE, Cox HSI 3000/256

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
  •