[SOLVED] Network card isn't connecting properly

[sparksleeve]

So, I've been dealing with this issue for maybe 2 months, and I thought it was about time I ask for help here. Honestly not sure whether this is a hardware or a software issue, so I made a random guess for categories.

Short while back, I bought a Cudy AX5400 network card to solve some Bluetooth issues caused by my old USB adapter. Tried installing it in a full sized PCIE port, found it wasn't producing a signal. Tried reinstalling it in a different port via an extender cable, that didn't seem to work either. Tried installing and reinstalling the recommended drivers (intel) to see if that was the issue. No such luck.

Then I found out that it is technically working. I can at least find it via the device manager.. I think. Honestly a bit difficult to tell if that's it or not since it's not listed by any sort of name. Just "bluetooth device". Tried deleting and disabling that, with no changes. But I have discovered that it is producing a bluetooth signal at least. It's just not picking up any devices I test with it.. except when I tried it with an xbox controller. It picked up the signal, but it wouldn't actually connect to it properly, just "try connecting your device again."

I should also mention that it's not picking up a wifi signal whatsoever, but that's admittedly not a huge concern of mine.

So. I'm kind of at a loss at this point. Do I need to update the bios, get a new card, just move it to another slot? Any advice would be appreciated.

CPU: Intel 12 Gen i7-12700K, 3600 MHz
CPU cooler: ID-Cooling SE-214-XT
Motherboard: MSI Pro Z790-A (MS-7D25)
Ram: 32 GB of Tteam T-Force Delta DDR5 5600
SSD/HDD: 4 SSD ranging from 1 to 2 TB with another 2 TB HDD
GPU: MSI Geforce RTX 3080 TI GDDR6X
PSU: Smartbuy 1000W (from 2022)
Chassis: Corsair 4000D Airflow
OS: Windows 11
Monitor: Odyssey G8
Bios: MSI - 7E07vA9

 

[Lutfij]

Welcome to the forums, newcomer!

When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

I bought a Cudy AX5400 network card
http://www.cudytech.com/productinfo/1336021.html
Is this the card you purchased?

 

[sparksleeve]

Right. Sorry, I wasn't aware of that. I'll try to write that down in the original post when I get the chance.

And yes, that is the right card.

 

[sparksleeve]

Alright. Finally got the specs sorted out at least. I would have done so sooner, but unfortunately when I tried updating the bios in an attempt to fix things, the SSD I had my OS on was basically bricked. I had to get a replacement and then update the bios again. Been a bit of a slog. And of course that didn't actually fix my issues with the card. Oh well. Gonna try bumping this to get some fresh eyes.

 

[Ralston18]

FYI: No need to bump and doing so may get those "bumps" deleted along with a warning to stop bumping.


Do you have any extension cables for card's antennas? Purpose being to raise the antennas up and away from the back of the host computer. [Noted your mention of a "port extender cable" - that being an internal cable. Correct?}

= = = =

With respect to the networking problem more information is needed.

Make and model: Modem, Router, or Modem/Router if combined.

Doublecheck that only one network adapter (either wired or wireless) is enabled.

Run "ipconfig /all" (without quotes) via the Command Prompt and post the results here.

[Note: You should be able to copy and paste the results with no need to retype everything.]

 

[sparksleeve]

Good to know. Sorry, I wasn't aware of the etiquette.

In terms of extension cables, I was attempting to use a PCI-e to PCI Express Extension Cable. But I stopped using that when I figured out a way to fit the actual card into one of the larger slots.

Netgear Nighthawk R7400 from around 2020 I believe.

I couldn't find any evidence of there being more than one adapter enabled. Just ethernet and Bluetooth.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Tower
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Controller (3) I225-V #2
Physical Address. . . . . . . . . : D8-BB-C1-93-D8-E3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8bd9:cf9a:f759:677f%3(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.26(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, February 7, 2024 9:10:52 PM
Lease Expires . . . . . . . . . . : Thursday, February 8, 2024 9:10:52 PM
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 282639297
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2D-52-30-6E-D8-BB-C1-93-D8-E3
DNS Servers . . . . . . . . . . . : 10.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 30-05-05-EC-E6-2B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

 

[sparksleeve]

If I had to guess, I'd say that media disconnected thing is the trick to figuring this out. But I'm having difficulty finding anything that works. Currently trying these out in an attempt to fix it, but I'm having no luck.

https://www.minitool.com/news/media-disconnected-windows-10.html

Does anyone know any other good ways to fix this particular issue?

 

[sparksleeve]

Ok. So I finally fixed the issue myself. It was one of those forest for the trees situation. The answer was so simple that I didn't bother to notice. It was not in fact a software issue so much as a hardware issue. You know those little cables on a wifi card that connect to the antenna? Well, they got buried underneath the card, so I didn't even notice they were there. Turns out they popped off at some point. Or were never on to begin with.

I feel remarkably foolish.

So I guess the problem is over. I legitimately have no idea how to add the "solved" to the title. Is that something a moderator does? Is it even worth it at this point? Maybe some poor soul will find this and realize they made the same mistake.

 

[Ralston18]

No reason to feel foolish.

Many problems are caused by things (or lack "of things") that no one would expect.

Your post will be flagged as "Solved" and there is a good chance that someone reading your thread will benefit.

Thanks for the update.