[Samba] Solaris 10 Samba Configuration
gaiseric.vandal at gmail.com
Sun Jun 12 07:24:28 MDT 2011
What version of samba? If you have added all the latest patches you should
be at samba 3.5.x.
If a Windows machine is part of an AD domain it may be set to disable
NetBios over TCP/IP (NBT)- which would not be needed for Windows 200x type
file servers but would be needed to samba and Windows NT4.
Can you connect by explicitly providing the credentials (user name and
password) of a user with an account on the samba server?
E.g net use P: \\servername\sharename /user:someuser
E.g net use P: \\server.ip.address\sharename /user:someuser
If the above works, then have verified that at least the basic file sharing
is working. If not, it sounds like the WINS or NetBrowsing was working but
that the file share itself is not accessible.
For anonymous shares you may need to set
map to guest= bad user
to make sure an unknown user does connect as a guest.
From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org]
On Behalf Of borgiaj
Sent: Tuesday, June 07, 2011 11:04 AM
To: samba at lists.samba.org
Subject: [Samba] Solaris 10 Samba Configuration
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
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:
Sent from the Samba - General mailing list archive at Nabble.com.
To unsubscribe from this list go to the following URL and read the
More information about the samba