F5F Stay Refreshed Power Users Networks Issues with RJ45 network connection on Aurora R11

Issues with RJ45 network connection on Aurora R11

Issues with RJ45 network connection on Aurora R11

A
AM72
Member
76
09-15-2023, 06:37 AM
#1
Dell R11 all OEM, no modifications made. I was adjusting settings on my TP-link WiFi router as an access point from the main router. After that, connections would drop randomly initially, and today I lost all connection even when connecting directly to the main router. A few days later, the connection returned but only supported 100MB, not the previous 1GB. I tried a cat cable (it worked), connected another PC (functioned at 1GB), and WiFi remained unaffected. I've changed the network cable and reinstalled drivers, removed the Killer APP. I'm open to suggestions, but considering installing another PCIe network card since it's on the motherboard? Thanks.
A
AM72
09-15-2023, 06:37 AM #1

Dell R11 all OEM, no modifications made. I was adjusting settings on my TP-link WiFi router as an access point from the main router. After that, connections would drop randomly initially, and today I lost all connection even when connecting directly to the main router. A few days later, the connection returned but only supported 100MB, not the previous 1GB. I tried a cat cable (it worked), connected another PC (functioned at 1GB), and WiFi remained unaffected. I've changed the network cable and reinstalled drivers, removed the Killer APP. I'm open to suggestions, but considering installing another PCIe network card since it's on the motherboard? Thanks.

X
xShaay
Junior Member
41
09-18-2023, 12:47 AM
#2
It was about modifying settings on my TP-link WiFi router as an access point connected to the main router. Did you perform a factory reset on either the primary router or the TP-Link device? Possibly both. What adjustments were made? Focus on any modifications related to static IP assignments, subnet configurations, MAC addresses, and network-specific settings.

I recommend verifying that DHCP is turned off on the TP-Link WiFi router. In many small networks, only one device should be handling IP address requests.

Count the number of network devices present: wired, wireless, DHCP-managed IPs, and static IPs.

Run "ipconfig /all" through the Command Prompt on your main computer and also on a device connected via the AP. Note the complete outputs from both executions, labeling them by the respective machines.

If you’ve given any IP addresses, record those as well. My advice is to check for IP conflicts caused by new devices joining the network.

Another approach is to execute "arp /a" (Address Resolution Protocol) to examine cached addresses.

For reference: https://learn.microsoft.com/en-us/window...mmands/arp
X
xShaay
09-18-2023, 12:47 AM #2

It was about modifying settings on my TP-link WiFi router as an access point connected to the main router. Did you perform a factory reset on either the primary router or the TP-Link device? Possibly both. What adjustments were made? Focus on any modifications related to static IP assignments, subnet configurations, MAC addresses, and network-specific settings.

I recommend verifying that DHCP is turned off on the TP-Link WiFi router. In many small networks, only one device should be handling IP address requests.

Count the number of network devices present: wired, wireless, DHCP-managed IPs, and static IPs.

Run "ipconfig /all" through the Command Prompt on your main computer and also on a device connected via the AP. Note the complete outputs from both executions, labeling them by the respective machines.

If you’ve given any IP addresses, record those as well. My advice is to check for IP conflicts caused by new devices joining the network.

Another approach is to execute "arp /a" (Address Resolution Protocol) to examine cached addresses.

For reference: https://learn.microsoft.com/en-us/window...mmands/arp

M
mumustrak
Senior Member
729
09-18-2023, 01:25 AM
#3
Besides the existing verification that the ip address used by the tplink is not identical to the aurora router, if both share the same address such as 192.168.1.1 you will encounter unusual outcomes. In this case, you must modify the IP on the AP.
M
mumustrak
09-18-2023, 01:25 AM #3

Besides the existing verification that the ip address used by the tplink is not identical to the aurora router, if both share the same address such as 192.168.1.1 you will encounter unusual outcomes. In this case, you must modify the IP on the AP.

M
mistercraft77
Posting Freak
900
09-19-2023, 12:11 AM
#4
TP-link isn't being used... I'm removing it.
R11 is set to 100MB while my other Dell device connects to the same cable at 1GB.
I've removed Killer App, deleted and reinstalled drivers.
Upload/download speed tests confirm the connection speed on both PCs.
M
mistercraft77
09-19-2023, 12:11 AM #4

TP-link isn't being used... I'm removing it.
R11 is set to 100MB while my other Dell device connects to the same cable at 1GB.
I've removed Killer App, deleted and reinstalled drivers.
Upload/download speed tests confirm the connection speed on both PCs.

J
jrobbs7
Member
235
09-21-2023, 04:57 PM
#5
Cat cables details: specifications, maker(s), origin?
Every cable must meet Cat 5e or 6a standards, be round, UTP, made of copper, with 22-24 AWG size.
Avoid flat designs, aluminum construction, or thinner materials. No bends, twists, pinches, sharp turns, or tangles with other wires. Ensure no signs of damage or corrosion.
Inspect the plug connections carefully—they might be loose or cause issues.
Router logs (if present and accessible) could offer useful hints.
Identify who has complete administrative rights on the router; assistance will be required from that individual.
J
jrobbs7
09-21-2023, 04:57 PM #5

Cat cables details: specifications, maker(s), origin?
Every cable must meet Cat 5e or 6a standards, be round, UTP, made of copper, with 22-24 AWG size.
Avoid flat designs, aluminum construction, or thinner materials. No bends, twists, pinches, sharp turns, or tangles with other wires. Ensure no signs of damage or corrosion.
Inspect the plug connections carefully—they might be loose or cause issues.
Router logs (if present and accessible) could offer useful hints.
Identify who has complete administrative rights on the router; assistance will be required from that individual.

I
ItsDysania2
Junior Member
22
09-21-2023, 11:41 PM
#6
Unless you forced the speed to 100 in the setting this is almost always a bad cable. The problem with bad cables is they work in some machines and not others.
You need to try a different cable. If that one also runs at 100mbps then you start to suspect damage to the port in the machine which is extremely rare.
I
ItsDysania2
09-21-2023, 11:41 PM #6

Unless you forced the speed to 100 in the setting this is almost always a bad cable. The problem with bad cables is they work in some machines and not others.
You need to try a different cable. If that one also runs at 100mbps then you start to suspect damage to the port in the machine which is extremely rare.

D
DerpyKookie_MC
Junior Member
13
09-22-2023, 03:34 AM
#7
Disconnection and performance problems with the Killer E3000 were frequent even prior to Intel's acquisition. It's generally recommended to avoid using the Killer drivers and instead let Windowsupdate install the Realtek RTL8125BG(S) drivers, which are based on the actual hardware behind that collection of unreliable "gaming optimization" software.
D
DerpyKookie_MC
09-22-2023, 03:34 AM #7

Disconnection and performance problems with the Killer E3000 were frequent even prior to Intel's acquisition. It's generally recommended to avoid using the Killer drivers and instead let Windowsupdate install the Realtek RTL8125BG(S) drivers, which are based on the actual hardware behind that collection of unreliable "gaming optimization" software.