Can't connect my Mac to my Windows 2003 server shares via SMB

Question

Level 1

0 points

Can't connect my Mac to my Windows 2003 server shares via SMB

Hello all

So my problem is I have my Powerbook running 10.4.7 with all the latest security updates and I cannot connect it to any shares on my Windows 2003 domain controller. Everything was working fine and I could connect to the server with no problem till about a month ago. However, I can still connect to the Windows 2000 domain controller with no problem. The error I get when trying to connect is "Could not connect to the server because the name or password is not correct". I did try clearing out my keychain, making sure all of the authentication policies on the server are correct (disabling the digitally sign commucations always policy), and I even went as far as editing a .conf file in /etc/ folder that allows for passwords to be sent without any encryption (I forget exactly what I changed but I can post that later when I get home from work) and none of this has worked. I unfortunately don't have another mac to test out connecting to the Windows 2003 server. Does anyone have any ideas of what I could do to try and get this issue resolved?

1.25Ghz 15" PowerBook G4, Mac OS X (10.4.7)

Posted on Aug 2, 2006 8:40 AM

Reply

Answer 1

Aug 2, 2006 9:20 AM in response to sardathesage

Have you tried sharing them out under AFP as well as SMB?

Also are you sure your password dosent need to be changed first. Ive come acroos this a coupel times where if your account needs to change its password via a Win Server policy and you havent done it yet it wont let you log on.

Reply

Answer 2

sardathesage Author

Level 1

0 points

Aug 2, 2006 9:35 AM in response to Anthony Cunningham

I don't know how to share them out under afp. Could you give me a brief over view or point me towards a good readme? The AD account's password is set to never expire, and like I said, it works when I connect to the Windows 2000 DC (the 2k3 and 2k are both in the same domain, 2k3 is the PDC).

Reply

Answer 3

Aug 2, 2006 5:43 PM in response to sardathesage

Have the Digital Signing requirements been turned off on the 2003 box?

Reply

Answer 4

sardathesage Author

Level 1

0 points

Aug 2, 2006 9:52 PM in response to Trevor Seward

Yes, as stated in the original post.

Reply

Answer 5

Aug 3, 2006 12:16 PM in response to sardathesage

Sorry, missed that one!

Is this Mac joined to the domain? If so, are you getting a Kerberos ticket before attempting to connect via SMB?

What is the password enforcement on the DC? NTLM & LM? You should note that "send plaintext passwords to 3rd party SMB servers" is disabled by default. There is no reason in Tiger to enable plaintext passwords.

Reply

Answer 6

sardathesage Author

Level 1

0 points

Aug 3, 2006 2:08 PM in response to Trevor Seward

The mac isn't joined to the domain. Since it isn't joined, I don't have to worry about the Kerberos ticket correct? I'm pretty sure the DC uses NTLM & LM for password enforcement, I can confirm this later. As for the plain text passwords, I found an article online (unfortunately I don't recall where I found it or even if it is from a reliable website) that said there seems to be lots of issue with password authentication with the SMB support in Tiger. The article suggested switching to plain text to see if that clears up the problem. That's why I tried it, but unfortunately it didn't work anyway.

Reply

Answer 7

Aug 3, 2006 4:14 PM in response to sardathesage

You could still aquire a Kerberos ticket, but that is extra setup that is not necessary. Instead you'll just simply use LM/NTLM/NTLMv2.

Check the level of encryption enforced on the passwords. I do know what article you're talking about, and I have no idea why it was posted...it really won't work in 90% of the cases on 2003 🙂

Reply

Answer 8

sardathesage Author

Level 1

0 points

Aug 3, 2006 6:29 PM in response to Trevor Seward

lol wish I knew that then. I did check my server and it uses NTLM & LM (not version 2 though). Also, if I just delete what I added to the .conf file, will Tiger go back to using encrypted passwords?

Aside from this, any other ideas of what I could do to get this working?

Reply

Answer 9

Aug 3, 2006 7:11 PM in response to sardathesage

TO share out as afp you need to have file and print services for macintosh installed on the 2k3 Server.

O n the main management console click on the shares icon on the left. then click the "link" create a share. The wizard will guide you through the process. i forget the order of progression but i beleive its the second or third part in the dialog it will have 2 check boxes, the top one checked by default, is to share it for windows/smb the second (lower box) is to share as AFP for mac check this box and change the share name if you like. then proceed through the rest of the wizard. Make sure you configure the security/sharing prefs for access.. we typically remove the everyone policy and add one for Authenitcated Users, and ofcourse Administrators.

Reply

Answer 10

sardathesage Author

Level 1

0 points

Aug 3, 2006 10:38 PM in response to Anthony Cunningham

Thank you so much, using AFP works! Even though this didn't actually solve my SMB issue, it's definitely a great alternate. If anyone has any ideas about the SMB issue, please let me know. I'd still like to get this fixed if possible.

Reply

Answer 11

Aug 4, 2006 8:22 AM in response to sardathesage

No problem man. I hope you get your SMB issue resolved. Im nist sure what the issue is. Ive got 3 macs her ein the office all accessing SMB and AFP shares on an SBS 2k3 server and we have no issues at all. Even before we threw down the bling for an actual server we had no problem accessing smb shares on the windows boxes (we did however have issue the other way around...). While we use afp on the mac side for nearly everything im with you on wanting to get it solved simply for solutions' sake if nothing else. Good luck!

Reply