xcanuc wrote: I have a question about APIPA. I am studying with the Microsoft Academic Course books and in 270 they say that if you have an APIPA address APIPA looks for a DHCP server every 5 minutes until it receives a DHCP address and then when it does it is fine. In 293 they say that if you have an APIPA address you must restart to get a DHCP address. I looked at Microsoft's web site and they say that you need to restart to get a DHCP assigned address also. Does anyone have a difinitive answer on it? Thanks in advance.
Danman32 wrote: You mean 169.254.*.*, don't you?
PCHoldmann wrote: I know I have hade some problems with computers getting APIPA addresses, causing a bunch of firewall block logs, and correcting itself almost immediately, so I would say it keeps checking for addresses. IPCONFIG /Renew would force it to check immediately.
zeus_r wrote: Hi, I am planing to prepare for MCP, which book should i follow.
_omni_ wrote: zeus_r wrote: Hi, I am planing to prepare for MCP, which book should i follow. Probably a book relevant to the exam.
zeus_r wrote: Thanx for the information sir, could u please tell me which book should i follow for 70-270 _omni_ wrote: zeus_r wrote: Hi, I am planing to prepare for MCP, which book should i follow. Probably a book relevant to the exam.
zeus_r wrote: Hi, APIPA stands for Automatic Private IP Addressing, and a windows xp computer gets a APIPA, if there is some problem while trying to get an address from the DHCP, generally u will get an ip address of the form 16.254.*.*, and yes it is true that the APIPA service will look for a valid ip address from the DHCP server after every 5 mins, and it stops automatically when it gets a valid ip address. Generally to get a valid ip u will have to release the IP address of the computer by using the Command ipconfig /release and then try to obtain a fresh ip using ipconfig /renew. When you try to renew the ip address, if the connection to the DHCP server if fine, u should get a valid ip address, else u will get an error message like "Unable to connect to a DHCP server" or something related to non connectivity. To reslove this problem u will have to check for the root cause, if there is a problem with the connection then rectify it, if it seems to working fine then resetting the WINSOCK, should help. In windows xp sp2 a simple command "netsh winsock reset", should work. In case of sp1 and earlier, u will have to delete the winsock folders from the registry and then reinstall TCP/IP client on the machine. Bye xcanuc wrote: I have a question about APIPA. I am studying with the Microsoft Academic Course books and in 270 they say that if you have an APIPA address APIPA looks for a DHCP server every 5 minutes until it receives a DHCP address and then when it does it is fine. In 293 they say that if you have an APIPA address you must restart to get a DHCP address. I looked at Microsoft's web site and they say that you need to restart to get a DHCP assigned address also. Does anyone have a difinitive answer on it? Thanks in advance.
voxic wrote: zeus_r wrote: Hi, APIPA stands for Automatic Private IP Addressing, and a windows xp computer gets a APIPA, if there is some problem while trying to get an address from the DHCP, generally u will get an ip address of the form 16.254.*.*, and yes it is true that the APIPA service will look for a valid ip address from the DHCP server after every 5 mins, and it stops automatically when it gets a valid ip address. Generally to get a valid ip u will have to release the IP address of the computer by using the Command ipconfig /release and then try to obtain a fresh ip using ipconfig /renew. When you try to renew the ip address, if the connection to the DHCP server if fine, u should get a valid ip address, else u will get an error message like "Unable to connect to a DHCP server" or something related to non connectivity. To reslove this problem u will have to check for the root cause, if there is a problem with the connection then rectify it, if it seems to working fine then resetting the WINSOCK, should help. In windows xp sp2 a simple command "netsh winsock reset", should work. In case of sp1 and earlier, u will have to delete the winsock folders from the registry and then reinstall TCP/IP client on the machine. Bye xcanuc wrote: I have a question about APIPA. I am studying with the Microsoft Academic Course books and in 270 they say that if you have an APIPA address APIPA looks for a DHCP server every 5 minutes until it receives a DHCP address and then when it does it is fine. In 293 they say that if you have an APIPA address you must restart to get a DHCP address. I looked at Microsoft's web site and they say that you need to restart to get a DHCP assigned address also. Does anyone have a difinitive answer on it? Thanks in advance. IPCONFIG /release will do nothing with APIPA. Instead it will say "this adapter has already been released" Just do a normal IPCONFIG/RENEW, you don't need the added first step. APIPA in XP is a biatch...at least pre SP2 it was. When I worked for a large ISP the APIPA would often not successfully acquire an address on an ipconfig/renew even when everything was kosher with the DHCP source. Often I would find that rebooting was the only thing that worked. I'm pretty sure it was a glitch with it in XP. I do not know if it still like this in XP SP2. I haven't seen problems with it for a long time. Also, you can't "uninstall" tcp/ip in XP. You have to reinstall tcp/ip onto itself when fixing a WINSOCK issue the old way. I'm not nitpicking, the only reason I brought this up is because I could imagine someone reading the post and then coming back complaining that the "uninstall" tcp/ip button was grayed out. It's supposed to be.
