169.254.. IP Address

I know this message has been around a thousand times, however, I still can't get my laptop to work. I'm using a BEFW11S4v4 router and a WPC54G card. Both are linksys. I've reinstalled my TCP/IP settings and applied a winsock fix several times. The only problem that I can see when I do an ipconfig/all now is that my subnet mask is 255.255.0.0 on my laptop when the subnet mask for my working computer is 255.255.255.0. I have limited or no connectivity due to the ip and can't connect to the internet. Any suggestions? Need more info from me?

Is DHCP activated on the router, and is the wireless card set to acquire an IP address automatically?

Similar Messages

MacBook 169.254 IP address fix

I had an issue connecting to a College network using a MacBook. The Airport would recognize the Cisco Aironet, but I was only assigned a 169.254 IP address. To fix this I turned on Apple Talk.
I found the solution here:
http://forums.macosxhints.com/showthread.php?p=352019
===quote
I tried multiple solutions including "reserving" an ip address for a specific MAC address on the actual router (which is acting as the DHCP server). even this did not work.
Then I checked the "Make AppleTalk Active" and had the "Configure" option set to "Automatically". its the only thing that worked. Hope this helps.
===end quote
Hope this helps,
Mitch

I have the same problems with my Mac mini bought June 22. Until yesterday there is no any problems, today I found it couldn't connect Internet and the ip is 169.254.12.3, I updated DHCP, reboot, and set ip to 192.168.1.3, and so on, but all to get the same result.
At last, I tried cable to connect it, I found the ip is also 169.254.12.3, I have no way, can you help me, too?
By the way, there are 5 others device connecting to my LAN with cable or wireless, including iPad, all of them are no any problems.

Can't connect to internet, always get (169.254) ip address

Mac Mini with OS X 10.5.8
Internet connection worked for years up til now.
I know the Comcast modem is working because my other computer accesses service fine.
I only connect directly from the Comcast modem to a single computer at any one time (to prevent conflicts).
I have disconnected the battery from the Comcast modem and rebooted the modem and my computer.
I have called Comcast and had them troubleshoot the line and reset the modem. All looks fine from their end.
I have trashed all plist files that have to do with the network (and let the computer regenerate new ones). I then reconfigured the network and the settings in Network seem exactly the same.
Any ideas? Could a bad internal battery be enough to cause this? Should I zap PRAM? Any suggestions will be entertained. Thanks, Peter
(Also, in Proxies dialog, I tried removing the info (*,local, 169.254/16) in the "Bypass Proxy Settings for These Hosts and Domains" and it would cause the "Configure Proxies" selection to default to "Always Use PAC File". Had to go back and retrash all the plist files to have Proxies go back to "Configure Proxies-Manually".
Here are my settings:

In my G5 (OS X 4.11) the Network area for Proxies has "Configure Proxies" set to "Manually", same as Mac Mini (OS X 5.8); that's why I can't understand the ability of one to work and not the other. (I'm fairly clueless about all the jargon in the Network configuring process, so asking me about proxies, etc will garner few informed response.)
Yes, I did use the "Insert Image" command. Don't know why it would be messed up. I will try again here.
And I'll try powering down the Modem for a longer period. Thanks.

DHCP Address changes to 169.254.x.x after starting to download image in PE

Our network requires the user to register their computer on the network to obtain network access. This really isn't for security, but for tracking reasons. This registration is done via the web on a temporary private network they get sent to if the dhcp server doesn't recognize the machine. Once registered they can either reboot and renew their IP or just wait till the IP times out which is 2 minutes to gain access to the network with a real IP. The tempoary network runs 2 minute lease times because of the limited number of IPs and the large turnaround we have on this network during peak times. The real network runs 4 hour lease times mainly just because of the large turnaround of computers some buildings have been reduced to 1 hour because at 4 hours we would run out of IPs for the building. We have a class B subnet for real IPs that all clients get with IPv4 we have to play a delicate balancing act to keep from running out. We have in the process of implementing IPv6 which could solve some of these problems.
Back to my problem. When a bare metal computer comes in the tech needs to load the machine. At this point it is on the tempoary network. The tech boots the computer into pe either cd or pxe. Then they register the computer with configmgr and start up the correct task sequence. Even with the 2 minute lease time the client maintains constant connectivity no matter how long the user takes to register the client. You can wait days if you like. Once the task sequence is chosen and it starts to apply the image it will fail. If you push F8 and do an ipconfig it shows a 169.254.x.x ip address. If you try to renew the IP you get An error occurred while renewing interface Local Area Connection : The requested address is not valid in its context. You can release and renew and get a new IP, but at this point the task sequence has failed with error 0x80070035. This is a problem with all model computers even in vmware.
Has anyone experienced this problem? I've seen other post before and the solution was always to bump up the lease time which the network guys won't and probably can't do. It is like the IP will not auto renew while downloading an image. This happens whether you do download as needed by task sequence or access content directly. We are in native mode, but had the same problem in mixed.

We need to be able to image bare metal computers from anywhere on the network so using a dedicated vlan is difficult. The requirement for network registration during the setup process has been a problem for years, but with little resolution between the techs and the network guys.
We are using public ips for clients because many years ago the routing hardware couldn't handle the NAT translations for the large number of clients. The network guys don't have dynamic vlans configured although I think they are working on it right now they just piggyback subnets on interfaces. Also the separate vlan for loading computers would be partially difficults since this has to work any all buildings, but because of potential routing problems they don't put a vlan in more than one building. Each building right now has at least 1 dedicated vlan with a corresponding subnet and router. Most of our core is 10Gb with at least 2Gb-10Gb to each building so bandwith usually isn't a problem. The DHCP server is old, but handleing the work load just fine.
Our environment doesn't 100% match the typical corporation that runs configmgr. We have a primary central support area and then many sub support areas that all do their own thing with special image requirements. There is a need to keep these areas separate, but centralliy manages with minimal administrative overhead. So to handle this we use unknown computer support just to make booting with pxe into PE. I then use tsconfig.ini to call a modified version of the unknownsystem.hta from the configmgr sdk. The tech doing the imaging logs into this screen and selects an image collection (the available list is based on the users rights to the collections), ad ou, custom variable settings, and machine name to add the computer to the system and recieve the appropriate os advertisements without having to add the system manually through the configmgr console.
We are still working on ways to avoid the network registration step or register the computer on behalf of the client, but would still like to figure out this problem.
Thanks,
Sam

IP address 169.254....

Hello,
A few weeks ago, both my ethernet and my airport were working fine in my dormitory and anywhere I went. Then in my dormitory, the ethernet suddenly stopped working as I was using it. I didn't change any settings, I was not messing arround with anything. It just suddenly stopped! I tried asking for help to the people in the dormitory, but being in a place where no one (in the dormitories and IT technicians) really speaks my language and I don't really speak theirs, doesn't help very much. Plus the fact that they don't really seem to be able to use and fix mac problems. My ethernet cable connection works excllent with any other computer that is connected to it BUT with mine.
Anyways, everything is on automatic the way it should be, but it shows that the self assigned IP address is of 169.254. etc, and it cannot connect to the internet. It happens with both ethernet and airport. With the airport I used to connect perfectly, but now, a few places where I used to connect perfectly won't work anymore, and it shows this same IP address of 169.254.blah.blah. It has been driving me crazy not being able to connect to the internet propperly since it is the only way I can communicate with my family. Could anyone PLEASE help me? I am really desperate here T^T Thank You!!
Regards,
Omar.

Try removing all the RAM and putting in new RAM. We had a PowerMac G5 at work that couldn't connect to the Ethernet no matter what we did. I was convinced it was the motherboard/Ethernet connection failure. But after running a couple of hardware tests, it came up with bad RAM. Put in all new RAM, and lo and behold, we have Internet!!
This would explain why multiple computers can connect to an internet connection, but one computer doesn't.
I'm having this problem with my MacBook Pro right now, and will attempt to take out the RAM when I get home to see if it fixes it. I had it at work, and was in the middle of surfing on our Ethernet network, when it suddenly stopped. I just put new RAM in a few weeks ago, so one might have failed.

How do I get rid of second 169.254.x.x IPv4 address on Windows Server 2008 SP2 x86?

I'm sure this is an obvious one but can't figure it out.
I have a Winserver 2008 Sp2 (x86) DC with a static IP address allocated to its only NIC. It seems to have acquired a second 169.254.x.x address automatically which I can't get rid of and which intermittently causes DNS problems (and possibly other)
problems.
ipconfig results are shown below:
C:\Users\Administrator.STRATIS2>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : STRATIS-SVR02
   Primary Dns Suffix . . . . . . . : stratis2.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : stratis2.local
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network Connection
   Physical Address. . . . . . . . . : 00-0F-1F-67-B8-CE
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.11.128.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   IPv4 Address. . . . . . . . . . . : 169.254.140.227(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 10.11.128.99
   DNS Servers . . . . . . . . . . . : 10.11.128.1
                                       10.10.128.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 8:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : isatap.{D60B08E6-D119-4CB8-BD18-380B7ED48
771}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Any ideas as to how this might have happened and how I get rid of it (a simple re-boot doesn't do the job).

OK, I followed Syed's instructions. I noticed that under the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\ there were two AdaptorGUIDs, but only one of them had any parameters.
I created the IPAutoConfigurationEnabled parameter for both these AdaptorGUIDs with a value of 0 as instructed and re-booted.
Here are the registry entries for the two AdaptorGUIDs:
After re-booting I did another ipconfig /all, and the APIPA address is still there! Here's the ipconfig output:
C:\Users\Administrator.STRATIS2>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : STRATIS-SVR02
   Primary Dns Suffix . . . . . . . : stratis2.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : stratis2.local
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network Connection
   Physical Address. . . . . . . . . : 00-0F-1F-67-B8-CE
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.11.128.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   IPv4 Address. . . . . . . . . . . : 169.254.62.149(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 10.11.128.99
   DNS Servers . . . . . . . . . . . : 10.11.128.1
                                       10.10.128.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 8:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : isatap.{D60B08E6-D119-4CB8-BD18-380B7ED48
771}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
[it's a different APIPA address this time, but I guess it is randomly allocated].
Any further ideas for me?
Thanks
Nigel

ACS 4.2.0 AAA-server-IP-address changing to 169.254.x.x

Hello,
I have ACS 4.2.0.124.15 installed on a windows server 2008.
In the configuration menu : network config > AAA server , the AAA-server-IP-address change to 169.254.x.x each time I disconnect the ethernet interface of the server.
Allthough, the ip adresse in my network connection of the windows-Lan-connection is set to static.
Whe I reconnect the ethernet interface of the server, it stays in 169.154.x.x. And I need to reconfigure the real static adresse each time.
Do you knows this problem. Is it a way to avoid it ?
Michel Misonne

Hello,I have ACS 4.2.0.124.15 installed on a windows server 2008.In
the configuration menu : network config > AAA server , the
AAA-server-IP-address change to 169.254.x.x each time I disconnect the
ethernet interface of the server.Allthough, the ip adresse in my network connection of the windows-Lan-connection is set to static.Whe
I reconnect the ethernet interface of the server, it stays in
169.154.x.x. And I need to reconfigure the real static adresse each
time.Do you knows this problem. Is it a way to avoid it ?Michel Misonne
Hi Michel,
It was issue in ACS 1113 SE Appliance and clear solution for the above is mentioned in the below link
http://www.ciscosystems.com/en/US/products/sw/secursw/ps2086/products_tech_note09186a00808d9199.shtml#stat
HTH
Ganesh.H

IP address 169.254 or no IP Address

I have a Linksys WRK54G (model with one antenna). I have problem with IP address.
If I enter with DHCP on the adapter, it receives an IP address like 169.254, which is not accepted by the Linksys. If I enter with static IP address the connection is very instable, some times I have to disconnect the USB adapter and connect again, or even disconnect the power of the router, to get an access to Internet. That means the IP address on the adapter is either wrong or empty. The Firmware Version is 1.55.02, May 21 2004, and I believed that there is not update.
The Radio signal appears as excellent, no surprise because the distance between adapter and router is 5 meters and there is only one conventional wall.
I have tried all of the above:
- uninstall and install the router configuration
- enter with WEP with open authentication, and work also without WEP
- change the channel to 11, the beacon interval, RTS, etc.
I did not try to disable the APIPA.I believe the newtork shoud work properly with this as usually (Am I wrong?).
The problem affects not only desktop PCs with wifi adapter but also LapTop with integrated wifi.
I see that many users have the same problem with different Routers of Linksys.
I would appreciate any assistance anyone may offer. Thank you in advance for your time.

only your wirless computer with the adapter cannot get an ip address?or all of the wireless computers?
if your router has a working computer wired then it must connect wirelessly as well.is your wireless adapter linksys as well?
try to update the drivers for your adapter and try to check if other wireless computers also can't grab an ip from your router.. then if not there is really something wrong with the wireless settings of the router

Why Windows keep detecting ip address such as 169.254.201.217/16 Both on Windows 8 and Windows 8.1

Why Windows 8 and Windows 8.1 (Even Windows 7) detects ip network address 169.254.201.217/16 on my computer???
I keep getting that most of the time.

Hi
This is my host files.
# Copyright (c) 1993-2009 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
And this is my network files.
# Copyright (c) 1993-1999 Microsoft Corp.
# This file contains network name/network number mappings for
# local networks. Network numbers are recognized in dotted decimal form.
# Format:
# <network name> <network number> [aliases...] [#<comment>]
# For example:
# loopback 127
# campus 284.122.107
# london 284.122.108
loopback 127

Why does my WRT54g sometimes give me a 169.254 address???

I have a WRT54G with firmware v1.01.0, Sep. 14, 2006. I've got an Apple G5 attached to it through one of the hardwired ethernet ports, connecting via DHCP. Once in a while, I'll get an address like 169.254.236.186 and can't connect. I have another Mac attached through a linksys wireless to ethernet bridge, and that one gets this kind of address all the time, needing to "renew DHCP lease" every couple of hours, to get a normal 192.168 address back. Can someone tell me how to fix this? Why does it give out such weird addresses? Mike Levin

When the computer fails or face the problem to get the IP from router automatically, then it will assign 169.254.x.x IP. Check the DHCP setting on wireless router and ensure you assigned big enough DHCP IP range. Also you can take a look on this wireless router configuration help..

TS3798 How do I stop my ethernet connection assigning itself a 169.254. ... address?

How do I stop my ethernet connection assigning itself a 169.254. ... address? My iMac is connected to a wired network. The DCHP server is set to allocate the iMac the address 192.168.1.2 but the iMac seems to over-ride this and allocate a 169.254 address. How do I stop this please?

Shouldn't be a need to use manual.
First try renewing the DHCP lease. In Network preferences, ensure the location in the top drop-down is set to Automatic, then click on advanced -
Then click on 'renew DHCP lease'. It may help to turn of IPv6, too, as some routers can't handle it yet.

HT3466 Airport has self assigned IP address 169.254.153.51 and will not be able to connect to the Internet

Cannot connect to internet wirelessly because I get the message "AirPort has the self-assigned IP address 169.254.153.51 and will not be able to connect to the Internet."

I would recommend that you do the following as a minimum:
Power-down the modem, AirPort base station, and computer(s).
Disconnect the AirPort base station from the Internet broadband modem.
While all of the devices are powered-down, perform a "factory default" reset on the base station. This will get it back to its "out-of-the-box" configuration and make setting it up much easier, especially if you use the "Assist me" process within the AirPort Utility. (ref: Resetting an AirPort Base Station or Time Capsule)
After the base station resets, go ahead and power it back down.
Reconnect the AirPort base station to the Internet broadband modem. For the Extreme and Time Capsule, be sure to connect the cable to the base station's WAN (circle-of-dots) port.
Power-up the modem; wait at least 10-15 minutes to allow it adequate time to initialize.
Power-up the AirPort base station; wait at least 5-10 minutes. Note: The AirPort's status light may continue to flash amber after it has intialized. That is because, there may be some additional configuration items necessary, like setting up wireless security, before the overall setup is completed to get a green status.
Power-up your computer(s).
In this basic configuration, the AirPort base station will broadcast an unsecured wireless network with a Network Name (SSID) of Apple Network NNNNNN. Network clients, connected to the base station either by wire or wireless, should now be able to access the Internet through the ISP's modem. Once Internet connectivity has been verified, you can use the AirPort Utility to configure the base station for wireless security and any other desired options. Please post back your results.

My Airpot/Time capsule will not will not connect. It states " AirPort has the self addressed IP address 169.254.231.99 and will not connect to the internet??????l

Cant' get my AirPort to sync up with internet. I get the message "AirPort has the self addressed IP address 169.254.231.99 and will not connect to the internet. How do I fix? Thanks.

What broadband router do you have?
What model Time Capsule do you have?
If you changed the system over from another router.. have you rebooted the entire network.. particularly a cable modem.. did you power off for at least 20min..
Tell us some info and we can help.

IP address of 169.254.x.x = no internet connection

I've had a torrid time with TimeWarner most of the day to discover that my Airport Extreme has suddenly defaulted to an IP of 169.254.x.x address. In other words, I can't connect to the internet at all using wireless, since addresses of 169.254.~ are invalid IP addresses.
However, if I connect my laptop via ethernet, I can connect no problem. I've tried: flushing the DNS Cache using Terminal... no luck. The only thing that will get me on the net is to connect my laptop directly.
Not ideal, since I have two other iMacs in the house in other rooms.
Can anyone help me with a solution to this dilemma? Much appreciated... help!

Hey, thanks... that definitely helps. Pain in the ***, but it's good to know.
I eventually got my 2-year-old Extreme replaced with a brand new unit at a nice Apple Store on Long Island, who gave me just the new unit from the box and the power supply. However, although my network now works again, the utility keeps telling me I need the latest Airport Utility (version 5.5, I believe).
I only have version 5.4.2. Apple's download site doesn't show 5.5, or is this an error message?

HT1338 my airport is not working getting Wi-Fi has the self-assigned IP address 169.254.5.29 and will not be able to connect to the Internet

my wi fi wont work giving me this Wi-Fi has the self-assigned IP address 169.254.5.29 and will not be able to connect to the Internet whats up with the airport how do i fix it

See this discussion.
Wi-Fi has the self-assigned IP address
Troubleshooting suggestions.
Troubleshooting Wi-Fi issues in OS X
Wireless Connection Problems - Fix
Wireless Connection Problems - Fix (2)
Wireless Connection Problems - Fix (3)
Wireless Connection Problems - Fix (4)
Wireless Diagnostics - About

IPad Wi-Fi has the self-assigned IP address 169.254.210.251 and will not be able to connect to the Internet. How to fix?

Mini connects to internet via cable modem fine.
Want to have ipad connect also but mini Wi-Fi has the self-assigned IP address 169.254.210.251 and will not be able to connect to the Internet. How to fix?

Hello:
I am a long way from a wi-fi expert, but.....
You need, I think, either a router with wi-fi or an airport (express or extreme). The iPad needs to connect to to a network. In my case, I use an airport express and both my iMac and iPad 2 connect to the Internet through the airport device.
Barry

169.254.*.* IP Address

Similar Messages

Maybe you are looking for

169.254.. IP Address