Windows client can’t connect to share

[foilpan]

This is strange.

The lone Windows user in a client’s office can’t connect to the freshly rebuilt OS X 10.4.2 server.

The shares he needs are available and shared via SMB.

He has a valid username and password, yet I can’t map drives from his desktop unless I use the OS X Administrator username and password.

What am I doing wrong here?

Thanks.

[foilpan]

Oh, and since the server’s set up as a standalone, I can’t give this user an open Directory password. He just has the standard crypt password. Could this be the problem? If so, why doesn’t the admin user have the same problem?

[foilpan]

Update:

All the DNS issues seem to be resolved. Before, I couldn’t do reverse lookups on the server, but that’s all working now.

Attempts to connect to the smb shares are now met with “NT_STATUS_WRONG_PASSWORD” errors, even for freshly created users.

The server’s configured as an OD master, but I don’t have the ability to assign users OD passwords. My only options are crypt or shadow.

Password server looks like it’s finally running, but is it possible that smbd isn’t communicating with it to authenticate users?

Anybody, anybody?

[Author]

Posts