RNDP 6000 seems to be short circuiting my UPS
@KenTanker0us1 wrote:
re: SMBv3
I am on Win7. My small amount of research tells me SMBv3 is not native to Win7. Does that mean the new NAS is not using it?
Your new NAS is advertising SMBv1, SMBv2, SMBv2.1, and SMBv3. Win7 will use SMBv2.1.
@KenTanker0us1 wrote:
re: guest access
When you say I've been using guest access, does that refer to only the new NAS or to the old NAS as well? What about the rest of my network? Do I need to change everything?
If you aren't using NAS account credentials (admin or some other account) when you access the shares, then you are using guest. That would be true on both NAS.
@KenTanker0us1 wrote:
For instance, if I set the Workgroup name to my workgroup, plugged in my name and password, would that allow me to sidestep having to make the credentials, etc? And would that be a bad idea?
The workgroup should be set to your workgroup name in any event - if it's not, then that could explain your access issues. Though the "groups" that you see when you enter a new account are linux groups. These are not the same as a workgroup, so they doesn't need to match anything on the PC. The idea of the linux group is to enable convenient access to classes of users - for instance, you can set up a share so all members of the marketing group have access to the marketing shares, without having to explicitly set up access for each person in marketing.
Creating accounts on the NAS that match your Windows logons is an alternative to the credential manager, so you can do that instead. Using NAS accounts would allow you to tailor access per user later on if you wanted to do that. The only downside is that accessing the full data volume can only be done with the NAS admin account.
Normal behavior with SMB (at least pre-WannaCry) is as follows:
If there are no credentials for the NAS in the credential manager, then Windows will use your windows logon credentials.
If there is no corresponding account on the NAS, then the NAS will treat that as guest access (though that might change in future releases). This is where Microsoft is tightening up it's behavior.
If there is a corresponding account on the NAS, then the access will fail if the password doesn't match (even if guest access is enabled).
If the logon is rejected by the NAS, then you are prompted for username/password. There are some cases where that username/password won't be accepted by windows, even if it is a valid NAS account. (From my point of view those are bugs in Windows).
@KenTanker0us1 wrote:
re: speed of backup and network pairing
I have 2 network cables plugged into the new NAS, just like I have on the old one. On the old I can set pairing but I don't see where I can to it in the new one. In the (new) network tab, all 4 network plugs are listed. The 2 that I'm plugged in to are listed with different IP addresses.
1. Is this paired? Is it slowing down the backup?
2. If I use your command line test which IP address would I use?
They are not paired, and I suggest disconnecting the second NIC for now and retrying accessing the NAS. When that works, then try setting up the bond again. It's possible that the NAS reponse to those commands is being sent on the other IP address, and that will create problems.
The way to set up a bond is to click on the settings wheel next to one of the adapters. You'll see a "new bond" choice.
The options are the same as your older NAS. Which options you can use depend on what switch/router you are using. If you provide that information, I can go into more details.
@KenTanker0us1 wrote:
2. I'm still not clear on the guest access. I'm using admin with my own NAS password to log in to the Admin Page in my browser, so that's not guest, right? If I try and access the shares through my Network, I don't have access whether I type in my browser admin logon or my Windows logon. Neither of these is Guest (it seems to me), so that's confusing
I've already tried to explain this. Right now when you use your windows logon, the NAS offers guest access because there is no corresponding user account on the NAS. That is failing with the new NAS, and that is part of the issue we are trying to fix.
admin is also failing, and we have no explanation for that.
One more setup question though - can you look at your share setting (network access tab, SMB, Advanced), and check the SMB3 transport encryption setting? Make sure it is not set to "required".
@KenTanker0us1 wrote:
3. I like the idea of creating an account on the NAS as an alternative to the credential manager but I'm not sure how to do it in the Admin Page. In the Accounts tab/Authentication section, I have entered the name of my workgroup but it didn't change the access issue. In that section are 2 choices for Access Type: Local Users and Active Directory. I can't type in my Windows name and password if the type is set to Local Users. If I set it to Active Directory, I can enter that info but I'm not sure what to put in the other fields.
You don't have an Active Directory server on your network, so you need to use "local users"
Are you saying that if you do that, you can't enter your windows username in the Name field, and your windows password in the Password/Re-enter Password fields? What error do you get when you try to do that?
@KenTanker0us1 wrote:
4. Re: pairing: I see how to do the pairing now, thank you. Per your recommendation I disconnected the second NIC but it didn't make any difference; I still don't have access through Windows, only through the browser Admin Page.
My older NAS is paired and using Transmit Load Balancing. Is that best?
With those switches (which are unmanaged), your only choices are transmit load balancing (TLB) and adaptive load balancing (ALB). TLB will increase total download speed (across all users) when there are multiple users, but obviously it can't go over one gigabit when there is only one user (even if that user is another NAS using TLB). It won't help total upload speed at all..
ALB does attempt to balance both upload and download speed across all users, but again it can't increase the single user speed. ALB sometimes can cause your network to misbehave, so if you see connectivity issues using it, the simplest thing to do is to turn it off.
If you often have multiple users accessing the NAS at the same time, then these modes can be handy. For most home users they don't help much (if at all).
The most robust way to max performance with an RN500 or RN600 ReadyNAS is to connect it to a switch that has 10Gbase-t ports, and also connect all your wired devices to that same switch. The cheapest option right now is the GS110MX (8 gigabit ports, and two ports can go to 10 gigabit). It's still fairly expensive ($200), but much cheaper than full 10gbase-t switches (Netgear's 8 port XS508M is ~$500).
If you still need a satellite switch, you could get a second GS110MX, and connect it to the first using 10 gigabit. Then you'd still get max multi-user performance over ethernet.
