Written on January 14th, 2010 by viliyana89one shout
When the client computer cannot contact the DHCP server for IP address configuration, Windows XP uses APIPA (Automatic Private IP Address) for IP configuration. This allows the client computer to communicate with other computers and printers on a single subnet. APIPA uses the private IP address range of 169.254.0.1 through 169.254.255.254 and a subnet mask of 255.255.0.0. 169.254.96.107 is thus an APIPA address that was assigned by Windows because the computer did not receive an IP configuration from a DHCP server. By running the Ipconfig /renew command we will force the computer to attempt to contact the DHCP server again so that it renew the client IP configuration.
Written on January 1st, 2010 by viliyana89no shouts
The network consists of a single Active Directory domain. The network includes Windows 2000 Advanced Server computers, and Windows 2000
Professional and Windows XP Professional client computers. Except for the domain controllers, all computers on the network use DHCP for their TCP/IP configuration. Users begin reporting that when they try to access resources on File Server, they receive the following error message: “Network path not found.”
The likely problem in this scenario is that when the file server was restarted, it received a new IP address. When a user connects to a server using a user-friendly name, DNS resolves the user-friendly name to an IP Address that is then used to connect to the server. This name-to-IP address resolution is then stored in cache on the user’s computer so that when they attempt to connect to the same server, they do not have to use DNS. The DNS cache on the users’ computers has the old IP address for the file server. Thus, when the client attempts to contact the file server it is using the wrong IP address that it has cached. The /flushdns switch of the Ipconfig command flushes the list of locally cached DNS names.