Help, I am having a terrible time configuring Samba on a Solaris 10 server. Seems like I did this years ago with a Solaris 2.6 server and it was nothing to configure.
Basically, I have a Solaris 10 U9 server that I'm trying to configure with one filesystem as a public file share. I am trying to connect to it from a Windows 2003 R2 server. I can see the server when I connect to \\SERVERNAME and I can even see the shares. When I attempt to access the shares from the Windows browser, it tells me: \\SERVERNAME\SHARENAME is not accessible. You might now have permission to use this network resource. The specifed network name is no longer available. Now, I have all the public permissions set in the smb.conf file to leave it open that I can think of. I've open UNIX perms wide on the directory (777) recursively just to make sure I'm covered in that respect, just to prove a concept. Still not working. All of the samples of connecting up a Windows server to a Samba server have such a simple configuration. There's got to be something stupid I'm missing somewhere. I'm wondering if the reason is that the Windows server I'm connecting from is part of an Active Directory domain. Still and all, it seems that if I have it open to the public, it should just work regardless of how the Windows server is configured. Has anyone had any experience with this? -- View this message in context: http://samba.2283325.n4.nabble.com/Solaris-10-Samba-Configuration-tp3579881p3579881.html Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
