[Dorset] Samba networking issues

2011-01-30 Thread Terry Coles
Hi,

My son is trying to access our Stora media server as a file server using samba 
on Kubuntu 10.10.  When he first tried to access the network, the response was 
that there was nothing on it, then after a while the Stora and other boxes 
appeared.  I told him that this was a 'feature' of smb/cifs in that the 
network takes a while to notice that a new host has joined but after that it 
should be pretty much instantaneous.

He's just proved me wrong because after a crash in k3b, (I don't know why; 
I've never seen k3b crash) he rebooted his machine and now he has exactly the 
same delay.

Anyone any ideas why this is happening?  Networking works fine on this 
computer and any others that I've connected in the past.  I don't recall if 
this machine has been connected to the network ipreviously; it's relatively 
new and we probably did a clean install of Kubuntu last October.

-- 
Terry Coles
64 bit computing with Kubuntu Linux


--
Next meeting:  Bournemouth, Tuesday 2011-02-01 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
How to Report Bugs Effectively:  http://goo.gl/4Xue


Re: [Dorset] Samba networking issues

2011-01-30 Thread Keith Edmunds
On Sun, 30 Jan 2011 13:42:34 +, d-...@hadrian-way.co.uk said:

 Anyone any ideas why this is happening?

The delay could be DNS timeouts. Is Samba configured to do a reverse DNS
lookup of clients? If it is, is there a valid reverse DNS entry (almost
certainly not)? 

--
Next meeting:  Bournemouth, Tuesday 2011-02-01 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
How to Report Bugs Effectively:  http://goo.gl/4Xue


Re: [Dorset] Samba networking issues

2011-01-30 Thread John Carlyle-Clarke

On 30/01/11 13:42, Terry Coles wrote:

Hi,

My son is trying to access our Stora media server as a file server using samba
on Kubuntu 10.10.  When he first tried to access the network, the response was
that there was nothing on it, then after a while the Stora and other boxes
appeared.  I told him that this was a 'feature' of smb/cifs in that the
network takes a while to notice that a new host has joined but after that it
should be pretty much instantaneous.

He's just proved me wrong because after a crash in k3b, (I don't know why;
I've never seen k3b crash) he rebooted his machine and now he has exactly the
same delay.

Anyone any ideas why this is happening?  Networking works fine on this
computer and any others that I've connected in the past.  I don't recall if
this machine has been connected to the network ipreviously; it's relatively
new and we probably did a clean install of Kubuntu last October.



I remember a similar problem, caused by DNS issues.  The systems were 
configured to use OpenDNS, and they serve a search page for any failed 
DNS lookup.  Samba clients were using DNS as a first option.  Instead of 
a failure that would cause them to try other methods, they were trying 
to use IP address returned, which was the OpenDNS search page web server.


The fix, IIRC, was to create a /etc/samba/smb.conf file on the client 
machines and set (again from memory) the name resolve order paramter.


The smbclient and smbcontrol command line tools are very useful for 
debugging!


Something like smbcontrol all debug 3 will set all daemons to a higher 
log level.  You can then tail -f the log file in one terminal and try 
smbclient -L //somename or smbclient -L //192.168.1.1, using the 
actual IP of the machine you want to browse.


Best regards,

John

--
Next meeting:  Bournemouth, Tuesday 2011-02-01 20:00
Meets, Mailing list, IRC, LinkedIn, ...  http://dorset.lug.org.uk/
How to Report Bugs Effectively:  http://goo.gl/4Xue