LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE
User Name
Password
SUSE / openSUSE This Forum is for the discussion of Suse Linux.

Notices


Reply
  Search this Thread
Old 04-22-2014, 03:30 AM   #1
dobradude45
Member
 
Registered: Dec 2013
Posts: 42

Rep: Reputation: Disabled
Samba accessing Windows shares via Dolphin times out


Hi there
Finally got Opensuse 13.1 running just great - but ONE niggling issue

Using Dolphin file manager (KDE) network I can see all the computers on the network (including Windows machines) - and can access all the shares after Samba starts.

After a while of not having used the system I then get a time out if I try and access a windows share although I can see all the computer. A samba restart fixes this easily but I don't want to keep doing this.

Are there any settings or other things I can do so this problem doesn't occur again. (It's a trivial problem but it's the difference between a 99.9% system and a perfect system.

Cheers
 
Old 04-22-2014, 08:11 PM   #2
berndbausch
LQ Addict
 
Registered: Nov 2013
Location: Tokyo
Distribution: Mostly Ubuntu and Centos
Posts: 6,316

Rep: Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002Reputation: 2002
Quote:
Originally Posted by dobradude45 View Post
Hi there
Finally got Opensuse 13.1 running just great - but ONE niggling issue

Using Dolphin file manager (KDE) network I can see all the computers on the network (including Windows machines) - and can access all the shares after Samba starts.

After a while of not having used the system I then get a time out if I try and access a windows share although I can see all the computer. A samba restart fixes this easily but I don't want to keep doing this.

Are there any settings or other things I can do so this problem doesn't occur again. (It's a trivial problem but it's the difference between a 99.9% system and a perfect system.
Do you see anything in the log files? Possibly /var/log/samba and /var/log/syslog or /var/log/messages, but they may have different names on OpenSUSE.
You can also switch on debugging in the samba config file and thereby increase the message output.
When you experience the timeout, try accessing the share with a command line tool like smbclient.
And try accessing the share from different Windows PC if that's possible.
 
Old 04-23-2014, 03:15 AM   #3
dobradude45
Member
 
Registered: Dec 2013
Posts: 42

Original Poster
Rep: Reputation: Disabled
Hi there
The strange thing is that FROM windows the Linux files are always accessible but from LINUX TO Windows is when the timeout happens

Cheers
 
Old 05-01-2014, 03:09 AM   #4
dobradude45
Member
 
Registered: Dec 2013
Posts: 42

Original Poster
Rep: Reputation: Disabled
Hi there


This conf file seemed to do the trick.

The relevant line was this one (not sure why )

name resolve order = bcast host lmhosts wins

Note this is only for a HOME network - no Domains or complicated stuff -- the Linux server to be accessible by 4 Home type Windows machines. No special things like Name / Wins servers etc.


# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
[global]
netbios name = Gylfi
workgroup = WORKGROUP
passdb backend = smbpasswd
preferred master = yes
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
usershare allow guests = Yes
server string = ""
usershare max shares = 100
usershare owner only = false
netbios name = gylfi
wins support = no
name resolve order = bcast host lmhosts wins

[gylfi-data]
comment = samba server
guest ok = Yes
inherit acls = Yes
path = /home/jim
read only = No


Cheers
 
Old 10-31-2015, 05:31 AM   #5
fometeo
LQ Newbie
 
Registered: Jul 2009
Location: Portugal
Distribution: CentOS, Ubuntu, SuSE
Posts: 3

Rep: Reputation: 0
Post security parameter

at a case where a very old Samba 2 share was not browsable by an Ubuntu 14 Dolphin
the solution was changing 2 parameters at /etc/samba/smb.conf

[global]
security = share
domain logons = No

it was not used for domain logons and had security = user
in this case it has just 2 public shares

[TEMP]
comment = TEMP (read-write)
path = /home/temp
read only = No
guest only = Yes
guest ok = Yes

[PUBLIC]
comment = PUBLIC (read-only)
path = /home/public
guest ok = Yes

good documentation about samba types at
https://www.samba.org/samba/docs/man...erverType.html
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Accessing Windows Or Samba Shares Using AutoFS LXer Syndicated Linux News 0 12-14-2006 04:03 PM
accessing samba shares from windows xubuntu_idiot Linux - Software 1 09-05-2006 12:25 PM
Accessing samba shares from a windows machine lacitpo Linux - Software 2 12-13-2004 06:47 AM
windows locks up while accessing samba shares Ogi Linux - Software 0 09-30-2004 05:28 AM
Problem accessing windows shares using samba Tinku Linux - Software 6 08-05-2004 07:47 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE

All times are GMT -5. The time now is 11:13 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration