I don't get the full internet speed that I should have.
I don't get the full internet speed that I should have.
I am having trouble getting the best internet speed with my ethernet cable. I plugged the cable into a laptop sitting next to my desktop, and the test showed 1Gbps download but only 30Mbps upload on speedtest.net. When I ran the same test from my own desktop, it showed 300Mbps download and 30Mbps upload. The test doesn't show 300Mbps directly; instead, it starts at 60Mbps and slowly goes up to reach 300Mbps at the end. I tried putting in a live Linux disc to see if Windows was the issue, but that didn't help. Next, I checked my motherboard and found an ethernet speed cap set to 1Gbps, which should be enough for me. So far so good. Here are all my computer details just in case something is wrong: OS Name Microsoft Windows 10 Pro N Version 10.0.19044 Build 19044 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name DESKTOP-D594G2B System Manufacturer Gigabyte Technology Co., Ltd. System Model X58A-UD3R System Type x64-based PC System SKU Processor Intel® Core™ i7 CPU 950 @ 3.07GHz, 3060 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date Award Software International, Inc. FA, 2010-04-20 SMBIOS Version 2.4 Embedded Controller Version 255.255 BIOS Mode Legacy BaseBoard Manufacturer Gigabyte Technology Co., Ltd. BaseBoard Product X58A-UD3R BaseBoard Version x.x Platform Role Desktop Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume3 Locale United States Hardware Abstraction Layer Version = "10.0.19041.1806" User Name DESKTOP-D594G2B\Ewan Time Zone Eastern Daylight Time Installed Physical Memory (RAM) 20.0 GB Total Physical Memory 19.2 GB Available Physical Memory 12.6 GB Total Virtual Memory 22.1 GB Available Virtual Memory 13.7 GB Page File Space 2.88 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes (I know I have an old computer) Thanks for any help!
Does your hard drive handle that fast? Whatever you're pulling down from the internet, whether it's a speed test or something else, everything needs to sit on your computer first. It gets saved in temporary files on the C drive before it goes anywhere else.
nvm got the answer here. The mainboard has a realtek card meant for 1Gbit, but it's sending data using four twisted pairs at 250MB each. This trick uses PAM5 line coding, which is outdated now (today they use 1000BASE-TX). You might need new cables or a better network card. Check the spec sheet of your network card on page 13 for more info.
Will this network card be right for you? You can check the link below.
It would be very odd to find a device that supports 1000 base-x. Even back in the day, this was so rare and didn't even work when it first came out. I saw some routers and switches from cisco around year 2000 with support for it, but your board has web pages listing specs even though the internet wasn't really there then. That makes it very unlikely your board uses that protocol. Maybe it does now, but if it did, you could probably sell this board to someone who loves collecting old stuff for a lot of money. What happens when you plug a 1000 base-x cable into a modern 1000 base-port is that the connection only works at 100 Mbps instead of the promised speeds. This means you won't get 300 Mbps, even though you sometimes do see 300 Mbps. Since you can get 300 Mbps now, the port is probably fine and just using full data encoding, but something else is wrong. Since you have already tried fixing the key problem I mentioned, it's almost certain to be a hardware issue with your nic card. Even though nic cards are cheap, I recommend trying linux again mostly because of that strange hardware glitch rather than assuming one of those old protocols was broken.