Problems mounting ReadyNAS shares from a Windows 7 AD client

Hola!

Seems like there's an active community over here, but unfortunately I still couldn't find an answer for my question.

I'm running a ReadyNAS Pro 4 with RAIDiator 4.2.22. The NAS box is not connected to AD, but is running stand alone. Everything works great from our AD connected XP computers, but AD connected Windows 7 (64-bit) computers seem to be running into trouble.

Here's what I try to do:

net use n: \\NAS\test /user:"NAS\username" Enter the password for 'NAS\username' to connect to 'NAS': System error 64 has occurred. The specified network name is no longer available.

And here's what I get from the logs:

[2012/10/03 07:44:35.185290, 2] auth/auth.c:304(check_ntlm_password) check_ntlm_password: authentication for user [XXX] -> [XXX] -> [XXX] succeeded [2012/10/03 07:44:35.198068, 0] lib/util_sock.c:474(read_fd_with_timeout) [2012/10/03 07:44:35.198303, 0] lib/util_sock.c:1441(get_peer_addr_internal) getpeername failed. Error was Transport endpoint is not connected read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by peer.

So far I've figured out, that it seems like there's a mismatch in what my client (getting it's settings from AD policies) expects from the ReadyNAS box.

I've tried few options based on the suggestions found from the net and from experience.

This is what I've added to the smb.conf, but I still get the same message:

client NTLMv2 auth = yes client lanman auth = yes lanman auth = yes ntlm auth = yes client signing = mandatory

I have a hunch, that the problem lies in the client signing (or as the Windows knows it: "Digitally sign communications") setting - am I on the right track?

Of course, there's a catch - policies on the workstations can't be altered - nor the ReadyNAS added to the same AD environment than the workstations.

Is there a way to make this work with these restrictions?