| Author |
Can not disable APIPA
|
|
| Bernie 2003-05-14, 8:47 pm |
| I'm running Win2000, the computer could connect to the internet and was working fine for a week. Now the Windows APIPA-automatic private ip addressing has kicked in and I can not get on to the internet anymore. I was already connected to a router/gateway with a DHCP Server and have another computer on this same gateway, it's working fine. I have put in a static ip address for this computer and it didn't work (mostly my fault for not config correctly) BUT even when I switch back from static to dynamic (with a DHCP Server attached), it still does not get a ip address within the DHCP range!!
I tried adding the registry DWord per MS Knowledge Base, reboot and the ip address is 0.0.0.0. I uninstalled/reinstalled tcp/ip, the adapter. I can't figure it out. Any suggestions would be great.
Bernie | |
| Bernie 2003-05-14, 8:49 pm |
| For those of you who are not familiar with APIPA. It's MS solution to small home networks. Kinda like a DHCP within itself . The address usually look like 169.254.x.x
This is driving me mad.
| |
| prezbedard 2003-05-14, 10:00 pm |
| I am familiar with APIPA.
Does the nic work with a static IP correctly configured? | |
| kackler 2003-05-14, 10:45 pm |
| If your getting 0.0.0.0 for an IP, then your getting an IP conflict, your DHCP server is trying to assign an IP that is already give. Here's a couple of commands to try. IPCONFIG /release and IPCONFIG /renew. Also make sure you have the IP for the DHCP server correct. Good Luck. | |
| kackler 2003-05-14, 10:48 pm |
| Oh yeah, if you have access top your DHCP server make sure the IP pool is big enough for the number of nodes on your network. | |
| ghaouf 2003-05-14, 10:50 pm |
| what is the difference between apipa and ics | |
| prezbedard 2003-05-14, 10:58 pm |
| quote:
Originally posted by ghaouf
what is the difference between apipa and ics
Apipa kicks for example if you have a nic in your computer and you boot up with no physical network connection. Provided of course the nic is set to get IP automatically. | |
| prezbedard 2003-05-14, 11:01 pm |
| quote:
Originally posted by kackler
If your getting 0.0.0.0 for an IP, then your getting an IP conflict, your DHCP server is trying to assign an IP that is already give. Here's a couple of commands to try. IPCONFIG /release and IPCONFIG /renew. Also make sure you have the IP for the DHCP server correct. Good Luck.
I had that problem before. Installed a new machine with DHCP enabled. The first day it worked fine. The next it acted up and was getting 0.0.0.0. Tried all those commands didn't work so I assigned it a static ip. | |
| Bernie 2003-05-15, 7:07 am |
| When I config a static ip, I can ping the gateway/router/switch/dhcp server (this is a d-link combo box), I can not connect to the router to administrate. I can not release/renew the ip address. It gives me an error. I would tell you exactly but I'm not at the computer now. It's something like you can not release an ip address because it is not assigned. This is when the address is 169.254.x.x
The DHCP ip pool range is 100 so there are plenty of available addresses. I've been booting with a DHCP Server attached yet it will not give me anything but 169.254.x.x | |
| kackler 2003-05-15, 8:06 am |
| Hmmm....well, make sure the DHCP scope is activated and the DHCP is authorized. Is your DHCP on the same subnet? If not it needs to be. | |
| kackler 2003-05-15, 8:08 am |
| Also try a loopback test to make sure your NIC is good. Ping localhost or Ping 127.0.0.1 | |
| Bernie 2003-05-15, 8:37 am |
| Thanks for all your help. This one is troubling me.
When I have the address 169.254.x.x, I can ping the nic. I have not tried when the address is 0.0.0.0. The DHCP is working fine for another computer. I even tried a different d-link router (same model though). On each d-link there is another computer connected and it does not have any problems. | |
| Bernie 2003-05-15, 8:58 am |
| When I do the following the ip address is 0.0.0.0
Q. How can I disable APIPA?
A. APIPA (Automatic Private IP Addressing) was discussed in 'Q. My Windows 2000 DHCP client has an IP address not in any scopes, how?' and is the mechanism in a small network that clients will automatically allocated themselves an IP address in the range of 169.254.x.x if no DHCP server can be contacted.
It may be desirable to disable this and to do this perform the following:
Start the registry editor (Regedit.exe)
Move to HKEY_LOCAL_MACHINE\SYSTEM\Curr
entControlSet\Services\Tcpip\P
arameters\Interfaces
Select the required interface
From the Edit menu select New - DWORD value
Enter a name of IPAutoconfigurationEnabled and press Enter
Double click the new value and set to 0. Click OK
Close the registry editor
If you have multiple adapters and wish to disable for all just create and set HKEY_LOCAL_MACHINE\SYSTEM\Curr
entControlSet\Services\Tcpip\P
arameters\IPAutoconfigurationE
nabled to 0. | |
|
|
| prezbedard 2003-05-15, 9:10 am |
| Have you tried upgrading the lastest drivers for the nic. I had a pc that for no reason was one day unable to connect to the network. I tried all the usual things first. Got an error when I used the diagnostic software so I updated the drivers and it worked. | |
| yerlanguy 2003-05-15, 9:38 am |
| Did you do an "ipconfig /release & renew" on the other computers to verify that DHCP is still operational? If so, did you try a diff't port and cable? | |
| Bernie 2003-05-15, 12:43 pm |
| quote:
Originally posted by yerlanguy
Did you do an "ipconfig /release & renew" on the other computers to verify that DHCP is still operational? If so, did you try a diff't port and cable?
I have plugged into a diff ports within two different routers (same model). I have not released the ip address of the other computers. I also will try a diff driver for the network card. Thanks for the tips. | |
| kackler 2003-05-15, 3:08 pm |
| Have you tried a different cable? | |
|
|
| Bernie 2003-05-19, 8:23 am |
| quote:
Originally posted by reggien66
if you guys have another alternative or solution i wanna hear about it!  
On that link I posted, it tells you of a reg fix (not sure if this was the same one you were talking about) that is suppose to work. I had to reinstall Windows to fix this issue. I guess something with tcp/ip or the nic drivers was corrupted.
Thanks for the help everybody.
Bernie | |
| kackler 2003-05-19, 5:06 pm |
| did you get it working? If you do post the fix for your problem. | |
| Bernie 2003-05-20, 7:10 am |
| On Sunday, I reloaded Win2000. All was working fine...WAS...
When I hooked the computer back up to the router/gateway. I was able to connect to the internet just fine. When I started to config network properties to see the other computer on the router, APIPA kicked in again on the new computer. I spent about 3+ hrs on the phone with D-Link's tech support and still could not get it fixed. | |
| ctrlaltdel 2003-05-20, 7:53 am |
| Bernie, Have you checked the connections ?
How about putting another machine that is working at that spot and see if it connects.
That way you could rule out the wiring.
Next try upgrading the nic drivers, and assigning a DNS address to the nic and see what happens. Let us know how you make out. | |
|
|
| Bernie 2003-05-22, 10:35 am |
| I did have another computer running Win98 on this router and it worked just fine. I could ping the loopback address. I was talking to someone else who uses Intel mthbrd with the built in LAN, he said he and a friend had the same problem. I updated the onboard LAN drivers and ran a BIOS update. Still did not work. I'm tired of working on it. I installed a pci network card and called it quits. So far it's been working fine.
Thanks everybody, for all your help.
Bernie |
|
|
|
