Wired lan does not work while wireless does.

[dpowers]

I've been scouring the web for a solution to my problem, and I haven't yet found anything similar. I have Windows XP SP3 and for some reason I can't get the wired ethernet to work right; it just won't connect to the internet. I've had a wireless usb adapter that I've been using for awhile that works fine, but now I want to be using the wired the connection. When I connect it says limited or no connectivity (yet it can still obtain an IP address) and whenever I run the repair on the connection it can't renew the IP address. It's so frustrating because I've tried just about everything and I don't get why the wireless is working while the wired isn't. I'm using a cisco linksys powerline connection to my router which I know is not the problem because I can connect and use it just fine through my Windows 7 based laptop.
Ethernet adapter Local Area Connection 2:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
        Physical Address. . . . . . . . . : 03-00-67-06-77-67
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.107
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 209.216.160.2
                                            209.216.160.131
        Lease Obtained. . . . . . . . . . : Monday, February 15, 2010 4:14:58 PM

        Lease Expires . . . . . . . . . . : Monday, February 15, 2010 6:14:58 PM

[EEVIAC]

You're able to obtain an ip address, so you're getting a connection to the router alright, but the repair network connection isn't successful which may indicate corrupt files, malware, or some run away third party program..

Next thing I would do is disable any third party firewalls (if any) and run a thorough virus scan..

Download, install, update and run malwarebytes

Then jump over to Kaspersky Online Scanner 7.0 This takes a long time and you must have Java enabled in your browser for it to work.  When it is done scanning, save the log file and post it..

edit: Before Kaspersky runs, it will go through an update process which takes a long time..When the updates are done, be sure to click on "my computer" on the left hand side to start the scan...

[dpowers]

I have BitDefender installed on my computer so here's the log file:

Product: BitDefender Antivirus 2010
Version: BitDefender Antivirus Scanner
Scanning task: Deep System Scan
Log date: 2/17/2010 2:49:49 PM
Log path: C:\Documents and Settings\All Users\Application Data\BitDefender\Desktop\Profiles\Logs\deep_scan\1266446989_1_00.xml
 
Scan paths:
Path 0000: C:\
Path 0001: J:\
Path 0002: K:\
Path 0003: F:\
 
Scan Level:
Scan for viruses: Yes
Scan for adware: Yes
Scan for spyware: Yes
Scan for applications: Yes
Scan for dialers: Yes
Scan for rootkits: Yes
Scan for keyloggers: Yes
 
Virus Scanning Options:
Scan registry keys: Yes
Scan cookies: Yes
Scan boot sectors: Yes
Scan memory processes: Yes
Scan archives: Yes
Scan runtime packers: Yes
Scan e-mails: Yes
Scan all files: Yes
Heuristic Scan: Yes
Scanned extensions: not configured
Excluded extensions: not configured
 
Target Processing:
Default first action for infected objects: Disinfect
Default second action for infected objects: None
Default first action for suspect objects : None
Default second action for suspicious objects: None
Default action for hidden objects: None
Default first action for encrypted infected objects: Disinfect
Default second action for encrypted infected objects: None
Default first action for encrypted suspicious objects: None
Default second action for encrypted suspicious objects: None
Default action for password-protected objects: Log only
 
Scan Engines Summary
Virus signatures: 5088528
Archive plugins: 44
E-mail plugins: 6
Scan plugins: 13
System plugins: 5
Unpack plugins: 8
 
Basic
Scanned items: 545733
Infected items: 0 (no infected items have been detected)
Suspect items: 0 (no suspected items have been detected)
Hidden items: 0 (no hidden items have been detected during this scan)
Resolved items: 0 (no threats have been detected during this scan)
Unresolved items: 0 (no issues remained unresolved)
 
Advanced
Scan time: 01:36:34
Files per second: 94
Skipped items: 29442
Password-protected items: 0
Over-compressed items: 0
Individual viruses found: 0
Scanned folders: 16106
Scanned boot sectors: 7
Scanned archives: 4196
Input-output errors: 34
Scanned processes: 69
Infected processes: 0
Scanned registry keys: 1197
Infected registry keys: 0
Scanned cookies: 2907
Infected cookies: 0
 

Here's the log file to the Malwarebytes:
Malwarebytes' Anti-Malware 1.44
Database version: 3748
Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

2/17/2010 12:44:21 AM
mbam-log-2010-02-17 (00-44-21).txt

Scan type: Full Scan (C:\|F:\|)
Objects scanned: 255907
Time elapsed: 3 hour(s), 54 minute(s), 16 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 5
Registry Values Infected: 0
Registry Data Items Infected: 2
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{0ed403e8-470a-4a8a-85a4-d7688cfe39a3} (Adware.Gamevance) -> Quarantined and deleted successfully.
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{f02fabcb-92dd-475a-98af-14217bd50746} (Adware.Gamevance) -> Quarantined and deleted successfully.
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Settings\{0ed403e8-470a-4a8a-85a4-d7688cfe39a3} (Adware.Gamevance) -> Quarantined and deleted successfully.
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Settings\{f02fabcb-92dd-475a-98af-14217bd50746} (Adware.Gamevance) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects\{0ed403e8-470a-4a8a-85a4-d7688cfe39a3} (Adware.Gamevance) -> Quarantined and deleted successfully.

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\AntiVirusDisableNotify (Disabled.SecurityCenter) -> Bad: (1) Good: (0) -> Quarantined and deleted successfully.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\UpdatesDisableNotify (Disabled.SecurityCenter) -> Bad: (1) Good: (0) -> Quarantined and deleted successfully.

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)

After doing that stuff the internet will still not work through the wired LAN.

[dahlarbear]

1.  Wireless NIC.  Use "Device Manager" to disable the wireless NIC, then reboot to ensure only the "wired" NIC is in the configuration.

2.  Wired NIC Connectivity.  Test your connectivity through the "wired" NIC towards the Internet using the "ping" command.  From a Command Prompt window execute the following without quotes and substitute requested information for "<>"?
     a.  "ping 127.0.0.1"                             ; TCP/IP loopback address
     b.  "ping <wired_NIC_IP_address>"         ; wired NIC IP address
     c.  "ping <your_router's_LAN_address"    ; your LAN gateway address
     d.  "ping 69.72.169.241"                       ; www.computerhope.com
     e.  "ping 139.151.188.4"                       ; www.yosemite.com

Note:  Please pay attention to the details of the command output (look for anomalies).  Specifically:
           (1)  IP address from Reply
           (2)  Percent packet loss
           (3)  Average "round trip time" in milli-seconds
           (4)  Any error/info message received in place of a reply

Reference:  Troubleshooting Connectivity Problems on Windows Networks (Part 1)

3.  DNS Name Resolution.  Use "ping" and/or "nslookup" to verify website domain names are being resolved to the correct IPv4 numeric address.
     a.  "ping www.computerhope.com"  ; reply should be from 69.72.169.241
     b.  "ping www.yosemite.com"         ; reply should be from 139.151.188.4
and/or
     c.  "nslookup www.computerhope.com"
     d.  "nslookup www.yosemite.com"

[dpowers]

Okay, here's the results:
2.a. Worked perfectly and pinged back with no loss.
b.Again worked fine pinging the connected IP address.
c-e. All failed and I couldn't ping the router address.

I'm almost wondering if maybe the network adapter is bad. I know the line is all good because I can unplug the network cable from the computer, and then plug it into my laptop and it works fine. When I plug it back into the computer, it just won't work. Maybe that computer will be stuck with the crappy usb wireless adapter.

Thanks also for the link to that network troubleshooting article.

So, anymore help or is it a hardware problem?

[EEVIAC]

Here's the log file to the Malwarebytes:
Malwarebytes' Anti-Malware 1.44
Database version: 3748
Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

2/17/2010 12:44:21 AM
mbam-log-2010-02-17 (00-44-21).txt

Scan type: Full Scan (C:\|F:\|)
Objects scanned: 255907
Time elapsed: 3 hour(s), 54 minute(s), 16 second(s)

Registry Keys Infected: 5

Registry Data Items Infected: 2

were you able to remove the viruses?

[dahlarbear]

Okay, here's the results:
2.a. Worked perfectly and pinged back with no loss.
b.Again worked fine pinging the connected IP address.
c-e. All failed and I couldn't ping the router address.

1.  Ping Results.  If the computer is able to request and then receive TCP/IP configuration from the router (DHCP server 192.168.1.1), I would expect it to successfully "ping" the router.  [Although this DHCP DORA traffic is "broadcast" (IPv4 address 255.255.255.255) to and from the router.]
     a.  What "response" was displayed for each failure?

I suspect the ping traffic through the NIC is being blocked by a firewall.  If so, make the necessary corrections, reboot, then attempt to "ping" router again.

2.  Firewall(s).  In order to "ping" successfully, your firewall(s) must be configured to permit ICMP message traffic through.  You should not have more than one third party firewall installed (including such functionality within security software suites or antivirus packages).  Please ensure you have no third party firewall(s) "enabled"; or better yet uninstall them while troubleshooting this issue.

Since you are behind a home router (which probably has firmware firewall component built-in on the WAN/Internet interface), please also ensure the Windows Firewall is "off".

3.  Route Table(s).  Configuration errors in the routing table may affect network communications.  Suggest you compare "route" table of the computer to that of the working laptop.  If you're still unable to ping router, you may "post" the computer route table.

From a Command Prompt window, enter "route print" to display the table.  To facilitate posting, you may use the optional syntax "route print > whatever.txt" which directs output to the text file.  Then you may use "notepad.exe" to view, select, copy, and paste contents to a post.

[EEVIAC]

I can agree that there is possibly a third party firewall, or third-party-whatever involved here.. He certainly had viruses that may have corrupted critical system files... A repair install might be good...

I'm not sure how Windows Firewall could be the culprit though...  I don't see any opened ports for ICMP in my Windows XP firewall and I can ping my router just fine....

[dpowers]

1.  Ping Results.  If the computer is able to request and then receive TCP/IP configuration from the router (DHCP server 192.168.1.1), I would expect it to successfully "ping" the router.  [Although this DHCP DORA traffic is "broadcast" (IPv4 address 255.255.255.255) to and from the router.]
     a.  What "response" was displayed for each failure?

I suspect the ping traffic through the NIC is being blocked by a firewall.  If so, make the necessary corrections, reboot, then attempt to "ping" router again.

2.  Firewall(s).  In order to "ping" successfully, your firewall(s) must be configured to permit ICMP message traffic through.  You should not have more than one third party firewall installed (including such functionality within security software suites or antivirus packages).  Please ensure you have no third party firewall(s) "enabled"; or better yet uninstall them while troubleshooting this issue.

Since you are behind a home router (which probably has firmware firewall component built-in on the WAN/Internet interface), please also ensure the Windows Firewall is "off".

3.  Route Table(s).  Configuration errors in the routing table may affect network communications.  Suggest you compare "route" table of the computer to that of the working laptop.  If you're still unable to ping router, you may "post" the computer route table.

From a Command Prompt window, enter "route print" to display the table.  To facilitate posting, you may use the optional syntax "route print > whatever.txt" which directs output to the text file.  Then you may use "notepad.exe" to view, select, copy, and paste contents to a post.

What I mean by failed is that I get a "Request timed out." with 100% packet loss. 4 sent, 0 received.

I'm pretty sure I don't have any third party firewalls. All I've got is the antivirus component of Bitdefender. I don't have any of the suites.
When I turn off the windows firewall I get the same results.


Route Print of faulty networking computer
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...03 00 67 06 77 67 ...... NVIDIA nForce Networking Controller - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1   192.168.1.107     20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1     1
      192.168.1.0    255.255.255.0    192.168.1.107   192.168.1.107     20
    192.168.1.107  255.255.255.255        127.0.0.1       127.0.0.1     20
    192.168.1.255  255.255.255.255    192.168.1.107   192.168.1.107     20
        224.0.0.0        240.0.0.0    192.168.1.107   192.168.1.107     20
  255.255.255.255  255.255.255.255    192.168.1.107   192.168.1.107     1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None



Route Print from working laptop
===========================================================================
Interface List
 17...00 26 c6 3c e9 7d ......Microsoft Virtual WiFi Miniport Adapter
 13...00 26 c6 3c e9 7c ......Intel(R) WiFi Link 5100 AGN
 11...00 26 9e 8b 35 0f ......Broadcom NetLink (TM) Gigabit Ethernet
  1...........................Software Loopback Interface 1
 18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
 19...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
 20...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
 16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
===========================================================================

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.105     20
        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     192.168.1.105    296
  169.254.255.255  255.255.255.255         On-link     192.168.1.105    276
      192.168.1.0    255.255.255.0         On-link     192.168.1.105    276
    192.168.1.105  255.255.255.255         On-link     192.168.1.105    276
    192.168.1.255  255.255.255.255         On-link     192.168.1.105    276
        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     192.168.1.105    276
  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     192.168.1.105    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
 16     58 ::/0                     On-link
  1    306 ::1/128                  On-link
 16     58 2001::/32                On-link
 16    306 2001:0:4137:9e76:3494:c09e:bd1b:e96b/128
                                    On-link
 11    276 fe80::/64                On-link
 16    306 fe80::/64                On-link
 16    306 fe80::3494:c09e:bd1b:e96b/128
                                    On-link
 11    276 fe80::515e:f373:51f6:f784/128
                                    On-link
  1    306 ff00::/8                 On-link
 16    306 ff00::/8                 On-link
 11    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None


I of course did these route prints by using the same network cable between the two machines.

[dahlarbear]

1.  Since you had malware, you probably should "suspend" this effort until you verify you're clean.  See here.

2.  Route Table(s).  The table for your computer looked fine.  I'm not that familiar with "wireless" or IPv6, but I didn't see any significant difference in the working laptop's table.

3.  Computer Questions.
     a.  Is the NIC onboard the motherboard or a separate card?
     b.  If onboard, what is the make and model name/number of the computer if brand name, otherwise the make and model number of the motherboard?
     c.  Has the NIC ever been used successfully?
     d.  If yes, have you reinstalled the operating system since then (chipset drivers, NIC drivers)?
     e.  If yes, has it been used successfully through the powerline adapters?

4.  Test NIC.  Previously you used "ping" to successfully traverse the TCP/IP stack on your computer (127.0.0.1 - loopback), and you were able to successfully reach the NIC by its assigned IP address (192.168.1.107 - supposedly assigned automatically via DHCP function of router).

You were not able to successfully "ping" off the computer to the router (192.168.1.1) or any other network node.  Need to demonstrate NIC can reliably send and receive data before worrying about Internet connectivity.

Keep it simple.  Best to test NIC communication with another local node, e.g. router, computer, or laptop.  (I would not test through the Powerline network.)  Recycle power on router (turn off for minute or so, then back on).  Connect both the computer and laptop to wired switch ports (LAN) of the router.  Check their TCP/IP configuation data.
     a.  From computer:
          (1)  Ping router IP address.
          (2)  Ping laptop IP address.

     b.  From router:
          (1)  Ping computer IP address.
          (2)  Ping laptop IP address.

     c.  From laptop:
          (1)  Ping router IP address.
          (2)  Ping computer IP address.

     d.  From computer, use "arp -a" command to verify it has discovered and associated the correct IP address with the correct MAC address for both the router and laptop.  The arp table entries have a short shelf life (a few minutes?).  You may have to re-issue ping to get back in table.  If they never show up - there's a problem...  You might want to practice on laptop to see what a normal arp table looks like.

     e.  From laptop, use "arp -a" to see if it can discover and associate correct IP address with correct MAC address for computer (and router).

[EEVIAC]

After verifying that you're clean from viruses, and it still doesn't work,

Download and install:

WinsockFIX



Registry entries may have been permanently corrupted form malware, so it may work...

[dpowers]

Well, thanks for the help but I think I give up. It seems to be something pretty complicated that's wrong with it and I don't really want to mess with it. I guess that computer will be stuck with the wireless g adapter. So, thanks everybody.

[dahlarbear]

1.  If you're looking for the "Easy Button", open a Command Prompt window and try the following (without the quotes) to reset Windows Firewall, TCP/IP, and Winsock software/registry entries:
     a.  "netsh firewall reset"

     b.  "netsh int ip reset c:\resetlog.txt"

     c.  "netsh winsock reset catalog"

Note:  Should be done from user account (that is member of Administrators group).  The machine owners account is probably one of those.  Let each command finish before entering the next.  Reboot when done and retry Internet access.

2.  It's always possible the NIC hardware is faulty.  Generally you would try a different "wired" NIC possibly in another expansion card slot (to get different resource assignments).

Other than that, good luck...

[EEVIAC]

There is the possibility that the router needs a firmware update..  It may be a bug that a more recent version may fix..

[dodat]

Not sure if you want to try this as I had something similar with a lenovo R400 after removing the stupid access connections software they ship with.

I went to the Advanced TCP/IP Settings of the LAN adapter and set the Interface Metric to 10 (unchecking Automatic metric) on the wireless set the metric to 15, this seemed to help a lot.

Started a 2GB xfer on wireless and when attaching the LAN cable the flow switched to the LAN without restarting.

Previously the Automatic metric was set to LAN = 20 and WiFi = 25 and with both adapters connected traffic would only flow across the WiFi link.

Time will tell if it helps long term

[veni]

For this problem, you contact the Internet service provider,
After that check your ping test, through this site http://www.whoisxy.com/ping.aspx
It has the best information of IP address, IP address to domain, domain name to IP,domain name, hosting, and ping test to know the particular connection is online or not!!!!!

[Sid]

For this problem, you contact the Internet service provider,
After that check your ping test, through this site http://www.whoisxy.com/ping.aspx
It has the best information of IP address, IP address to domain, domain name to IP,domain name, hosting, and ping test to know the particular connection is online or not!!!!!

So contacting the ISP about a LAN issue...

If you're here to learn, please refrain from giving rubbish advice.

OP, what happens if you set the IP address manually?