Problem with new ethernet card

kbidols

Distinguished
Mar 21, 2010
37
0
18,530
Hi, I'm having an issue about my new ethernet card. My onboard ethernet port got hit by lightning recently. I can see that, because the light on the port would not go off even when there's no LAN cable attached to it and it dissapeared mytesriously from the device manager.

So I decided to buy a PCI ethernet card and a LAN to USB device. When I first install the ethernet card (D-LINK DFE-520TX) I got no connection at all, it keeps saying that I have an unidentified network. So I deleted/uninstalled Bonjour service which is mostly from Adobe products. Then I tried again to see if it can connect, and yes it says "Network: Internet Access" on the bottom right icon. I thought that was it, but when I tried pinging to my router, it almost failed everytime.

Pinging gives me this result:

Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.

Ping statistics for 192.168.1.1:
Packets: Sent = 2138, Received = 1090, Lost = 1048 (49% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3ms, Average = 0ms


The ethernet card is there on the device manager with no exclamation point or question mark. I tried reinstalling the latest driver from its website but no luck the problem still persist. I did uninstall/reinstall the ethernet card, disable/enable it, disabling Avast!, disabling Windows Firewall, clearing with CCleaner, use a manual IP address, change back to obtain automatic IP address, run all sorts of ipconfig command, cleared the DHCP, and obviously tried to do all of that from safe mode with networking. I checked the NETWORK AND SHARING CENTER and clicked on the LOCAL AREA CONNECTION 2, it shows that I received only few packets. The diagnose result says that "The network gateway is accessible, but Windows couldn't receive traffic from the Internet". It's all in these pictures:

http://imageshack.us/photo/my-images/189/1o6m.jpg/
http://imageshack.us/photo/my-images/811/szi5.jpg/

I checked with Speccy to see if my network card had problems. This is the result given:

Network
You are connected to the internet
Connected through D-Link DFE-520TX PCI Fast Ethernet Adapter
IP Address 192.168.1.102
Adapter Type Ethernet
WinInet Info
LAN Connection
Local system uses a local area network to connect to the Internet
Local system has RAS to connect to the Internet
Wi-Fi Info
Wi-Fi not enabled
WinHTTPInfo
WinHTTPSessionProxyType No proxy
Session Proxy
Session Proxy Bypass
Connect Retries 5
Connect Timeout 60000
HTTP Version HTTP 1.1
Max Connects Per 1.0 Servers INFINITE
Max Connects Per Servers INFINITE
Max HTTP automatic redirects 10
Max HTTP status continue 10
Send Timeout 30000
IEProxy Auto Detect No
IEProxy Auto Config
IEProxy
IEProxy Bypass
Default Proxy Config Access Type No proxy
Default Config Proxy
Default Config Proxy Bypass

Other than that I've tried connecting the LAN cable to my laptop (the one I use to write this) and the internet works just fine. As well as using the LAN to USB device on the "defect" PC and can connect to internet fine untill yesterday another lightning strikes that device and made it dead. So it musn't be a cable issue I believe. I've also tried connecting the LAN cable directly to the modem given by my ISP, and still no internet connection. The only thing that I haven't done is to disable onboard LAN, because I just don't know where to find it on the BIOS.

Additional info:

PC Specs:
Windows 7 Ultimate 32-bit
Intel Core2Quad 2,33GHz
4GB RAM
Gigabyte Motherboard G31M-S2C (Socket 775)

I have 4 computer connecting to the same router, 2 PC's and 2 laptops. One PC running Windows XP (internet works just fine), 1 PC running Win 7 ultimate (the one that has no internet), 1 laptop running Win Vista Home Premium (internet works fine via wireless/wired), and 1 laptop running Win 7 Home Premium (internet works fine via wireles/wired).

Please kindly help me. I've looked it up almost everywhere on the internet for solution with no luck at all.
Thank you.
 

kbidols

Distinguished
Mar 21, 2010
37
0
18,530


the router is working fine. the other computers can connect to the internet even with the LAN cable used for the "defect" PC.