On 1/17/2015 11:36 AM, Piece Maker wrote:
>
> venzkep;2689658 Wrote:
>>
>> Piece Maker;
<snip>
> The ping worked, the time was 2011ms which I dunno if that’s fast or
> slow. I can also ssh into my Suse machine, but it takes a LONG time to
> connect.
>
If this is the total time 2011ms is OK. If it is the time for individual responses, it’s horrid
<snip
>
>
> Code:
> --------------------
> SuSEfirewall2.service - SuSEfirewall2 phase 2
> Loaded: loaded (/usr/lib/systemd/system/SuSEfirewall2.service; enabled)
> Active: inactive (dead) since Sat 2015-01-17 05:25:22 GMT; 11h ago
> Main PID: 4602 (code=exited, status=0/SUCCESS)
> --------------------
>
>
> Seems to be off!
>
Yes
<snip>
> Code:
> --------------------
> smb.ssmb.service - Samba SMB Daemon
> Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled)
> Active: active (running) since Sat 2015-01-17 05:17:32 GMT; 12h ago
> Main PID: 9141 (smbd)
> Status: “smbd: ready to serve connections…”
> CGroup: /system.slice/smb.service
> ├─9141 /usr/sbin/smbd -D
> └─9142 /usr/sbin/smbd -D
> --------------------
>
>
>
> Code:
> --------------------
> nmb.service - Samba NMB Daemon
> Loaded: loaded (/usr/lib/systemd/system/nmb.service; enabled)
> Active: active (running) since Sat 2015-01-17 05:24:01 GMT; 12h ago
> Main PID: 30232 (nmbd)
> Status: “nmbd: ready to serve connections…”
> CGroup: /system.slice/nmb.service
> └─30232 /usr/sbin/nmbd -D
> --------------------
Good!
>
> This is an smb.conf I stole off a friend ‘just to test’ -
>
>
> Code:
> --------------------
> [global]
> server string = %h server (Samba, Ubuntu)
> map to guest = Bad User
> obey pam restrictions = yes
> pam password change = yes
> passwd program = /usr/bin/passwd %u
> passwd chat = enter/snew/s/spasswrd:* %n
Retype/snew/s/spassword:* %n
password/supdated\ssuccessfully .
> unix password sync = yes
> syslog = o
> log file = /var/log/samba/log.%m
> max log size = 1000
> dns proxy = no
> usershare allow guest = yes
> panic action = /usr/share/samba/panic-action %d
> usershare allow guests = Yes
> wins support = No
> usershare max shares = 100
> security = domain
> ldap admin dn =
> passdb backend = smbpasswd
> wins server =
> workgroup = WORKGROUP
>
<snip>
This can not work. “security = domain” should only be used on a member server of an NT or Samba Domain. NEVER on a
simple workgroup setup. You also have the password backend set to smbpasswd. This is a clear texf file and unless you
reran smbpasswd with this config file it will be empty. The original config used the tdb backend.
>
> This is the smb.conf I was trying before that - it’s basically stock,
> except for ticking the usershare boxes in Yast.
This looks fairly good. There is a bit of extra stuff that does no harm and with the defaults it should work.
With the comments removed, this is what I found.
> [global]
> workgroup = WORKGROUP
> passdb backend = tdbsam
> printing = cups
> printcap name = cup
> printcap cache time = 750
> cups options = raw
> map to guest = Bad User
> include = /etc/samba/dhcp.conf
> logon path = \%L\profiles.msprofile
> logon home = \%L%U.9xprofile
> logon drive = P:
> usershare max shares = 100
> usershare allow guests = Yes
>
>
> [homes]
> comment = Home Directories
> valid users = %S, %D%w%S
> browseable = No
> read only = No
> inherit acls = Yes
>
> [profiles]
> comment = Network Profiles Service
> path = %H
> read only = No
> store dos attributes = Yes
> create mask = 0600
> directory mask = 0700
> [users]
> comment = All users
> path = /home
> read only = No
> inherit acls = Yes
> veto files = /aquota.user/groups/shares/
>
> [groups]
> comment = All groups
> path = /home/groups
> read only = No
> inherit acls = Yes
>
> [printers]
> comment = All Printers
> path = /var/tmp
> printable = Yes
> create mask = 0600
> browseable = No
>
> [print$]
> comment = Printer Drivers
> path = /var/lib/samba/drivers
> write list = @ntadmin root
> force group = ntadmin
> create mask = 0664
> directory mask = 0775
> --------------------
> Thanks for the help! 
Your original samb.conf should have worked fairly well. There may have been some name resolution problems and I would
suggest you add to the [global] section the following parameter:
name resolve order = bcast host lmhosts
By default broad casts (bcast) are last and often name resolution fails before you get that far.
That could be the cause of this error:
Code:
protocol negotiation failed: NT_STATUS_IO_TIMEOUT
If you were using IP it could be something else. Have you disabled AppArmor for testing purposes?
Use your original smb.conf with the above name resolve parameter added. Then post the results of:
smbclient -L <IP of Server>
smbclient -L <ServerName>
When asked for a password use the smbpasswd of the user that executes the command.
Run these on both the client and server. Post the exact results not a summary.
By default the > is the same as the host name(first part of the DNS name) so long as it conforms to netbios
standards (up to 15 ASCII characters). If the host name does not comply you can add a netbios name. To add the name in
the [global] section of /etc/samba/smb.conf add the parameter:
netbios name = <MYSERVER>
Once you can contact the server we can work on the shares.
P.V.
“We’re all in this together, I’m pulling for you” Red Green
Any help would be appreciated, thanks all!
). I tried connecting to it from my Android client, and it tells me the IP is unreachable or isn’t a Samba server (And it doesn’t show up in the auto-discovered list). I’ll try a Windows box next and see if that works.