my lan ip address changed by itself and no internet connection

Discussion in 'other security issues & news' started by wutsup, May 18, 2010.

Thread Status:
Not open for further replies.
  1. wutsup

    wutsup Registered Member

    Joined:
    Sep 20, 2009
    Posts:
    630
    Location:
    United States
    hey wilders,

    i had this problem today where my main copmuters ip address changed from my usual LAN ip of xxx.xxx.x.x to 169.254.242.22 which is totally out of my home network. i disabled and renabled through the network icon in tray icon area and it reverted back to my lan ip of xxx.xxx.x.x.

    i checked the routers log and this is what it says down the whole page:

    [INFO] Tue May 18 17:01:37 2010 DNS relay ALG rejected packet from 169.254.242.22:60783 to
    [INFO] Tue May 18 17:01:37 2010 Dropped packet from 169.254.242.22 to 68.105.28.12 (IP protocol 17) as unable to create new session
    [INFO] Tue May 18 17:01:33 2010 DNS relay ALG rejected packet from 169.254.242.22:60783 to
    [INFO] Tue May 18 17:01:33 2010 Dropped packet from 169.254.242.22 to 68.105.29.11 (IP protocol 17) as unable to create new session
    [INFO] Tue May 18 17:01:32 2010 DNS relay ALG rejected packet from 169.254.242.22:54357 to
    [INFO] Tue May 18 17:01:32 2010 Dropped packet from 169.254.242.22 to 68.105.28.12 (IP protocol 17) as unable to create new session
    [INFO] Tue May 18 17:01:29 2010 DNS relay ALG rejected packet from 169.254.242.22:60783 to
     
    Last edited: May 18, 2010
  2. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,956
    Location:
    Somethingshire
  3. LowWaterMark

    LowWaterMark Administrator

    Joined:
    Aug 10, 2002
    Posts:
    17,875
    Location:
    New England
    IP addresses in the 169.254.x.x range are what a Windows system will assign itself when it can not get a response from a DHCP server...

    http://en.wikipedia.org/wiki/Link-local_address

    http://ask-leo.com/why_cant_i_connect_with_a_169254xx_ip_address.html

    In short, your network connection went down for some reason. Your PC attempted to acquire or renew its IP address via a DHCP request. It got no response, so, Windows assigned the 169.254 IP address itself. Now, while that is a normal thing to do, it's actually fairly worthless because you can not connect out to the Internet using an address in that range.

    The 169.254 addresses have very few practical uses. The only one that has some value is if you plug two PCs into some sort of network hub that is not connected to anything else, Internet or other LAN, and let the PCs try to assign themselves IP addresses. They will both get addresses in the 169.254 range and should be able to connect to each other. No where else, but, they can connect to each other.

    Anyway, it was only a temporary error condition that obviously resolved itself. Once you reset the network connection, it got the necessary DHCP response and was assign a valid IP address.
     
  4. wutsup

    wutsup Registered Member

    Joined:
    Sep 20, 2009
    Posts:
    630
    Location:
    United States
    ohhhh ok, yea this happened before. but it was my ip address last time it happened and not 169.254.xxx.x

    so the ip address of 169.254 is just one from windows? ok cool, didnt know that.

    so its probably just a network error right? i was thinking maybe a hacker changed my ip address lol
     
  5. doktornotor

    doktornotor Registered Member

    Joined:
    Jul 19, 2008
    Posts:
    2,047
    See this tip for disabling APIPA. It's for 2000/XP/2003 but probably works on Vista/W7 as well. This APIPA stuff is highly annoying and I never got the thinking behind the "usefulness" of such idea. It's not like it'd produce a working network for anyone. :rolleyes:
     
Loading...
Thread Status:
Not open for further replies.