Unchangeable 169.254.x.x IP Address
Dear Sir or Madame:I think the LAN in System B is what is causing the connection problem between System A and System B. It is the onboard LAN in the PC Chips A13G+ V3.0A Micro ATX board. The operating system is Microsoft Windows XP Home Edition, Version 2002 with Service Pack 3, No. 76477-OEM-0015717-31545.When I try to configure this LAN's IP address automatically IP Address 169.254.197.182 and subnet mask 255.255.0.0 are always assigned. When I try to configure it manually I cannot find an IP address that will work. According to Microsoft Help literature an IP address of the form 169.254.x.x and a subnet mask of 255.255.0.0 are configured by an automatin private networking application of Windows XP Professional rather than by DHCP. The status box for the connection in System B under "Support" reads "Automatic Private Address" for Address Type whereas the status box for the corresponding connection in System A under "Support" reads "Assigned by DHCP" for Address Type.Is there any way to change the address type to one assigned by DHCP?Systems A and B and the modem are connected wired to an Asus W-520GU router. There are no wireless connections and the wireless radio is turned off. The IP diagnostic information for System A is:C:\Documents and Settings\Peter J. Dooling>ipconfig /allWindows IP ConfigurationHost Name . . . . . . . . . . . . : SYSTEM-APrimary Dns Suffix . . . . . . . :Node Type . . . . . . . . . . . . : MixedIP Routing Enabled. . . . . . . . : NoWINS Proxy Enabled. . . . . . . . : NoEthernet adapter Board-A Local Area Connection:Connection-specific DNS Suffix . :Description . . . . . . . . . . . : NVIDIA nForce Networking ControllerPhysical Address. . . . . . . . . : 00-1B-B9-CD-60-FEDhcp Enabled. . . . . . . . . . . : YesAutoconfiguration Enabled . . . . : YesIP Address. . . . . . . . . . . . : 192.168.1.2Subnet Mask . . . . . . . . . . . : 255.255.255.0Default Gateway . . . . . . . . . : 192.168.1.1DHCP Server . . . . . . . . . . . : 192.168.1.1DNS Servers . . . . . . . . . . . : 192.168.1.168.237.161.12Lease Obtained. . . . . . . . . . : Sunday, September 26, 2010 5:23:23 PMLease Expires . . . . . . . . . . : Monday, September 27, 2010 5:23:23 PMEthernet adapter Local Area Connection:Media State . . . . . . . . . . . : Media disconnectedDescription . . . . . . . . . . . : ADMtek ADM8511 USB To Fast EthernetConverterPhysical Address. . . . . . . . . : 00-50-5B-00-0A-4BTunnel adapter Teredo Tunneling Pseudo-Interface:Connection-specific DNS Suffix . :Description . . . . . . . . . . . : Teredo Tunneling Pseudo-InterfacePhysical Address. . . . . . . . . : 80-00-FB-F9-93-F1-3C-47Dhcp Enabled. . . . . . . . . . . : NoIP Address. . . . . . . . . . . . : 2001:0:4137:9e74:8000:fbf9:93f1:3c47IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4Default Gateway . . . . . . . . . : ::NetBIOS over Tcpip. . . . . . . . : DisabledTunnel adapter Automatic Tunneling Pseudo-Interface:Connection-specific DNS Suffix . :Description . . . . . . . . . . . : Automatic Tunneling Pseudo-InterfacePhysical Address. . . . . . . . . : C0-A8-01-02Dhcp Enabled. . . . . . . . . . . : NoIP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.2%2Default Gateway . . . . . . . . . :DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1fec0:0:0:ffff::2%1fec0:0:0:ffff::3%1NetBIOS over Tcpip. . . . . . . . : DisabledThe IP diagnostic information for System B is:C:\Documents and Settings\Peter J. Dooling>ipconfig /allWindows IP ConfigurationHost Name . . . . . . . . . . . . : SYSTEM-BPrimary Dns Suffix . . . . . . . :Node Type . . . . . . . . . . . . : MixedIP Routing Enabled. . . . . . . . : NoWINS Proxy Enabled. . . . . . . . : NoEthernet adapter Board-B Local Area Connection:Connection-specific DNS Suffix . :Description . . . . . . . . . . . : NVIDIA nForce Networking ControllerPhysical Address. . . . . . . . . : 00-1B-B9-CE-FA-33Dhcp Enabled. . . . . . . . . . . : YesAutoconfiguration Enabled . . . . : YesAutoconfiguration IP Address. . . : 169.254.197.182Subnet Mask . . . . . . . . . . . : 255.255.0.0Default Gateway . . . . . . . . . :DNS Servers . . . . . . . . . . . : 192.168.1.168.237.161.12Tunnel adapter Teredo Tunneling Pseudo-Interface:Connection-specific DNS Suffix . :Description . . . . . . . . . . . : Teredo Tunneling Pseudo-InterfacePhysical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FFDhcp Enabled. . . . . . . . . . . : NoIP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4Default Gateway . . . . . . . . . :NetBIOS over Tcpip. . . . . . . . : DisabledTunnel adapter Automatic Tunneling Pseudo-Interface:Connection-specific DNS Suffix . :Description . . . . . . . . . . . : Automatic Tunneling Pseudo-InterfacePhysical Address. . . . . . . . . : A9-FE-C5-B6Dhcp Enabled. . . . . . . . . . . : NoIP Address. . . . . . . . . . . . : fe80::5efe:169.254.197.182%2Default Gateway . . . . . . . . . :DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1fec0:0:0:ffff::2%1fec0:0:0:ffff::3%1NetBIOS over Tcpip. . . . . . . . : Disabled Regards Peter Dooling1 person needs an answerI do too
September 30th, 2010 10:18pm

Hi169.254.xxx.xxx is a default IP that Windows installs when it cannot connect to a DHCP server.Your computer A is configured correctly.Computer B has No Default Gateway (which in your case it should be the IP of the Router 192.168.1.1).No Default gateway means that the computer is not aware of the existence of the Router.Try to update the Network card Drivers.If it does not help, try a Static IP with computer BUse the followingIP Address. . . . . . . . . . . . : 192.168.1.100Subnet Mask . . . . . . . . . . . : 255.255.255.0Default Gateway . . . . . . . . . : 192.168.1.1DHCP Server . . . . . . . . . . . : 192.168.1.1DNS Servers . . . . . . . . . . . : 192.168.1.1It also possible that the onboard nVidia card is "quirky" and you will need a new PCI card. Jack-MVP Windows Networking. WWW.EZLAN.NET
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2010 11:04pm

Besides Jack's recommendations, I have one other suggestion ... Make sure that your DHCP Client service is running. To do this:Start -> Run -> "services.msc"Then look for a line that begins "DHCP Client". Make sure that its status is "Started" and the startup type is "Automatic". If not, double-click on it and set it that way.HTH, JW
October 2nd, 2010 2:23am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics