samba - Aug 2007 - Offline files enabled clients are loosing network drives

Hello,

since the update to Samba 3.0.25b Clients which have offline files enabled
- typically notebooks - are sporadical loosing their network drives.  

In the samba logs I see: 
"read_data: read failure for 4 bytes to client 192.168.1.58. Error =
Connection timed out"

After a new login the client can connect again to the shares again, but
after some minutes of work the same thing happens again.

Clients with no enabled offline files have no problems.

We are using XP Prof. Clients and Samba 3.0.25b (sernet-samba) on Debian
Etch. One of our five samba file server is acting as PDC with OpenLDAP as
auth. backend.



Regards,

Henry

Greeting Henry,

I say that is normal (because it's the same thing with a Windows server) 
. If the notebook (with offline files enabled) is turn on without any 
nic connected, Windows will work offline (no surprise here). A this 
point, you can't map or acces the server share (you can try to access 
share with UNC path, it will not work). But if you try to access share 
on another server, not in the share mapping of your client, then all 
work perfectly.

The "problem" is the client. You must enable online work to reaccess
the
server share. Look at the taskbar on the windows client for a small 
computer, double-click on it an try to synchronise, or just select the 
option to work online without synchronize (look at the buttom of this 
page 
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/prork/prdc_mcc_gmba.mspx?mfr=true).


Best regards,

Robert

-- 
Cybionet - Solution reseautique
http://www.cybionet.com
> Hello,
>
> since the update to Samba 3.0.25b Clients which have offline files enabled
> - typically notebooks - are sporadical loosing their network drives.  
>
> In the samba logs I see: 
> "read_data: read failure for 4 bytes to client 192.168.1.58. Error =
Connection timed out"
>
> After a new login the client can connect again to the shares again, but
> after some minutes of work the same thing happens again.
>
> Clients with no enabled offline files have no problems.
>
> We are using XP Prof. Clients and Samba 3.0.25b (sernet-samba) on Debian
> Etch. One of our five samba file server is acting as PDC with OpenLDAP as
> auth. backend.
>
>
>
> Regards,
>
> Henry
>
>

Hallo, Henry,

Du (hjensen) meintest am 16.08.07:
> since the update to Samba 3.0.25b Clients which have offline files
> enabled - typically notebooks - are sporadical loosing their network
> drives.
> In the samba logs I see:
> "read_data: read failure for 4 bytes to client 192.168.1.58. Error
> Connection timed out"
I know many installations in schools where this notice fills the log  
files ...
> After a new login the client can connect again to the shares again,
> but after some minutes of work the same thing happens again.
> Clients with no enabled offline files have no problems.
  http://www.winfaq.de/faq_html/Content/onlinefaq.php?h=tip1962.htm

shows how to change this configuration.
Tomorrow a colleague will test it.
> We are using XP Prof. Clients and Samba 3.0.25b (sernet-samba) on
> Debian Etch.
Samba 3.0.22 on Slackware 11.0, no PDC.

Viele Gruesse!
Helmut

Hello,


On Thu, Aug 16, 2007 at 09:19:04AM +0000, Henry Jensen
wrote:
> since the update to Samba 3.0.25b Clients which have offline files enabled
> - typically notebooks - are sporadical loosing their network drives.  

The problems I had here with samba 3.0.25b are significant. It all began
after the upgrade:

- Notebook-Clients which had offline files enabled are losing network drives.

- MS-Office complains that it can not safe files. The error messages are 
  variantly (translated from german Windows XP Prof. and MS-Office 2003) 
  "No space left on device" (which is a network share) and "Too
many open
  files". Unfortunatley this is erradic and not reproducible, and I have
  no time to debug, because this is a production system which must
  "simply work".
  I can't find any messages regarding this problems in the samba log. 

I have now downgraded to Samba 3.0.25a again which was running with no
problems for two month before the upgrade to 3.0.25b.  

Regards,

Henry