Re: [Samba] Device WinDfs error

2007-05-04 Thread Kevin Bailey 

Jeremy Allison wrote:


On Sun, Apr 29, 2007 at 07:59:00PM +0100, Kevin Bailey wrote:
 


\Device\WinDfs\H:00186bf9\psctpdc\bpeters\thunderbird\ImapMail\10.1.1.10\INBOX.msf
The data has been lost.
This error may be caused by a failure of your computer hardware or 
network connection.


[2007/04/23 14:38:26, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 10.1.1.144. Error 
Connection reset by peer

[2007/04/23 14:38:26, 0] lib/util_sock.c:send_smb(769)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/04/23 14:57:23, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.1.1.144. Error = 
Connection timed out
   



Your tcp connection failed. We (smbd) don't know why.

Check your networking hardware + cables.

Jeremy.
 




Thanks for the reply.

This error has occured since we upgraded to Samba 3 but we also turned off 
roaming profiles at the same time.


Since the Thunderbird profile is now stored in the users H: drive and not being 
downloaded from the server to the PC at logon it sounds like Thunderbird is 
having a glitch.


(We don't want to turn profiles back on as loading the NTConfig.POL file gives 
us all the control we need).


Thanks again for all the hard work!

Kevin





Jeremy Allison wrote:


On Sun, Apr 29, 2007 at 07:59:00PM +0100, Kevin Bailey wrote:
 


\Device\WinDfs\H:00186bf9\psctpdc\bpeters\thunderbird\ImapMail\10.1.1.10\INBOX.msf
The data has been lost.
This error may be caused by a failure of your computer hardware or 
network connection.


[2007/04/23 14:38:26, 0] lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 10.1.1.144. Error 
Connection reset by peer

[2007/04/23 14:38:26, 0] lib/util_sock.c:send_smb(769)
Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/04/23 14:57:23, 0] lib/util_sock.c:read_data(534)
read_data: read failure for 4 bytes to client 10.1.1.144. Error = 
Connection timed out
   



Your tcp connection failed. We (smbd) don't know why.

Check your networking hardware + cables.

Jeremy.
 



--
Kevin Bailey
IT Consultant

Email: [EMAIL PROTECTED]
Tel: 01752 268923
W: www.freewayprojects.com

--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

[Samba] Device WinDfs error

2007-04-29 Thread Kevin Bailey 

Hi,

Have recently upgraded from Samba 2.2 on Debian Woody to Samba 3.0.24-6 
on Debian Etch.


Some PC's have now reported errors similar to this one.

Windows - delay write failed.
Windows was unable to save all the data for the file
\Device\WinDfs\H:00186bf9\psctpdc\bpeters\thunderbird\ImapMail\10.1.1.10\INBOX.msf
The data has been lost.
This error may be caused by a failure of your computer hardware or 
network connection.



This seems to be related to when the users are using Thunderbird.  
Thunderbird on each PC is set up to use a profile which is stored under 
the users H: drive which is the home folder supplied by Samba.  All the 
profiles are set to pick up mail over IMAP and the actual mail is stored 
under a Maildir in each users home directory.


Funny thing is that I can't see an INBOX.msf file anywhere.  I'm not 
sure what Windows is trying to do here.


The server runs dual SCSI HDD's as RAID 1 from an adaptec SCSI RAID 2110s.

uname -a gives
Linux psctpdc 2.6.18-4-486 #1 Mon Mar 26 16:39:10 UTC 2007 i686 GNU/Linux

and this is the output from the samba log file which I fairly sure is 
the right PC on the day when the error appeared.



Thanks for any help.

[2007/04/23 08:42:11, 1] smbd/service.c:make_connection_snum(950)
 xp4 (10.1.1.144) connect to service netlogon initially as user bpeters 
(uid=1007, gid=1007) (pid 25434)

[2007/04/23 08:42:14, 1] smbd/service.c:make_connection_snum(950)
 xp4 (10.1.1.144) connect to service bpeters initially as user bpeters 
(uid=1007, gid=1007) (pid 25434)

[2007/04/23 08:42:24, 1] smbd/service.c:make_connection_snum(950)
 xp4 (10.1.1.144) connect to service bksb initially as user bpeters 
(uid=1007, gid=1007) (pid 25434)

[2007/04/23 08:42:25, 1] smbd/service.c:make_connection_snum(950)
 xp4 (10.1.1.144) connect to service public initially as user bpeters 
(uid=1007, gid=1007) (pid 25434)

[2007/04/23 08:50:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 08:50:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 08:52:46, 1] smbd/service.c:close_cnum(1150)
 xp4 (10.1.1.144) closed connection to service public
[2007/04/23 08:52:46, 1] smbd/service.c:close_cnum(1150)
 xp4 (10.1.1.144) closed connection to service bksb
[2007/04/23 08:52:46, 1] smbd/service.c:close_cnum(1150)
 xp4 (10.1.1.144) closed connection to service netlogon
[2007/04/23 09:02:56, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 09:02:56, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 09:07:45, 1] smbd/service.c:make_connection_snum(950)
 xp4 (10.1.1.144) connect to service bksb initially as user bpeters 
(uid=1007, gid=1007) (pid 25434)

[2007/04/23 09:16:01, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 09:16:01, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 09:18:01, 1] smbd/service.c:close_cnum(1150)
 xp4 (10.1.1.144) closed connection to service bksb
[2007/04/23 09:29:03, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 09:29:03, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 09:42:05, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 09:42:05, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 09:55:01, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 09:55:01, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 10:08:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 10:08:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 10:21:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 10:21:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 10:34:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 10:34:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 10:47:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 10:47:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 11:00:00, 0] printing/pcap.c:pcap_cache_reload(159)
 Unable to open printcap file /etc/printcap for read!
[2007/04/23 11:00:00,

Re: [Samba] Device WinDfs error

2007-04-29 Thread Jeremy Allison 
On Sun, Apr 29, 2007 at 07:59:00PM +0100, Kevin Bailey wrote:
 \Device\WinDfs\H:00186bf9\psctpdc\bpeters\thunderbird\ImapMail\10.1.1.10\INBOX.msf
 The data has been lost.
 This error may be caused by a failure of your computer hardware or 
 network connection.
 
 [2007/04/23 14:38:26, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 10.1.1.144. Error 
 Connection reset by peer
 [2007/04/23 14:38:26, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
 [2007/04/23 14:57:23, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 10.1.1.144. Error = 
 Connection timed out

Your tcp connection failed. We (smbd) don't know why.

Check your networking hardware + cables.

Jeremy.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba