10.4 is horrifically ancient - you could migrate the Mac to 10.5 but even that isn't getting security updates/patches anymore. If it's inserting AFP then something is wrong with the client machine. That should not happen - not normally - ever, at all. It's a less than ideal situation but there it is.Įxtreme ZIP is an excellent product especially if you have an established Microsoft server environment, and want to provide an excellent fileserver experience to your Mac clients.Īs for the OP, " on the mac, OSx substitutes "AFP://SMB://ServerName/Share" for "SMB://ServerName/Share".
#Mac connect to windows share code
So it's not up to Apple and no they're not going to make their private code (necessary modifications in the form of tie-ins for authentication) publicly available as required by the license anymore than Microsoft would do so - in other words, never going to happen. The glaring difference with Apple being that they are a particularly huge and visible company. smb:// followed by the name of the server you are connecting to. So until that time, save your would-be schadenfreude, and instead see if you can realize the hard fact that - just like you and me - Apple has to abide by the licensing terms (of GPLv3) for Samba. Select Connect to Server Enter the address of the network share Windows network shares use the Server Message Block protocol and therefore begin with. :)Īnd if you can go convince Samba to revoke, reverse or give up their use of GPLv3, go right ahead.
#Mac connect to windows share upgrade
Or the better method would be to upgrade OS X so you're not dealing with an 8 year old client operating system trying to connect to a 5 year old server operating system. Microsoft network server: Digitally sign communications (if client agrees) Microsoft network server: Digitally sign communications (always) I don't know for sure, but OS X 10.4 may only have support for SMB 1.0.Ĭomputer Configuration -> Policies -> Windows Settings -> Security Settings -> LocalPolicies -> Security Windows Server 2008 will default to SMB 2.0. Since you have Server 2008 and OS X 10.4.11, my guess is Server 2008 is asking for a higher level of security than 10.4.11 supports. Also, I haven't had any issues accessing Windows servers in Lion or Mountain Lion so I wouldn't put too much stock in that route either.
Eric specifically said the client is 10.4.11, so everything posted by Galen about Lion and Mountain Lion can be ignored.
0 kommentar(er)
