Autoconfiguration IP changed

[aixelsyd]

I am not sure this is where this goes so if it is not mods feel free to move(Like you wouldn't anyway )
I have a rather odd problem that started a couple of weeks ago, I can no longer access my ADSL router/modem through 192.168.1.1
I am almost 100% sure it is not the router itself that is causing the problem.
Here is what IPConfig shows

Windows IP Configuration


Ethernet adapter Local Area Connection 3:

        Connection-specific DNS Suffix  . :
        Autoconfiguration IP Address. . . : 169.254.146.241
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        IP Address. . . . . . . . . . . . : fe80::211:9ff:fe03:8298%4
        Default Gateway . . . . . . . . . :

PPP adapter:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : MYIP
        Subnet Mask . . . . . . . . . . . : 
        Default Gateway . . . . . . . . . : MYIP

Tunnel adapter Teredo Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
        Default Gateway . . . . . . . . . :

Instead of detecting the default 192.168.1.1 it detects the invalid 169.254.146.241 and it also has designated my LAN device as device 3.
The tunnel adapter has something or another to do with a Windows update and I am fairly sure it is not the cause of the problem. Before about two weeks ago there was no indication of this problem and the problems seems to have just started randomly, but I should note that prior to the problem I did have an expansion NIC in a PCI slot whereas now I am using my integrated adapter and removed the NIC a few weeks before the problem occurred.
Initially when the problem started Windows could not connect to the internet at all by itself so I had to setup a "Dial-ip" PPOE connection that you see in the IPConfig and enter my ISP's given Name and Pass. Although the connection now does run at full speed I need to be able to connect to the router to change the modulation type or this router likes to frequently and randomly drop my connection completely and reconnect.
I may be completely wrong here, but me it seems that my comp(It doesn't seem to be my OS) is detecting my integrated ethernet adapter to be the NIC I removed some time ago(Phantom Limb ).
I'm pretty sure I am just being a complete moron and have done something to cause this without realizing it.
Thanks in advance for any help.

Also an IP Whois reveals this about "169.254.146.241"

OrgName:    Internet Assigned Numbers Authority 
OrgID:      IANA
Address:    4676 Admiralty Way, Suite 330
City:       Marina del Rey
StateProv:  CA
PostalCode: 90292-6695
Country:    US

NetRange:   169.254.0.0 - 169.254.255.255 
CIDR:       169.254.0.0/16 
NetName:    LINKLOCAL
NetHandle:  NET-169-254-0-0-1
Parent:     NET-169-0-0-0-0
NetType:    IANA Special Use
NameServer: BLACKHOLE-1.IANA.ORG
NameServer: BLACKHOLE-2.IANA.ORG
Comment:    Please see RFC 3330 for additional information.
RegDate:    1998-01-27
Updated:    2002-10-14

OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName:   Internet Corporation for Assigned Names and Number 
OrgAbusePhone:  +1-310-301-5820
OrgAbuseEmail:  abuse@iana.org

OrgTechHandle: IANA-IP-ARIN
OrgTechName:   Internet Corporation for Assigned Names and Number 
OrgTechPhone:  +1-310-301-5820
OrgTechEmail:  abuse@iana.org

# ARIN WHOIS database, last updated 2007-10-29 19:10
# Enter ? for additional hints on searching ARIN's WHOIS database.

I don't have much of a clue as to how that is connected to any of this, but thought I would throw that in.

[johnwill]

TCP/IP stack repair options for use with Windows XP with SP2.

Start, Run, CMD to open a command prompt:

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log

Reboot the machine.



I'd also like to see ALL of the IPCONFIG /ALL output.

[aixelsyd]

Thanks for the reply.
I saw that you suggested that in another post and tried and tried it again, this time after I got my machine to start detecting 192.168.1.1 again, but the router was still unreachable and I believe it was because I had changed the autoconfiguration manually considering I was getting ping latencies of <1ms for 192.168.1.1

Windows IP Configuration

        Host Name . . . . . . . . . . . . : TIM
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethe
rnet NIC
        Physical Address. . . . . . . . . : MYMAC
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        Autoconfiguration IP Address. . . : 169.254.146.241
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . . . . :

PPP adapter My connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
        Physical Address. . . . . . . . . : MYMAC
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : MYIP
        Subnet Mask . . . . . . . . . . . : 
        Default Gateway . . . . . . . . . : MYIP
        DNS Servers . . . . . . . . . . . : MYPRIMDNS
                                            MYALTDNS
        NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4
        Default Gateway . . . . . . . . . :
        NetBIOS over Tcpip. . . . . . . . : Disabled

[johnwill]

You were able to ping the router? What changed, because you sure can't ping it with that configuration!

[aixelsyd]

I don't believe I was actually pinging the router, but just by simply changing the autoconfiguration options for "LAN 3" to the default 192.168.1.1 setting it did seem to just give me a false positive(From my viewpoint anyway) since I was not able to access the router. I should also note that I was in the process of reinstalling Ubuntu Linux (I had recently removed Linux for other reasons) and the autodetect for my network settings did not go through, I actually stopped the installation there and sought help here.

[johnwill]

The fact that you have issues with two totally different operating systems tends to make be believe you may have hardware issues. Time to look a lot closer at the cable, the port on the router/switch, and the NIC in the machine.