Changed routers (from AT&T box to Google Wifi puck). Can access web GUI, cannot access SMB share.

[XmodAlloy]

Greetings all.

I'm 100% sure this is a networking issue, but I have no idea how to fix it... I've fought with this for several hours and I've gotten some progress but now I'm stuck.

Originally, I set up my SMB share on my TrueNAS rig on an AT&T box that seemed to be really straightforward. I had an IP of 192.168.1.42 set up. I turned on network sharing on my windows machine and added a network location. All was good.

Today I'm changing over to google fiber and I installed my little round puck. It has only one LAN port on the router device and so I plugged my TrueNAS into that while I'm accessing it via wifi. Not fast, but I'd previously been connecting via wifi and it was good enough. The google box had a default DHCP pool of 192.168.86.20 through 192.168.86.250. I changed this to be 192.168.1.20 through 192.168.1.250 and now I can access the web GUI for my NAS again. However, on all of my windows machines I am getting a network timeout when I try to access the NAS. The little windows help gremlin points to an 'improperly set up router'.

Another post that sounded vaguely similar pointed to changing the subnet mask from 255.255.255.0 to 255.255.0.0. I tried that, no change so I put it back to default.

Anyone have any clues on getting access to my share again? I'm sorry for being a helpless networking noob...

Best regards,
-D

 

[Samuel Tai]

Did you change the LAN IP to 192.168.1.1, with mask 255.255.255.0?

 

[XmodAlloy]

Did you change the LAN IP to 192.168.1.1, with mask 255.255.255.0?

That's correct. The router LAN IP is changed to 192.168.1.1 at the moment.

 

[Samuel Tai]

OK, it's likely the other systems still have 192.168.86.x IPs. Just reboot them so they'll pick up IPs in the correct subnet.

 

[XmodAlloy]

Sadly no change.
I'm really thinking I should just go buy a regular router and hook it up to the fiber box. I hate having to use an android app to change 'router' settings. Sure, Google's little wifi pucks are cute and I'm sure they'd work for a household with plainly wireless devices... But I don't think they're going to work for me as there's so few settings that I can even access on them.

 

[XmodAlloy]

Okay, I replaced my router with an Asus RT-AX1800S and I'm running into the exact same issue...
There's something I'm missing here.
I can ping the NAS and get replies. I can connect to the web GUI through 192.168.1.42 and change settings and verify things... But if I type file://192.168.1.42/Primary_Storage into a browser I get "Your file could not be accessed"...

I'm pulling my hair out here.

 

[Samuel Tai]

Are you by any chance using root to authenticate to the share? This is no longer allowed for security reasons. You'll need to create a Windows account on your TrueNAS, and give it permissions to the share.

 

[XmodAlloy]

No. I'm using a username and password other than root. I am logging into the web GUI with root, but I don't even get the chance to type in my username and password for the share. It does not get to that point.

 

[XmodAlloy]

Okay, my desktop computer running windows 11 is now talking to the NAS. I don't know what I changed, but it's now talking. But my laptop running windows 7 is still refusing to connect to the NAS. I unplugged and restarted and plugged back in just about everything half a dozen times.

Is there any quick way to get rid of all network information on windows 7 so I can set all my networks back up from scratch? I guess I can always reformat my laptop and reinstall windows 7 on it.

 

[XmodAlloy]

Okay, I typed in the \\192.168.1.42\Primary_Storage into the address for adding a network location.

I've still got a dead ghost of TRUENAS network location, but it's working!

 

[CT117]

I've had a similar issue on windows 10. no change of networking setup though. not sure exactly when the issue began because it was letting me access it via my mapped network drive, but my backup software couldn't get access. going directly to the "Primary_Storage" directory did work, but if I tried accessing via "Network > NAS > storage Directory" it wouldn't let me in at all. not sure why "Primary_Storage" doesn't show up under that route.

At a wild guess, I set up something wrong with the account I use to access the Samba share or something. Windows network troubleshooter would fail to run immediately. I'm very much a newbie when it comes to operating this NAS.