Question Network card bad ?

Toggle sidebar Toggle sidebar
D

duceduc

Distinguished
Dec 25, 2014
27
0
18,530
Hello. I have a strange issue. I was able to access the internet when I got home, but after a few hours, I lost internet connection AND unable to access my main router. NIC has gone semi bad??

What I can still do:
Access other local devices. Ex. AP router. ssh into my rpi.
All wifi devices are able to connect to the internet
PC in question is able to access the internet and main router via the built in wifi network card.

What I have done so far to fix it:
Reset the nic using ipconfig cmd
Power off the main router
Physically removed the nic card from pc and plug it back in
Direct connect the pc cable to the main router itself bypassing the unmanaged switch.

What I think has gone bad:
NIC. But why I can still access other local devices?
The patch cable from the pc to the outlet and or the cable from the outlet to the unmanaged switch. But I am able to access other local devices.

Below is how the pc is setup. Excuse the rough images.

diagram.jpg
 
duceduc said:
Hello. I have a strange issue. I was able to access the internet when I got home, but after a few hours, I lost internet connection AND unable to access my main router. NIC has gone semi bad??

What I can still do:
Access other local devices. Ex. AP router. ssh into my rpi.
All wifi devices are able to connect to the internet
PC in question is able to access the internet and main router via the built in wifi network card.

What I have done so far to fix it:
Reset the nic using ipconfig cmd
Power off the main router
Physically removed the nic card from pc and plug it back in
Direct connect the pc cable to the main router itself bypassing the unmanaged switch.

What I think has gone bad:
NIC. But why I can still access other local devices.
the patch cable from the pc to the outlet and or the cable from the outlet to the unmanaged switch. But I am able to access other local devices.

Below is how the pc is setup. Excuse the rough images.

diagram.jpg
Click to expand...
I assume you access your local devices by IP address. It is more likely that you are having DNS issues. If you can ping 8.8.8.8 but not www.google.com, then you need to investigate DNS.
Windows has a cmd.exe program "nslookup" that can help debug DNS.
 
Is this correct in testing the nslookup??

-
Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Duc>nslookup 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.1

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users\Duc>nslookup www.google.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
-
 
duceduc said:
Is this correct in testing the nslookup??

-
Microsoft Windows [Version 10.0.19045.4170]
(c) Microsoft Corporation. All rights reserved.

C:\Users\Duc>nslookup 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.1

DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users\Duc>nslookup www.google.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
-
Click to expand...
That shows you are having DNS problems. You can add a DNS override to the end of the nslookup command. Use the /? to see the syntax.
 
Sorry, I am not understanding what nslookup is doing. I am no able to access my main router to begin with.

--
C:\Users\Duc>nslookup isc.org 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 8.8.8.8

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users\Duc>nslookup yahoo.com 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 8.8.8.8

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
--
 
duceduc said:
Sorry, I am not understanding what nslookup is doing. I am no able to access my main router to begin with.

--
C:\Users\Duc>nslookup isc.org 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 8.8.8.8

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

C:\Users\Duc>nslookup yahoo.com 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 8.8.8.8

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
--
Click to expand...
There is something strange going on. Your "nslookup yahoo.com 8.8.8.8" should have returned
C:\Windows\System32>nslookup yahoo.com 8.8.8.8
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: yahoo.com
Addresses: 2001:4998:124:1507::f000
2001:4998:24:120d::1:1
2001:4998:24:120d::1:0
2001:4998:44:3507::8000
2001:4998:44:3507::8001
2001:4998:124:1507::f001
74.6.143.26
74.6.231.20
98.137.11.164
98.137.11.163
74.6.143.25
74.6.231.21
I don't know if that means there is corruption somewhere in your Windows files.
Does ping 8.8.8.8 work ?
You could try a bootable Linux USB drive. See if the problems are gone when you run Linux.
 
Your system certainly isn't getting outside of your internal network it seems and this could be software related if it's not configuration.

When you do ipconfig /all do all of these have something in them? (I cleared a bunch of useless information from mine so you'll see a lot more entries):
Ethernet adapter Ethernet 8:

Description . . . . . . . . . . . : Intel(R) Ethernet Server Adapter X520-2 #5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.10.10.15(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : xxxxxxxxxxxxxxx
Lease Expires . . . . . . . . . . : xxxxxxxxxxxxxxx
Default Gateway . . . . . . . . . : 10.10.10.1
DHCP Server . . . . . . . . . . . : 10.10.10.1
DNS Servers . . . . . . . . . . . : 10.10.10.1
 
duceduc said:
Hello. I have a strange issue. I was able to access the internet when I got home, but after a few hours, I lost internet connection AND unable to access my main router. NIC has gone semi bad??

What I can still do:
Access other local devices. Ex. AP router. ssh into my rpi.
All wifi devices are able to connect to the internet
PC in question is able to access the internet and main router via the built in wifi network card.

What I have done so far to fix it:
Reset the nic using ipconfig cmd
Power off the main router
Physically removed the nic card from pc and plug it back in
Direct connect the pc cable to the main router itself bypassing the unmanaged switch.

What I think has gone bad:
NIC. But why I can still access other local devices.
the patch cable from the pc to the outlet and or the cable from the outlet to the unmanaged switch. But I am able to access other local devices.

Below is how the pc is setup. Excuse the rough images.

diagram.jpg
Click to expand...
Can you ping the router? If not, try a different port on the switch.
 
@ kanawolf
ping 8.8.8.8. No does not work.

C:\Users\Duc>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

@ daleH
No, I cannot ping the main router. ping AP router, ok. I hav tried swithing to different ports on the router that connects to the swith and also tried a differnent port on the switch that is connecting to the pc.

@ thestryker
ipconfig suggest I should be connected to the router, but no internet and no access to main router config page.

ipconfig /all
-
C:\Users\Duc>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-FDDL8I4
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Realtek PCIe 2.5GbE Family Controller
Physical Address. . . . . . . . . : B4-4B-D6-27-22-55
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fd7e:ec81:d1f2:0:355d:a143:8f0d:b55(Preferred)
Temporary IPv6 Address. . . . . . : fd7e:ec81:d1f2:0:d137:7d9:e6d0:8590(Preferred)
Link-local IPv6 Address . . . . . : fe80::6b6e:4d26:b4e2:d708%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.111(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, March 14, 2024 7:59:31 AM
Lease Expires . . . . . . . . . . : Friday, March 22, 2024 7:59:30 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 213142486
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-0E-8C-78-B4-4B-D6-27-22-55
DNS Servers . . . . . . . . . . . : 192.168.1.1
fd7e:ec81:d1f2::1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Zscaler Network Adapter 1.0.2.0
Physical Address. . . . . . . . . : 00-FF-77-84-3C-FF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 5C-F3-70-89-CE-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

C:\Users\Duc>
-
 
That configuration looks like it should which leads me to believe there might be something software wise on your computer preventing traffic. I can't think of anything off the top of my head that would do this, but if you've installed anything recently start there.
 
I have not installed any new devices or config the router. In the morning, the pc was working fine and was shut down. In the evening, it was working for a few hours. PC was idle for about an hour, then connection lost.

It is not the lan cables. I have run a patch cord from the pc to the ap router. Same issue. Cannot access the internet nor the main router. Able to ping local devices.

Either is the nic hardware or some settings in the router/pc that is preventing me from accessing the main router.
 
C:\Users\Duc>tracert 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

1 * <1 ms * SER [192.168.1.20]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * 3 ms 2 ms dns.google [8.8.8.8]

Trace complete.
 
duceduc said:
I have not installed any new devices or config the router. In the morning, the pc was working fine and was shut down. In the evening, it was working for a few hours. PC was idle for about an hour, then connection lost.

It is not the lan cables. I have run a patch cord from the pc to the ap router. Same issue. Cannot access the internet nor the main router. Able to ping local devices.

Either is the nic hardware or some settings in the router/pc that is preventing me from accessing the main router.
Click to expand...
duceduc said:
I have not installed any new devices or config the router. In the morning, the pc was working fine and was shut down. In the evening, it was working for a few hours. PC was idle for about an hour, then connection lost.

It is not the lan cables. I have run a patch cord from the pc to the ap router. Same issue. Cannot access the internet nor the main router. Able to ping local devices.

Either is the nic hardware or some settings in the router/pc that is preventing me from accessing the main router.
Click to expand...
Sure sounds like the NIC. Are you using the one on the mother board or a NIC card? I'm thinking you'll have to at least temporarily try another NIC to prove conclusively.
 
duceduc said:
C:\Users\Duc>tracert 8.8.8.8

Tracing route to 8.8.8.8 over a maximum of 30 hops

1 * <1 ms * SER [192.168.1.20]
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * 3 ms 2 ms dns.google [8.8.8.8]

Trace complete.
Click to expand...
The interesting thing is trying .20 rather than .1 which was listed as the default gateway in post #9. Could you have a second DHCP server or a sibling that is trying to break your internet access via ARP poisoning?
 
Is it possible a setting on the router is blocking the traffic?

As I said before your IP configuration is good, but you cannot even reach the router. This is extremely unlikely to be any sort of hardware fault it's configuration or software related.
 
I do have an onboard nic card but it was not working proper when I first installed built the system. I think it didn't work or something. Can remember now. So purchased a 3rd party nic card and have used that since.

The only dhcp server enable is from the main router. I have disabled dhcp server on the ap router.
 
duceduc said:
I do have an onboard nic card but it was not working proper when I first installed built the system. I think it didn't work or something. Can remember now. So purchased a 3rd party nic card and have used that since.

The only dhcp server enable is from the main router. I have disabled dhcp server on the ap router.
Click to expand...
Do you know what device is .20 ?
 
Just to recap of my issue. I am not able to access the main router nor the Internet with the NIC which is a wire connection.
However, I am able to access the main router and the Internet with the built in wireless nic card. Both connections the dhcp are set to automatic on the pc. Router is assigning an ip address.
 
Update: It is the evening same day since my last post. My internet connection is back up and I am able to access my router. I have done nothing to resolve the issue other than to switch back to the network card every so often throughout the day. I will swap out the nic with another to rule out a faulty card.

It's strange but most likely a coincident. It' about the same time yesterday that this issue occurred. Now it's working again.

C:\Users\Duc>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ac1750.lan [192.168.1.1]
2 <1 ms <1 ms <1 ms 192.168.128.2
3 3 ms 3 ms 2 ms 192.168.22.5
4 4 ms 3 ms 5 ms 27.85.212.101
5 4 ms 5 ms 5 ms 27.86.120.49
6 3 ms 3 ms 3 ms 27.85.230.50
7 3 ms 2 ms 3 ms 72.14.208.177
8 4 ms 4 ms 4 ms 108.170.242.193
9 3 ms 3 ms 3 ms 108.170.235.103
10 2 ms 2 ms 2 ms dns.google [8.8.8.8]

Trace complete.
 
duceduc said:
Update: It is the evening same day since my last post. My internet connection is back up and I am able to access my router. I have done nothing to resolve the issue other than to switch back to the network card every so often throughout the day. I will swap out the nic with another to rule out a faulty card.

It's strange but most likely a coincident. It' about the same time yesterday that this issue occurred. Now it's working again.

C:\Users\Duc>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ac1750.lan [192.168.1.1]
2 <1 ms <1 ms <1 ms 192.168.128.2
3 3 ms 3 ms 2 ms 192.168.22.5
4 4 ms 3 ms 5 ms 27.85.212.101
5 4 ms 5 ms 5 ms 27.86.120.49
6 3 ms 3 ms 3 ms 27.85.230.50
7 3 ms 2 ms 3 ms 72.14.208.177
8 4 ms 4 ms 4 ms 108.170.242.193
9 3 ms 3 ms 3 ms 108.170.235.103
10 2 ms 2 ms 2 ms dns.google [8.8.8.8]

Trace complete.
Click to expand...
For some reason the .20 address (your server) is not the default gateway. Notice that .1 is the first hop in the above tracert. Your post #13 shows .20 as the default gateway (first hop). There is something wrong internally on your network. It is acting like a second DHCP server is configured. A PC just sends out a DHCP request. The first one to respond "wins". If you have two configured the results are unpredictable.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom