Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Set Windows Server 2003 to allow Mac connections' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Set Windows Server 2003 to allow Mac connections
Authored by: senor_rudy on Dec 05, '06 09:50:00PM

After reading Vista's EULA, I ordered a macbookpro. I've been playing with RH & Debian based distros for years, now I plan to stick with a *nix OS. Bash is my friend. Tiger is impressive and FAST! XP runs faster on Parallels than on a new Dell laptop. (I administer a medium size 2003 AD domain and need the XP mmc tools on my laptop).

One disappointment with Mac is the 2003 share smb access. I can't believe this has not been corrected by Apple. It appears I will have to change the domain security policies to allow the mac to connect to my 2003 servers.

I have successfully configured FC5 and Centos4 to use winbind and kerberos AD authentication. When using a login that is AD authenticated (FC or Centos), I can access my 2003 servers. Tiger's bash command line can access the servers also by using smbclient. What gives? If FC and RH can do it, why can't Apple? The fact these types of posts go back to 2004 leaves me confused. This is a big deal in my book. Until someone creates a directory better than AD (and as easy to administer), interoperability with samba is critical. If another solution besides a commercial smb OS X client is known, please post. I don't want to change the existing security policies in AD unless absolutely necessary.

Thanks for any advice,

Ryan - brand new Mac rookie.

[ Reply to This | # ]