[Samba] Vista error 67 The network name cannot be found
osp at aloha.com
osp at aloha.com
Thu May 13 14:13:59 MDT 2010
On 2010-05-12 05:12:12 GMT Gary Dunn <osp <at> aloha.com> wrote:
> On Fri, 2010-05-07 at 09:57 +0000, osp <at> aloha.com wrote:
> > Should I try Samba 4.0?
I had been using Samba 3.3 so I installed the 3.4 port and got the same
result. Yesterday I installed samba4. It's like a whole new ball game!
Sorry to report no improvement. I have a few notes and questions.
I had to add a "users" group to /etc/group, did not see that mentioned
anywhere. Figured it out from provision errors.
I used server role = standalone
I added my share to /usr/local/etc/smb4.conf
I added my g8team user with net newuser g8team
I can connect to the share from the console, and using smbclient on a
separate FreeBSD box. Gnome's places/network stopped working, so I
installed the samba4wins port but Gnome is still unhappy. Vista still gives
error 67 and refuses to connect.
I recommend having the provision script suggest renaming the existing
smb4.conf file instead of just giving errors as it does now. (I tried
running it several times while figuring out how it worked.)
1. Is printer sharing working? What syntax do I use in the [printers] section?
2. This is running on a nat gateway. I only want the samba service to
appear on the private network. My old smb.conf file had
hosts allow = 10.0.1. 127.
interfaces = 10.0.1.1
How do I specify this in Samba4?
Overall I rate the installation process very good for alpha software. Wiki
howto was a big help. For what I need, though, all that support for
kerberos and dns and ldap seems like overkill. Samba 3 with security =
share is all I need. Physical access to the Ethernet switch is all the
access control this application requires. A generic username and password
is as far as I want to go. I am absolutely certain that client workstations
will not be joining my domain, and I do not want to authenticate against
any other directory.
Open Slate Project
More information about the samba