unable to map OSX 10.4.2 to Windows 2003 member server

[Blake]

I am trying to map a normal SMB share to a Windows 2003 member server. I
can map to any server that was upgraded from Win2K to Win2k3 without
problem. Servers on the same domain that were fresh installed of 2003 will
not allow a connection. Nothing appears in the server event log.

When I connect to the 2k or 2k->2k3 upgrade servers I get prompted for
name/password/domain and then can connect. When I connect to a fresh
install I never get prompted - it just fails with 'bad name or password'
error without every prompting.

Any ideas?

Blake

 

[William Smith]

I am trying to map a normal SMB share to a Windows 2003 member server. I
can map to any server that was upgraded from Win2K to Win2k3 without
problem. Servers on the same domain that were fresh installed of 2003 will
not allow a connection. Nothing appears in the server event log.

When I connect to the 2k or 2k->2k3 upgrade servers I get prompted for
name/password/domain and then can connect. When I connect to a fresh
install I never get prompted - it just fails with 'bad name or password'
error without every prompting.

Hi Blake!

This is a common issue. Your server is requiring digitally signed
communications via a policy that is set this way as a default in Windows
2003. Have a look at this article on Microsoft's website
<http://support.microsoft.com/default.aspx?scid=kb;en-us;887429>. It
doesn't specifically mention Mac OS X, but it is about SMB connections
and explains what needs to be disabled on your server.

Hope this helps! bill

 

[Blake]

Bill,
Thanks for your reply. I got the feeling it was an SMB signing problem
(OS X won't support it) but I haven't been able to find the exact fix (and I
am trying to avoid simply turning off everything on our domain just to
support a small number of people). I am printing out the KB article now and
will be in touch.

Thanks again!

Blake