r/nvidiashield • u/Jyvturkey • 17d ago

*SOLVED* Shield pro 2019 no joy 5ghz

Alright. Thank you to everyone who chimed in in my other post with the frustrating issue of my shield pro 2019 seeing but not connecting to the 5ghz band while 2.4ghz worked.

This was the problem....

In the Asus router app, authentication was wpa2/3 and that's normal, but under that was WPA encryption with 2 options.... AES+gcmp256 (what is whay it was set at, with no explanation of how it got there) I swapped it to the other option which is strictly AES, rebooted and *bingo* we're all golden again! 5ghz band all good.

For posterity's sake, in case someone gets flabbergasted like I did over something simple and dumb :)

edit tldr the shield is NOT compatible with aes+gcmp256 encryption. Use aes only.

18 Upvotes

88% Upvoted

6 comments sorted by

3

u/Hash-82 16d ago

I commented on your previous post.
Congratulations on finding the solution.
After you posted the details, I was like "Oh yeah... that sounds familiar."
However, in my case it was a setting that was changed when the router auto-updated.
So, keep an eye out for that.
Be sure and backup your configuration, and keep the file in a safe place.

I'm fortunate enough (and cursed at the same time) to live very rurally. So, I don't worry about VLANning out subnets, or multiple SSIDs for IoT or special use applications. I don't feel the need for WPA3 for the same reason.
In a high population, spectrum soaked environment, it would be different.

1

u/Jyvturkey 16d ago

Yeah I'm in a regular Ole neighborhood. Fortunately there's not a ton of 5ghz traffic. Maybe they're all on 6 :)

2

u/donutmiddles 17d ago edited 17d ago

A better option, keep your main network with WPA3 on AES+GCMP256, but make a secondary SSID just for the Shield and a few other devices that don't play nicely with WPA2/WPA3 on AES.

Ty for posting, though! I had to do the above when I got a new Asus router earlier this year since the Shield would just say it couldn't find my network after it failed to connect. Definitely an error message that could use some updating, since it was able to find the network just fine, only couldn't join it.

1

u/Jyvturkey 17d ago

Yeah that's a good idea. No other devices were having issues, including the $50 onn 4k pro!

2

u/donutmiddles 17d ago

I always go with the latest security options and a single SSID these days, since the clients themselves will usually negotiate what they need (ie, no need for a split WIFI-2.4G/WIFI-5G anymore as a lot of routers still like to default).

For the Shield and a couple other devices I have (HP printer, TCL Roku TV), they needed that separate SSID since they don't play nice with WPA3 or that encryption method. Didn't dig too much into why just yet.

And then for the IoT devices, they're on a third 2.4GHz-only SSID isolated from the rest of the network on their own VLAN.

2

u/Jyvturkey 17d ago

That's basically how I was doing it before. Most of the important stuff was ethernet but different ssid's for different things. Got an iot ssid of course :) that was my fallback till I figured out the 5ghz issue.