I have enabled Windows File Sharing in the preferences, but, when I try to enable my user account, it tells me I have the incorrect pswd. Any ideas? Is the pswd stored separately?
Update...I read the help sections and articles. It appears that I should be using my Mac user account pswd, which I am. However, I am still being rejected by Win Sharing.
I have a WINs dir set-up in Directory Access. Could this effect anything?
My Dir Access WINS info is set for my work's domain. Still no luck though.
The issue arose when I was attempting to create a peer-to-peer wireless network to share some files btwn a friends PC and my Mac. All was well until I tried to enable Windows sharing. In this instance, there was no pre-existing domain. Any thoughts?
.....The issue arose when I was attempting to create a peer-to-peer wireless network to share some files btwn a friends PC and my Mac. All was well until I tried to enable Windows sharing. In this instance, there was no pre-existing domain. Any thoughts?
i have been able to do this 8)
i just made sure to name a workgroup eg "RWORKGROUP" and leave the WINS blank.
then create a computer-to-computer network on the Mac, then the PC was able to log on wirelessly and vice versa
well, beyond this my windoze network knowledge is crap, so good luck \
As far as I know (and I could be wrong), the Samba server acts just like another user on the machine. If you're sharing your home directory, the Samba user cannot access it as it does not have enough permissions to do so (UNIX permissions are blocking the access). And if the Samba user cannot access it, the Samba server cannot share it to someone else. Try sharing a directory that is shared globally (think chmod 777).
Further, there is an extra layer of permissions to deal with. Even if your UNIX permissions are set such that Samba can access the files, you can still have Samba configured to block certain access. Note however, if Samba cannot access the file in the first place (via UNIX), nothing you do at the Samba level can give you the requisite permissions.
As far as I know (and I could be wrong), the Samba server acts just like another user on the machine. If you're sharing your home directory, the Samba user cannot access it as it does not have enough permissions to do so (UNIX permissions are blocking the access). And if the Samba user cannot access it, the Samba server cannot share it to someone else. Try sharing a directory that is shared globally (think chmod 777).
Further, there is an extra layer of permissions to deal with. Even if your UNIX permissions are set such that Samba can access the files, you can still have Samba configured to block certain access. Note however, if Samba cannot access the file in the first place (via UNIX), nothing you do at the Samba level can give you the requisite permissions.
Hope that makes sense...
i think if one is enabling sharing SMB on the Mac side, by default your Public folder is shared (eg. users/sunil/public) IIRC - that's the default chmod'ed 777 folder
I should add that you might not want chmod 777 if you don't want write access from Samba. But, remember that there's an extra layer of protection from Samba. So, you can have UNIX writable (777), but the Samba daemon can still refuse external users write permission. Always good to protect your files at all levels though, so think carefully before chmod 777, even if Samba is set to disallow write.
Tiger ACLs add finer grain permissions, but I haven't had the time to read up about them yet. For now, what I just said is common to all UNIX platforms.
I should add that you might not want chmod 777 if you don't want write access from Samba. But, remember that there's an extra layer of protection from Samba. So, you can have UNIX writable (777), but the Samba daemon can still refuse external users write permission. Always good to protect your files at all levels though, so think carefully before chmod 777, even if Samba is set to disallow write.
Tiger ACLs add finer grain permissions, but I haven't had the time to read up about them yet. For now, what I just said is common to all UNIX platforms.
cool... let us know if you have any further details on Tiger setting permissions beyond chmod 777, that is, how would the samba daemon refuse write permission.... intriguing stuff
Comments
I have a WINs dir set-up in Directory Access. Could this effect anything?
.......
i only know for workgroups,
on mac os x
i go to directory access,
click on SMB/CIFS
click on configure...
i make sure the workgroup name is exactly the same as the workgroup i assigned my win2000 machine to.
similarly, i assume wins should be set to exactly the same on the mac directory access as your win2000 machine
My Dir Access WINS info is set for my work's domain. Still no luck though.
The issue arose when I was attempting to create a peer-to-peer wireless network to share some files btwn a friends PC and my Mac. All was well until I tried to enable Windows sharing. In this instance, there was no pre-existing domain. Any thoughts?
Originally posted by Keda
.....The issue arose when I was attempting to create a peer-to-peer wireless network to share some files btwn a friends PC and my Mac. All was well until I tried to enable Windows sharing. In this instance, there was no pre-existing domain. Any thoughts?
i have been able to do this 8)
i just made sure to name a workgroup eg "RWORKGROUP" and leave the WINS blank.
then create a computer-to-computer network on the Mac, then the PC was able to log on wirelessly and vice versa
well, beyond this my windoze network knowledge is crap, so good luck
Further, there is an extra layer of permissions to deal with. Even if your UNIX permissions are set such that Samba can access the files, you can still have Samba configured to block certain access. Note however, if Samba cannot access the file in the first place (via UNIX), nothing you do at the Samba level can give you the requisite permissions.
Hope that makes sense...
Originally posted by drumsticks
As far as I know (and I could be wrong), the Samba server acts just like another user on the machine. If you're sharing your home directory, the Samba user cannot access it as it does not have enough permissions to do so (UNIX permissions are blocking the access). And if the Samba user cannot access it, the Samba server cannot share it to someone else. Try sharing a directory that is shared globally (think chmod 777).
Further, there is an extra layer of permissions to deal with. Even if your UNIX permissions are set such that Samba can access the files, you can still have Samba configured to block certain access. Note however, if Samba cannot access the file in the first place (via UNIX), nothing you do at the Samba level can give you the requisite permissions.
Hope that makes sense...
i think if one is enabling sharing SMB on the Mac side, by default your Public folder is shared (eg. users/sunil/public) IIRC - that's the default chmod'ed 777 folder
Tiger ACLs add finer grain permissions, but I haven't had the time to read up about them yet. For now, what I just said is common to all UNIX platforms.
Originally posted by drumsticks
I should add that you might not want chmod 777 if you don't want write access from Samba. But, remember that there's an extra layer of protection from Samba. So, you can have UNIX writable (777), but the Samba daemon can still refuse external users write permission. Always good to protect your files at all levels though, so think carefully before chmod 777, even if Samba is set to disallow write.
Tiger ACLs add finer grain permissions, but I haven't had the time to read up about them yet. For now, what I just said is common to all UNIX platforms.
cool... let us know if you have any further details on Tiger setting permissions beyond chmod 777, that is, how would the samba daemon refuse write permission.... intriguing stuff