1133 Views 5 Replies Latest reply: Jul 16, 2007 8:08 AM by Brian Swanson3
Do they both have the Microsoft network client: Digitally sign communications disabled?
I am having the exact same problem ( Alias error with network attach and then name or password error with SMB) on our main fileserver.
Here is the rub, I have no problem authenticating either way againest our WS2K3 server that is used as an FTP server to the outside (it is a network share point internally).
We have 3 servers (all running WS2K3 R2), one is our DC (runs a number of none user facing services as well as exchange), the second is our file and print server (this is the one I can't get to from our Macs), the third is a our FTP server. They are all in the same AD tree and all authentication is done through the DC.
I have made the changes to AD security policies and configured Directory Access on our Macs.
Why would one server have no problems while the other won't work at all?
Is there a secret setting on the server that needs to be set?
Do I have to restart my server to flush the AD changes (never seemed to have to do that in the past)?
PB G4 1Ghz 1G RAM 80G HD Mac OS X (10.4.6)
Ok I have finally got it working (I got it working last week, this is not a high priority project). This the best resource I found for getting it all working:
The one problem that I ran into and have not resolved is the registry change resets back to the default after WS2K3 updater runs security patches (but only on the server we use for file sharing...the others are fine). Very annoying.
I will look into a way to make this stick and report back.