fugumagu

I checked the Belkin router and it does not appear to have bridge mode, only access point mode. I plugged the switch upstream of the access point router and plugged the upstairs computer into the switch. That definitely fixed the issue. Not sure if the access point was causing the double NAT or what but I'd be interested in seeing a newer router with bridge mode works. I'm thankful for your help!

Yeah, that's pretty much me. I saw something online somewhere that said something to the effect of "Did you know you can use your old router as an access point and boost your WiFi?". I thought, sweet, I have an old one laying around. I got it working and everything was great! I'm definitely new to/inexperienced in all of the above (Unraid, servers, and Linux) but am learning a lot so far just by getting my hands dirty and trying things out. I think the next step is for me to budget for some new network hardware for sure since I'm working with oldish stuff.

Thanks for the advice! From the computer behind the access point, I am able to successfully ping the Unraid server and any other computer upstream from the access point. I am just now looking up the date for the access point router and it is quite old. I wouldn't be surprised if it was just too old but I really have no clue where to start looking if it is or not. Best thing I could do is just get another router that is the same as the main router or even do what you're recommending and check out the Ubiquiti option. I'm definitely getting good information on this and am gratful for your input!

I might actually just do this since I have a spare 5 port Gb switch lying around.

I wouldn't be surprised if it was my setup since I'm nowhere near an expert in networking. I have a standalone modem going to a standalone wireless router (TP Link Archer A10). The router doesn't have modem functionality at all. I have an ethernet cable going upstairs where I have it plugged into another wireless router (an old Belkin N600 router, not a modem combo device) and it is running in Access Point mode. I actually just looked up the date the Belkin router came out; it's about a decade old. Might be the cause. My entire awareness of Unraid's existence is only a couple weeks old, so I'm still figuring it out. I only tried to access the server from upstairs yesterday when I noticed the issue. I'm not sure if the router being used as an access point is compatible with the main router or if it is in bridge mode. However, knowing that compatibility and bridge mode is "a thing" is hugely helpful and gives me a direction in which I can do more research and learning. I might take Frank1940's advice above and use a Gb switch to solve this. Or get an up-to-date router. Or just not worry about accessing the server via it's host name from upstairs.

First, I'm very new to Unraid, so apologies in advance if this is a dumb question. TLDR: I can't access Unraid shares via the host name while on a computer behind an access point. Accessing other computer shares on the network and accessing Unraid via the IP address all work fine from a computer behind an access point. I have a router set up in access point mode to improve WiFi signal upstairs. This router is connected to my main router via ethernet cable. My Unraid server is also connected to the main router via ethernet cable. While on a Windows 10 computer connected to the main router, I have no issues connecting to Unraid under the Network list in File Explorer; I can see \\Tower and open the shares just fine. However, while on an upstairs computer connected to the access point, I can see \\Tower in File Explorer but cannot open it. I get the "Windows cannot access \\Tower. Check the spelling of the name..." error (0x80070035). I am able to type the IP address into File Explorer and access the shares this way though. I can also click on the computer name of any of the other computers in the Network list and access those shared files just fine. If I bypass the access point and plug the upstairs computer directly into the ethernet cable that was previously plugged into the access point, I am now able to click on \\Tower and open the shares. It fixes the issue. Is this normal operation? Can I make it so I can click on \\Tower and open the shares from a computer on the access point? I've searched through the forum and tried the following on the machine behind the access point: Turning on SMB 1.0 in Windows Features Enabling insecure guest logons via Local Group Policy Editor > Computer Configuration > Administrative Templates > Network > Lanman Workstation Enabling NetBIOS over TCP/IP via Ethernet > Properties > Internet Procol Version 4 (TCP/IPv4) Properties > Advanced > WINS tab Enabling SMB 2.0 in Powershell with the "Set-SmbServerConfiguration -EnableSMB2Protocol $true" command None of the above steps have fixed the issue.