APIPA Issue
-
My user in the company is facing the APIPA issue that is the IP of the system is assigned to 169.x.x.x.
The system is Windows 7 64 Bit Enterprise Edition and the OS is update properly.
Whenever the user restarts the IP gets limited and then the system have APIPA IP.
I have done
the command in the command prompt"netsh ip reset all".
After this also the same thing happens.
So then the Network access point service is also restarted in administrator mode.
After that also the system assigns the APIPA IP.
When the system is provided with static IP no issue.
When the system is in DHCP,the APIPA issue occurs for this user.Why this happens? -
Check under "Services" on the machine, and make sure that the DHCP Client service is set to automatic, and make sure that it is started, as well.
-
This simply means that DHCP is failing. Maybe DHCP is full, maybe there is a router in between, hard to say. But bottom line DHCP is not working.
-
The internet works When I connect the static IP and then I switch the static IP to dynamic and after that there is no issue with the internet
When the system gets restarted the system has the internet which gets Limited access. -
On the client machine...
Click on Start -> Run, and then type in Services.mscThen look in the list for the one that says "DHCP Client"
It should look like that.
-
Ok I will look that also
-
@Lakshmana said:
The internet works When I connect the static IP and then I switch the static IP to dynamic and after that there is no issue with the internet
When the system gets restarted the system has the internet which gets Limited access.Any reason not to just keep the system static?
-
@scottalanmiller Yes Always the user needs to be connected in DHCP only not in static
-
@Lakshmana said:
@scottalanmiller Yes Always the user needs to be connected in DHCP only not in static
Why?
-
Laptop users will connect to Wifi also so the DHCP is preferred and the Desktop users have dedicated servers for DHCP and so the DHCP is assigned to Desktops
-
okay. Do users having the issue have the same issue from home or other location?
-
Do other machines have the issue when they try to hook up at the same location?