Local area connection doesn't have a valid ip configuration after using ubuntu

[dahamsta]

So in order to do a Uni task, I installed Ubuntu 14.04 on a USB (created a liveUSB) and booted with it this morning. I normally use Windows 7 and when I went back to Windows, I got the yellow triangle of doom and the troubleshooter informed me that this was the ip config issue. I know that this isn't an issue with the cable or the router, since attaching my laptop to the same cable worked. The weirdest and scariest part is the fact, that when I boot up the Ubuntu again on the same PC, the networking works there just fine. So any idea as to how I could make the Windows networking work again? Thanks for any help you may give.

I have surfed around the web for hours and done a couple of things:

netsh reset ips and winsock
ipconfig /release /renew - timed out when connecting to the DHCP server
turning off and unplugging PC for 30 mins or so (was taking a bath)
rolling back the realtek generic controller driver
Sadly I have no restore points so couldn't use those.
Uninstalling and reinstalling the network driver didn't work either.
Checked the services and everything seemed to be up and running.
Installing the reliable multicast on ipv4 in the adapter settings didn't work either.

ipconfig /all results:

Windows IP Configuration

Host Name . . . . . . . . . . . . : MyFineComputer
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 8C-89-A5-82-4D-C3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc75:1c4d:30d8:ba6b%19(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.186.107(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 193759653
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-7C-C4-49-8C-89-A5-82-4D-C3
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{C0C93553-C0F8-4FE9-923A-C30BDE23FA6F}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Reusable Microsoft 6To4 Adapter:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

 

[Saga Lout]

That 169 address is the problem.

In Control Panel>Network and Sharing Centre, click on Change adapter settings then right click the ethernet connection and go to Properties. Highlight the Internet Protocol Version 4 entry and click on Properties. Enter a valid 192.168.?.? based on the Default Gateway which is router's address. If that is 192.168.0.1 then allocate,for example, 192.168.0.40 to your PC and also enter the Default Gateway in the appropriate box.

Click Apply and OK your way out then restart the machine.

That should do it.

 

[dahamsta]

That 169 address is the problem.

In Control Panel>Network and Sharing Centre, click on Change adapter settings then right click the ethernet connection and go to Properties. Highlight the Internet Protocol Version 4 entry and click on Properties. Enter a valid 192.168.?.? based on the Default Gateway which is router's address. If that is 192.168.0.1 then allocate,for example, 192.168.0.40 to your PC and also enter the Default Gateway in the appropriate box.

Click Apply and OK your way out then restart the machine.

That should do it.

Thanks for the response, however, after changing the IP, subnet mask and default gateway as well as DNS servers to the exact same ones I use on my laptop (which I am currently using and hence definitely works). Whatever this insane problem is, it remained even after reinstalling windows (upgrading my old 7 to 8.1 while keeping personal files, if that matters) . I also noticed that packets are being received, but none are being sent. There is also a new error that states - The default gateway is not available. ipconfig /renew now says, that there is no adapter in the state permissible for this operation. I will also show the new revised ipconfig file:

Windows IP Configuration

Host Name . . . . . . . . . . . . : MyFineComputer
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 8C-89-A5-82-4D-C3
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::4d23:6d40:a82b:ff4f%3(Preferred)
IPv4 Address. . . . . . . . . . . : 91.105.124.245(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 91.105.124.1
DHCPv6 IAID . . . . . . . . . . . : 59541925
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-85-3F-19-8C-89-A5-82-4D-C3
DNS Servers . . . . . . . . . . . : 195.122.12.241
80.232.230.241
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{44B1DC92-29DB-41EA-83ED-911700AE0A50}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:5b69:7cf5::5b69:7cf5(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 134217728
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-85-3F-19-8C-89-A5-82-4D-C3
DNS Servers . . . . . . . . . . . : 195.122.12.241
80.232.230.241
NetBIOS over Tcpip. . . . . . . . : Disabled



EDIT: I will also add the ipconfig of my laptop (which works):


DNS Suffix Search List. . . . . . : apollo.lv

Wireless LAN adapter Local Area Connection* 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Karta Microsoft Hosted Network Virtual Adapter
Physical Address. . . . . . . . . : 00-71-CC-A0-FC-75
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1569:4f1f:90e3:647c%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.137.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 134246860
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-D4-04-C2-F0-76-1C-65-BA-CC
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Karta Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 02-71-CC-A0-FC-75
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Karta sieciowa Broadcom 802.11n
Physical Address. . . . . . . . . : 00-71-CC-A0-FC-75
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : apollo.lv
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : F0-76-1C-65-BA-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::447f:8197:6d6a:7223%3(Preferred)
IPv4 Address. . . . . . . . . . . : 91.105.124.245(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : Wednesday, March 23, 2016 2:52:21 PM
Lease Expires . . . . . . . . . . : Thursday, March 24, 2016 6:32:32 AM
Default Gateway . . . . . . . . . : 91.105.124.1
DHCP Server . . . . . . . . . . . : 91.105.124.1
DHCPv6 IAID . . . . . . . . . . . : 66090524
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-D4-04-C2-F0-76-1C-65-BA-CC
DNS Servers . . . . . . . . . . . : 195.122.12.241
80.232.230.241
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.apollo.lv:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : apollo.lv
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:442:2293:a496:830a(Preferred)
Link-local IPv6 Address . . . . . : fe80::442:2293:a496:830a%9(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 452984832
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-D4-04-C2-F0-76-1C-65-BA-CC
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6TO4 Adapter:

Connection-specific DNS Suffix . : apollo.lv
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:5b69:7cf5::5b69:7cf5(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::1
2002:c058:6301::c058:6301
DHCPv6 IAID . . . . . . . . . . . : 486539264
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-D4-04-C2-F0-76-1C-65-BA-CC
DNS Servers . . . . . . . . . . . : 195.122.12.241
80.232.230.241
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{AD31820A-0072-4DD5-B48B-9ED376CF0CD4}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

 

[dahamsta]

So I did manage to solve it by sort of expanding on the idea of copy pasting other configurations. If you have a similar situation with having Ubuntu booted from flash (like I did) or even dual booted and thereafter having lost the ability to connect to the modem (sorry guys I forgot it is a modem not a router :/), what you should do is open up the ubuntu and find out what ip configuration it generated. My guess is it overwrote windows DHCP server on either the modem side or somehow changed it in the networking card, which also changed the very gateway itself (since the IP and gateway I found on the Ubuntu side of things was WAY different from the one I copied from my laptop).

So here is what you do:
Open up the Ubuntu operating system:
1) Connect the USB to the PC if, like me, you are using a LiveUSB or just boot into it.
2) Check if the internet works here and, if it does, you are on the right track.
3) Open the terminal.
4) Write ifconfig -a | grep eth to find the ethernet connection's name that Ubuntu is using (it will probably be eth0, but whatever it is, use it in the next command).
5) Write ifconfig eth0 (instead of eth0 there might be another name you found with the previous command) to acquire the IP address that Ubuntu is using. In the example output taken from the documentation the IP address is inet addr or in this case 10.0.0.100 (this is not my configuration, it's just an example in the documentation). Also note the subnet mask (Mask). If it's the usual 255.255.255.0, then you can forget about it already, otherwise write it down.

eth0 Link encap:Ethernet HWaddr 00:15:c5:4a:16:5a
inet addr:10.0.0.100 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::215:c5ff:fe4a:165a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:466475604 errors:0 dropped:0 overruns:0 frame:0
TX packets:403172654 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2574778386 (2.5 GB) TX bytes:1618367329 (1.6 GB)
Interrupt:16
.
6) Whatever Inet addr you found, write it down.
7) Log on to Windows again.
8). Open the network and sharing center and next to your unidentified network click on the adapter. (connection attribute).
9) As Saga Lout previously advised, open the preferences tab, click on Internet Protocol Version 4 ... well protocol, and open properties (that are inside these properties).
10)In Internet Protocol v4 properties write the inet addr you previously found, in the subnet mask write 255.255.255.0 or something else if the subnet mask differed. In the default gateway write the same input as ip addr, but make the last number 1 (so if you have an ip addr 24.21.42.34, write 24.21.42.1). As for the DNS, I found it by attaching my Windows laptop to the cable (since those seem to remain the same), but otherwise you will have to look up how those are found (sorry :/). Press OK and you should probably restart, although it worked for me without even restarting. Went straight into downloading drivers and writing this resolution. Hope it helps someone.

EDIT: So I had my theory semi-confirmed by the fact that after working with the Internet for a bit, the connection became unidentified again, so, because of the theory, I decided to just re-enable the automatic IP resolution via DHCP and it worked. Guess Windows overwrote Ubuntu's DHCP service. This is so weird, but it works.

 

[Saga Lout]

I think it might have been worth changing the ethernet LAN settings to match those of the Wireless LAN. The wireless settings look far more realistic than the numbers in the LAN, even though they still both seem to be pointing you to your server in Riga.

Anyway, well done for fixing it but I can't see how either two installations of separate operating system could affect the others settings.

 

[dahamsta]

I think it might have been worth changing the ethernet LAN settings to match those of the Wireless LAN. The wireless settings look far more realistic than the numbers in the LAN, even though they still both seem to be pointing you to your server in Riga.

Anyway, well done for fixing it but I can't see how either two installations of separate operating system could affect the others settings.

It's hard to specify what exactly went wrong where, but the DHCP service did stop working right after booting and screwing around with Ubuntu. Thereafter it went crazy and stopped working on Windows, although it worked fine on Ubuntu, until I managed to fix the Windows connection for a while (like 5 minutes). Then I could use DHCP again. If I had to guess, it probably has something to do with my built in network card reacting to the different OS. That being said, it's just a theory and it doesn't even matter, since now, if this ever surfaces, it will be an easy fix. Thanks for the help, mate.