OS 6.2.x on Pro2?

I know this is normally not required to connect, but do you have the workgroup set on the pc's to the same as the NAS? This is under accounts->authentification on os6. Access Type should say "local users" on that same window in os6. Also, disable your virus scanner on the pc's when you are diagnosing any weird connectivity problem.

steve

My dad has a network of Mac's. Though when I was visiting him helping him get setup I had my PC with me and was getting similar failures as well.

Authentication is set to "local users" and the workgroup is "VOLUME". I don't think that really matters though...

Like I said earlier this was all working like a champ on previous OS4, so I don't think it is related to client issues (none of his macs work and my PC didn't work either). And I know similar configs work for me on current OS6.

So, I am just wondering if there was something that might not have worked properly during the upgrade process? Any analysis would be helpful.

Thanks!

The reason I like to get the workgroups all set correctly is that when you browse the network windows will show you the shares in the same workgroup automatically.

Have you tried mapping a network drive using the user credentials you set up? I only use authenticated user accounts though. Both MAC and windows will remember the user id/password so it's a one time event. Also, if you set your windows username/password to the same as what you use on the nas for a user, windows will automatically connect and not even prompt for the password.

FWIW I grepped my log.smbd and found only two entries for GUEST:

log.smbd: check_ntlm_password: Authentication for user [GUEST] -> [GUEST] FAILED with error NT_STATUS_NO_SUCH_USER
log.smbd: check_ntlm_password: Authentication for user [GUEST] -> [GUEST] FAILED with error NT_STATUS_NO_SUCH_USER

Looking at my configuration I think "guest" should have read access to most of my shares so I don't know why those errors are in my log either.

steve

Yea, the Mac does a nice job of showing when you are connected as guest or as a user. When I connect as a guess I can see all the shares, but get an error when I try to open any of them up. I've checked access and file permissions of the shares and the actual file/directory permissions on the NAS.

I think that GUEST failure is a red herring.

Unless someone has a theory or has the time to look through the logs for anything material I am going to prep to do a factory default on the device (after my backup finishes). And just see if it behaves differently with default settings.

Factory defaults appears to have resolved it. I am going to slowly start rebuilding it just in case it happens again I might be able to pinpoint the problem better.

For an apple environment I assume it is a good idea to have both SMB and AFP protocols? I notice when I do that I see three options for the NAS on the network; first is just the NAS name, second is NAS name (AFP), third is NAS name (SMB).

I would assume for an Apple network AFP would make most sense. Any idea what protocol the first name is using?

The first one is the advertisement for Time Machine (if enabled) or otherwise the advertisement of SMB for Windows.

mdgm wrote:
The first one is the advertisement for Time Machine (if enabled) or otherwise the advertisement of SMB for Windows.

Time machine not enabled. So, if I select it then it is the same as SMB?

I'm wondering, for my father's Apple network, whether is makes sense to just disable SMB all together and just let him run AFP on his network. (I can always turn it back on if I need it I suppose)

Any thoughts?

You could do that if you want. Best to just use AFP or just use SMB.

My dad works best with fewer choices... Hoping I could get it down to just one (instead of having to explain them...)

Thanks!