Am trying to connect a new Mac to a Win2003 file server.
- Server has File & Print services for Mac running as well as AppleTalk
protocol installed
- Mac user is setup in AD same as Mac logon
- Folder is shared on server and is an NTFS volume.
- Server help says to add "Apple Mactonish Users" to the share permissions
but that does not show uo as a choice.
- User is trying to logon using: smb://server/share
- I've downloaded UAM (User Authentication Module) for OSX 10.1 or later as
referenced in mactopedia. It is MSUAM.forX.sit. How is this installed on a
MAC?
Any and all help appreciated... Thank you!
> Am trying to connect a new Mac to a Win2003 file server.
> - Server has File & Print services for Mac running as well as AppleTalk
[quoted text clipped - 9 lines]
>
> Any and all help appreciated... Thank you!
Leithiser -
You're mixing two very different communications technologies here. If
you want to access the information on the server using AppleTalk, you
need to use the afp://server/macshare syntax. If you use the
smb://server/share syntax, you're bypassing AppleShare altogether.
Here are a couple of posts that might help you resolve your connectivity
issues. Though the posts reference the Small Business Server product,
the steps work the same for standard Windows 2003 as well.
http://simultaneouspancakes.com/Lessons/2004/12/29/connecting-a-macintosh-to-sbs
-using-appletalk/
http://simultaneouspancakes.com/Lessons/2004/12/28/connecting-a-macintosh-to-sbs
-2003-server-via-smb/
HTH...
-Eriq

Signature
Eriq Neale - SBS MVP, Small Business Specialist, MCSE, Mac Guy
EON Consulting - www.eonconsulting.net
Author of Microsoft Small Business Server 2003 Unleashed
Listen to the eOnCall Radio broadcast at Airtunz
(www.airtunz.com) or hear past episodes at www.eoncall.com
> Am trying to connect a new Mac to a Win2003 file server.
What version of OS X?
Is the 2K3 server a simple file server, or an Active Directory server?
> - Server has File & Print services for Mac running as well as AppleTalk
> protocol installed
Not needed, for straight TCP/IP connections.
> - Mac user is setup in AD same as Mac logon
Cool
> - Folder is shared on server and is an NTFS volume.
Good
> - Server help says to add "Apple Mactonish Users" to the share permissions
> but that does not show uo as a choice.
If you have the user in AD already and have them or their security
group added to the share permissions, that's all you should need, as
long as security permissions don't exclude them.
> - User is trying to logon using: smb://server/share
In other words, Command+K, right?
You should get a pop up with the Domain, Username and Password fields,
are you?
If the user is typing in the correct pw, what, if any, error message
are you seeing?
> - I've downloaded UAM (User Authentication Module) for OSX 10.1 or later as
> referenced in mactopedia. It is MSUAM.forX.sit. How is this installed on a
> MAC?
Again, don't believe it's necessary, as long as you're not dealing with
shares on an AD server.
> Any and all help appreciated... Thank you!
Please post back with the answers to the questions above, if you
haven't solved your problem already.
Cheers!

Signature
Poindexter M.S.
n00by - 22 Aug 2007 17:36 GMT
> > Am trying to connect a new Mac to a Win2003 file server.
<snip>
> Is the 2K3 server a simple file server, or an Active Directory server?
ya git! it's in hte bloody subject :^\
<snip>
> Please post back with the answers to the questions above, if you
> haven't solved your problem already.
betcha its the dc security policy. it my connexion to an ad server
thru the admin share was borked after promoting a member server to ad
role.
if yer getting an message like "username or password is incorrect" even
when ya know they're right, you're a candidate for this fix.
if ya have the service pack and all updates installed its like this:
"Configure security settings to allow SMB connections:
1. Allow unencrypted connections in the Default Domain Controller and
Default Domain Group Policies: [Active Directory Users and Computers]
In the Default Domain Controller Policy \ Computer Configuration \
Windows Settings \ Security Settings \ Local Policies \ Security
Options, find ³Microsoft network server: Digitally sign communications
(always)² and ³Microsoft network server: Digitally sign communications
(if client agrees)². Define both of these policies as ³Disabled²:"
http://weblog.bignerdranch.com/?p=6
in my case i had to set the dc to allow lm and ntlm responses, with
ntlm2 preferred, as well (tho' this is *not* preferred for security
reasons
http://www.windowsecurity.com/articles/Protect-Weak-Authentication-Proto
cols-Passwords.html )
hth

Signature
nooby