New router works on wi-fi but not on LAN

[Arakkan]

Hello, I just bought a new router form my ISP and is a combo router/modem (Comtrend AR-5381u) and my desktop can connect via wi-fi just fine, serf the internet and whatnot at the speeds I pay for, but on whiles its on Ethernet (which i vastly prefer) the connection is awfully slow and i cannot connect to anything on the internet (usually works slowly for about a minute) I get DNS_Probe_not_found and time out and have huge latency issues. I use a static IP so i thought that would be the problem so i went back to dynamic ip and the problem still persists (I also set my DNS server to 8.8.8.8 and 8.8.4.4), I know that my LAN card is not the issue because my Ethernet worked fine literally right before installing this new router. I would appreciate help on this! thank you!

 

[gbb0330]

Hello, I just bought a new router form my ISP and is a combo router/modem (Comtrend AR-5381u) and my desktop can connect via wi-fi just fine, serf the internet and whatnot at the speeds I pay for, but on whiles its on Ethernet (which i vastly prefer) the connection is awfully slow and i cannot connect to anything on the internet (usually works slowly for about a minute) I get DNS_Probe_not_found and time out and have huge latency issues. I use a static IP so i thought that would be the problem so i went back to dynamic ip and the problem still persists (I also set my DNS server to 8.8.8.8 and 8.8.4.4), I know that my LAN card is not the issue because my Ethernet worked fine literally right before installing this new router. I would appreciate help on this! thank you!

run the following in command prompt:

ipconfig /all

on both WiFi and wired and post the results.

 

[Arakkan]

I would prefer if you just told me what you are looking for, I could post that.

 

[gbb0330]

I would prefer if you just told me what you are looking for, I could post that.

i am looking for the IP config results, all of it.

you can use ipconfig /all > c:\ipconfig.txt

to send the results to a text file for easy copy pasting. there is no personally identifiable info in any of this, just network settings, most likely wrong, every computer has those.

 

[Arakkan]

XXXXX

 

[gbb0330]

Windows IP Configuration

Host Name . . . . . . . . . . . . : XXXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Home

Wireless LAN adapter Wireless Network Connection 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 8A-94-F6-26-F9-B8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : Home
Description . . . . . . . . . . . : TP-LINK 450Mbps Wireless N Adapter
Physical Address. . . . . . . . . : E8-94-F6-26-F9-B8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::31ad:f6c1:df1:7170%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.5.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Saturday, August 08, 2015 10:29:40 AM
Lease Expires . . . . . . . . . . : Sunday, August 09, 2015 10:29:40 AM
Default Gateway . . . . . . . . . : 192.168.5.1
DHCP Server . . . . . . . . . . . : 192.168.5.1
DHCPv6 IAID . . . . . . . . . . . : 350786806
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-42-16-4D-44-8A-5B-88-54-E0
DNS Servers . . . . . . . . . . . : 206.169.38.2
206.169.38.3
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : Home
Description . . . . . . . . . . . : Killer e2200 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
Physical Address. . . . . . . . . : 44-8A-5B-88-54-E0
DHCP Enabled. . . . . . . . . . . : Yes
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 isatap.Home:

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

Tunnel adapter isatap.{9B3531F2-D213-450D-BF4E-AC167EDE68DE}:

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

according to what you have posted above your network card is not connected. Please confirm the Ethernet cable is plugged in and there is a green light on both the network card port and the the router port.

 

[Arakkan]

Hahahahahaha if it were that simple then I would not be posting here! Yes it is plugged in because I can still get onto the internet (sometimes and very slowly) while on Ethernet and my wi-fi card disabled.

Opps I did this while on my wi-fi card (not Ethernet), maybe that was the problem?

 

[gbb0330]

Hahahahahaha if it were that simple then I would not be posting here! Yes it is plugged in because I can still get onto the internet (sometimes and very slowly) while on Ethernet and my wi-fi card disabled.

Opps I did this while on my wi-fi card (not Ethernet), maybe that was the problem?

disable WiFi
open 2 separate command prompt windows
run the following ping tests, for a about 5 minutes, press ctrl + c to interrupt them and look for statistics at the end, post results

ping 8.8.8.8 -t

ping 192.168.5.1 -t

 

[Arakkan]

Weird, there was a TON of results in CMD but it only saved a few of them, but I did indeed run it for 5 minutes.


Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=24ms TTL=56
Reply from 8.8.8.8: bytes=32 time=24ms TTL=56
Reply from 8.8.8.8: bytes=32 time=23ms TTL=56
Reply from 8.8.8.8: bytes=32 time=24ms TTL=56
Reply from 8.8.8.8: bytes=32 time=24ms TTL=56
Reply from 8.8.8.8: bytes=32 time=24ms TTL=56
Reply from 8.8.8.8: bytes=32 time=23ms TTL=56
Reply from 8.8.8.8: bytes=32 time=24ms TTL=56
Reply from 8.8.8.8: bytes=32 time=24ms TTL=56
Reply from 8.8.8.8: bytes=32 time=24ms TTL=56

Ping statistics for 8.8.8.8:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 24ms, Average = 23ms

Pinging 192.168.5.1 with 32 bytes of data:
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64
Reply from 192.168.5.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.5.1:
Packets: Sent = 29, Received = 29, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Also I ping youtube which i could not get onto (got ERR_Name_Not_Resolved)

Pinging youtube.com [216.58.218.206] with 32 bytes of data:
Reply from 216.58.218.206: bytes=32 time=24ms TTL=55
Reply from 216.58.218.206: bytes=32 time=24ms TTL=55

Ping statistics for 216.58.218.206:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 24ms, Average = 24ms

 

[gbb0330]

Weird, there was a TON of results in CMD but it only saved a few of them, but I did indeed run it for 5 minutes.


Ping statistics for 216.58.218.206:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 24ms, Average = 24ms

something went wrong with the test, looks like you tried multiple times and the results you posted are inconclusive because very few packets were sent 8.8.8.8 - 10 packets sent, 192.168.5.1 - 29 packets sent and 216.58.218.206 only 2. I am interested in the part at the very end, "Ping Statistics" and below. but for the results to be meaningful we need to send about 1000 packets.

 

[Arakkan]

Ah I see, but in the end I managed to fix it by uninstalling and reinstalling the drivers. I don't know what went wrong but if it works now that is all I am interested in! Thanks so much for your help man! I know that doing all of this is a lot of work because some of my buddies wouldn't help me without cash in their hand! Thank you so much!

 

[gbb0330]

Ah I see, but in the end I managed to fix it by uninstalling and reinstalling the drivers. I don't know what went wrong but if it works now that is all I am interested in! Thanks so much for your help man! I know that doing all of this is a lot of work because some of my buddies wouldn't help me without cash in their hand! Thank you so much!

you are welcome, glad you figured it out, those killer NICs do have weird driver issues sometimes.