Unidentified Network LAN to router won't connect.

[mcgyber0o0]

I have tried everything I, and others on many forums, can think of to fix this issue. I have tried static network settings, re installing my network card, restarting winsock, disabling bonjour, route delete 0.0.0.0, editing the group policy to change unidentified networks to work networks, and many others. The same PC booting to linux does not have an issue. It connects to the router and I have internet. This problem has exhausted my knowledge and resources. This computer is my fathers and it had a virus that messed with a number of network settings. I removed the virus and have a wireless USB adapter working right at the moment; however I would like to get the LAN working. The LAN won't connect to anything. Not the router, laptop via crossover cable, or cable modem. The PC has Microsoft Windows 7 x64 Ultimate / Ubuntu 11.10. Integrated LAN.

Here is the ifconfig from linuxmint:

mint ~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:22:15:ee:ae:d0  
          inet addr:192.168.1.12  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::222:15ff:feee:aed0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1812 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1329 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2038462 (2.0 MB)  TX bytes:149297 (149.2 KB)
          Interrupt:18 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1120 (1.1 KB)  TX bytes:1120 (1.1 KB)

wlan0     Link encap:Ethernet  HWaddr e0:91:f5:1b:ee:8a  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Here is my Windows 7 x64 ipconfig /all:

C:\Windows\system32>ipconfig /all

Windows IP Configuration

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

Wireless LAN adapter Wireless Network Connection 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
   Physical Address. . . . . . . . . : E0-91-F5-1B-EE-8A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Netgear Wireless:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : NETGEAR WG111v3 Wireless-G USB Adapter
   Physical Address. . . . . . . . . : E0-91-F5-1B-EE-8A
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5c18:dd84:d1fa:cddf%19(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Thursday, February 23, 2012 1:29:04 PM
   Lease Expires . . . . . . . . . . : Friday, February 24, 2012 1:29:04 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 283152885
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-2A-3C-41-00-22-15-EE-AE-D0

   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter LAN:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigab
it Ethernet Controller
   Physical Address. . . . . . . . . : 00-22-15-EE-AE-D0
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Autoconfiguration IPv4 Address. . : 169.254.14.251(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{921474D8-A698-4C22-A364-F36791C7AA04}:

   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 Local Area Connection* 11:

   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:4137:9e76:38ac:2919:e78b:6510(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::38ac:2919:e78b:6510%15(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{613C2F88-1164-42AC-8877-627B794D5781}:

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

C:\Windows\system32>

Here is my Windows 7 x64 route print -4:

C:\Windows\system32>route print -4
===========================================================================
Interface List
 20...e0 91 f5 1b ee 8a ......Microsoft Virtual WiFi Miniport Adapter
 19...e0 91 f5 1b ee 8a ......NETGEAR WG111v3 Wireless-G USB Adapter
 17...00 22 15 ee ae d0 ......Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethern
et Controller
  1...........................Software Loopback Interface 1
 23...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 15...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
 25...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1      192.168.1.6     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      169.254.0.0      255.255.0.0         On-link    169.254.14.251    276
   169.254.14.251  255.255.255.255         On-link    169.254.14.251    276
  169.254.255.255  255.255.255.255         On-link    169.254.14.251    276
      192.168.1.0    255.255.255.0         On-link       192.168.1.6    281
      192.168.1.6  255.255.255.255         On-link       192.168.1.6    281
    192.168.1.255  255.255.255.255         On-link       192.168.1.6    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link    169.254.14.251    276
        224.0.0.0        240.0.0.0         On-link       192.168.1.6    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link    169.254.14.251    276
  255.255.255.255  255.255.255.255         On-link       192.168.1.6    281
===========================================================================
Persistent Routes:
  None

C:\Windows\system32>

 

[Dwarf]

The fact that you can connect when running Linux but not Windows means that the hardware itself is functional. This would probably be a driver issue. In Device Manager, look to see if there is a warning triangle in the Network adapter section.

 

[mcgyber0o0]

The driver is functioning normally according to the manager. I have reinstalled the driver a dozen times with the manufacturer and windows update drivers. Neither seem to help.

 

[Dwarf]

Just noticed that the assigned address is in the 169.XXX.XXX.XXX range. This indicates that the DHCP server was unable to provide an address, and so Windows automatically issued one in the above range.

See if the following videos (note that the audio on the first one is not very loud) help:

 

[mcgyber0o0]

I have done the steps in the videos before, however I did them again hoping they would work this time. Unfortunately it did not.

 

[mcgyber0o0]

It seems it won't connect to the router at all. It says that it cannot get an ip address and that the default gateway does not exist. I would suspect the dhcp service isn't working, restarting the service then plugging in the LAN cable gets a home network to show up with Internet access, but it's just saying that. It doesn't have Internet access or connectivity to the router (cannot ping gateway). It later reflects that in the network and sharing center.

Ps. The router is brand new and working fine. I have tested it with numerous devices on all ports.

 

[Dwarf]

So you're saying that you can connect OK via LAN whilst in Linux, but not Windows? That means that the hardware is working OK, and also that you don't need to perform a factory reset on your router (which is another thing you could have tried, after making sure that you had the configuration information from your ISP to plug back in to it afterwards).

It is possible that this malware that you have had on this machine still has some foothold on it, and is causing the problem. You say that you have removed the virus, but have you managed to eradicate it fully? I'm going to request our malware specialists to have a look. They might require you to download and run various tools, so please do as requested and post back with any files/documents that they ask for.

 

[Petey7]

It's more than likely that part of the virus you meantioned or another virus still exist on the computer. I would run a scan with Malwarebytes and SuperAntiSpyware. I would also run CCleaner to clean up all temp files and clear the DNS cache. While I'm on the topic of the DNS cache, you can try copying and pasting what I have below into notepad and saving it as flush.bat to your desktop. right-click the bat file and select "Run as Administor" to run it. It might get the internet working again without having to do what I mentioned already.

@Echo on
pushd\windows\system32\drivers\etc
attrib -h -s -r hosts
echo 127.0.0.1 localhost>HOSTS
attrib +r +h +s hosts
popd
ipconfig /release
ipconfig /renew
ipconfig /flushdns
netsh winsock reset all
netsh int ip reset all
shutdown -r -t 1
del %0

 

[Golden]

Hi,

Presumably this virus was caught using Windows, and not Linux? I'm pretty sure this is not going to deliver anything, but as a precaution lets check for infection inside Linux.

1. Open a terminal in Mint, and run the folliowing to download and install CLAM antivirus and the GUI interface:

sudo apt-get install clamav clamtk

2. Now check that the database is up-to-date:

sudo freshclam

Locate the item called Virus Scanner, and run a scan of your system (note that the GUI interface will be marked as outdated, you can ignore that). If it comes up clean, we can cross off an infection in Linux.

CLAMAV screen capture shown below so you know what you are looking for.

Regards,
Golden

 

[carwiz]

If the virus corrupted settings in the Tcpip Parameters, Windows may not even be looking for a router. I see that your DNS Suffix Search List is not present. In a standalone homegroup LAN this should specify "Router". Take a quick look at the Tcpip Parameters located at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters

I've attached a copy of my settings to compare.