Can't get a real IP address from any wireless router

[HoMeZ]

I can't seem to connect to any wireless routers. I am currently on campus and I've tried to connect to many wireless routers, but I always get a 169.x.x.x ip address with subnet mask of 255.255.0.0 Does anyone know how to fix this?

 

[JackMDS]

The Wireless on campus might require specifc site settings, and may be password you should talk to th IT guys there.

:sun:

 

[HoMeZ]

I get this problem with any wireless router. I tried to connect to my friend's wireless router that he set up in his room and I get the 169.x.x.x address.

 

[KarenMarie]

169.254.xxx.xxx is the windows default IP whenever there is a problem with your network setup.

It could be one of many things....

What OS are you using?

 

[JeffMD]

isnt 169 a valid lan ip? I used to run 169 back on my 10mbit networks, thought it seems all of todays consumer routers are using 192. but maybe if its using old hardware, could the school net be using 169?

 

[JackMDS]

Originally posted by: JeffMD
isnt 169 a valid lan ip? I used to run 169 back on my 10mbit networks, thought it seems all of todays consumer routers are using 192. but maybe if its using old hardware, could the school net be using 169?

169.254.x.x is the default IP that Windows assigns when the IP is set to Auto Obtain and there is No DHCP server to obtain it from. :thumbsdown:

Basically it means that the specific Computer talks to itself (in other none Computer circumstances it might be one of the symptoms of Psychotic breakdown:shocked:😉 ).

:sun:

 

[HoMeZ]

I am using Windows XP.

 

[HoMeZ]

Originally posted by: JackMDS

Originally posted by: JeffMD
isnt 169 a valid lan ip? I used to run 169 back on my 10mbit networks, thought it seems all of todays consumer routers are using 192. but maybe if its using old hardware, could the school net be using 169?

169.254.x.x is the default IP that Windows assigns when the IP is set to Auto Obtain and there is No DHCP server to obtain it from. :thumbsdown:

Basically it means that the specific Computer talks to itself (in other none Computer circumstances it might be one of the symptoms of Psychotic breakdown:shocked:😉 ).

:sun:

Yea I think you are right. My laptop just hates me. I let my cousin try to fix it and when he turned it on it just worked, but then when I shut it down and tried it again later on it didn't work anymore. And now it still doesn't work.

 

[JeffMD]

jack, windows would not randomly assign an ip to talk to itself, thats what 127 is for. 169 is a valid local network ip, it assigns it as a last ditch attempt as a valid ip, since the only other choice would be no ip at all (127 also has nothing to do with the network card, you will allways have 127 without a network device). I was mearly asking if by chance, his schools network actually did use 169.

 

[JackMDS]

It meant as a Metaphor.😉 "If it can not obtain an IP (from a network) it talks to itself".:shocked:

:sun:

 

[HoMeZ]

so is there no fix?

 

[Kelemvor]

Try creating a new profile in your wireless config client. Just give it a name like "Default" and don't put in any other settings at all. Then activate that profile and see what happens. That *should* make it jsut find any available Public wireless network and connect to it. Also make sure in your Network Properties that your TCP/IP is set to Automatic IP.

 

[y0giboy]

>jack, windows would not randomly assign an ip to talk to itself, thats what 127 is for. 169 is a valid local >network ip, it assigns it as a last ditch attempt as a valid ip, since the only other choice would be no ip at >all (127 also has nothing to do with the network card, you will allways have 127 without a network >device). I was mearly asking if by chance, his schools network actually did use 169.

JeffMD,

A 169.x.x.x ip address is not a routable ip address. It is specifically called an 'Automatic Private Address', as stated before, it is issued by Windows whenever the adapter is set to use DHCP and it is unable to communicate with a DHCP server. Once again, routers/DHCP servers DO NOT issue 169.x.x.x addresses. What is the point? Windows issues this address so the computer still has the ability to communicate with other PCs on the same network or subnet that have been issued a 169. The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private internets (local networks):

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

He will recieve a private ip address from said router if the wireless NIC is able to communicate. Unless HoMeZ has set his wireless NIC to the 169.x.x.x statically, it is going to be a connectivity issue. Also make sure you are not looking at the IP for your 10/100 NIC in the pc. There may be a problem with one of the following, starting with the most likely:

A) His TCP/IP settings are incorrect or are set statically when they should be set to DHCP, or vice-versa.

B)There is a wireless signal issue., caused by faulty equipment or a poor signal due to obstruction or interferance.

C)TCP/IP is functioning however the wireless NIC itself is not functioning.

D)There is an issue with the wireless equipment on the other end, whether it is settings or hardware related.

E)There may be some software used for authentication, such as Oddessy. In some networks, no authentication may equate to no communication with the DHCP server. But, it really depends on their particular setup.

It is best to determine the the recommended settings and hardware that should be used when connecting to this wireless network. You may need to replace the adapter as well.

Hope this helps.

-Yogi

 

[HoMeZ]

I got it to work, but I have to turn off my wireless card reboot and then it will give me a good IP. If I leave my wireless on and reboot I'll get it the 169 ip.

 

[amdskip]

You just need to set it up so that it connects automatically, no need to reboot everytime.