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!
New router works on wi-fi but not on LAN
- Thread starter Arakkan
- Start date
gbb0330
Reputable
- Apr 28, 2015
- 1,498
- 0
- 5,960
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.
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?
Opps I did this while on my wi-fi card (not Ethernet), maybe that was the problem?
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
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
Reputable
- Apr 28, 2015
- 1,498
- 0
- 5,960
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.
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!
TRENDING THREADS
-
Question User RX 580 8gb red devil powercolor, asking original BIOS- Started by PizzaInGame
- Replies: 5
-
-
-
News Microsoft updates Windows 11 24H2 requirements, CPU must support SSE4.2 or the OS will not boot- Started by Admin
- Replies: 14
Facebook
Twitter
Instagram