Mac filesharing from 2003 DC

  • Thread starter Thread starter Mark N.
  • Start date Start date
M

Mark N.

Is it just me and something I'm doing wrong, or is filesharing for Mac
tightly controlled on a 2003 DC? I have a 2000 server (not a DC) in the
same test AD and can easily share for a Macintosh, but although my Mac can
see the DC, it won't let me login or see the share - although I can see it
with my 2000 Pro test machine.

Thanks,
Mark
 
Mark N. said:
Is it just me and something I'm doing wrong, or is filesharing for Mac
tightly controlled on a 2003 DC? I have a 2000 server (not a DC) in the
same test AD and can easily share for a Macintosh, but although my Mac can
see the DC, it won't let me login or see the share - although I can see it
with my 2000 Pro test machine.

Thanks,
Mark
Click to expand...

I have not had much of a chance to play around with 2003, have one on
the way though. I am having growing problems with Mac users and shares
on Windows Servers however. The AppleShare protocol that Microsoft
provides limits the character length of file names and becomes a serious
problem with OS X Users that seem to want to write novels for file names.
The current OS X Clients will all do SMB and should be able to get to
the shares that way as long as you can get the Mac Users not to use
illegal characters in the file names.
Depending on how many Macs you have get an OS X Server and put it in
Active Directory, or get the users to change their habits
Is port 548 accessible for the Mac clients to get to the server? Can you
connect over smb from the Mac? Did you install the Mac UAM client? The
default Mac authentication over afp to 2000 Servers is clear text
passwords, I would definitely assume that is not allowed with Server 2003
 
I have not had much of a chance to play around with 2003, have one on
the way though. I am having growing problems with Mac users and shares
on Windows Servers however. The AppleShare protocol that Microsoft
provides limits the character length of file names and becomes a serious
problem with OS X Users that seem to want to write novels for file names.
The current OS X Clients will all do SMB and should be able to get to
the shares that way as long as you can get the Mac Users not to use
illegal characters in the file names.
Depending on how many Macs you have get an OS X Server and put it in
Active Directory, or get the users to change their habits
Is port 548 accessible for the Mac clients to get to the server? Can you
connect over smb from the Mac? Did you install the Mac UAM client? The
default Mac authentication over afp to 2000 Servers is clear text
passwords, I would definitely assume that is not allowed with Server 2003
Click to expand...



We've never had an issue with OS X and Win2K Servers, but AD is introducing
some new issues, that's for sure. Is the Mac UAM client the same thing as
what comes built-in with 10.3.5? We tried "binding" the Mac to AD, whatever
that does??

Thanks,

Mark
 
Back
Top