samba - Mar 2004 - Problems since upgrading 2.2 to 3

Hello,
I am running Debian on an i386 machine. I recently upgraded to Debian 
Testing, which upgraded Samba from 2.2 to 3.0.2. Since then, I have been 
having several problems. The Samba server is used as a PDC for Windows 
XP Pro. clients. Sometimes (often) when users log on, they get an error 
about a single file in their profile not being able to be copied to 
their local profile, and then a message saying that their server profile 
cannot be found. Whenever this occurs, the following appears in 
/var/log/smbd:

[2004/03/02 20:47:31, 0] lib/util_sock.c:get_peer_addr(952)
  getpeername failed. Error was Transport endpoint is not connected

This problem also occurs when the server is otherwise being used - it is 
noticeable in that the Windows clients freeze for roughly 30 seconds 
whilst attempting to access the server. The above error message also 
appears in the log.

Secondly, printers shared by the server (using CUPS as printer system), 
have the tendancy to "disappear" from being shared after a week or so;
they reappear if smbd is restarted.

Any ideas?
Thanks,

Alex Meaden,
Xelam Internet Services.

"Alex Meaden" <alex@xelam.net> wrote in message
news:4044F949.5010906@xelam.net...
> I am running Debian on an i386 machine. I recently upgraded to Debian
> Testing, which upgraded Samba from 2.2 to 3.0.2. Since then, I have been
> having several problems. The Samba server is used as a PDC for Windows
> XP Pro. clients. Sometimes (often) when users log on, they get an error
> about a single file in their profile not being able to be copied to
I had the same problem when I upgraded from RedHat 7.3 to Fedora Core 1.
The problem file was in the "Send To" folder in each user's
profile.  It was
the "Send to 3 1/2" floppy" link.  I think the problem was
because Fedora
supports UTF8 and the old system didn't or something.  In any event, the
name of the link was mangled into something that Windows didn't dig.  I just
erased the file from each user's profile and then they were able to log on
just fine.  You could probably also rename it to "Floppy" to get rid
of the
fraction part.

That error message you are seeing in the logs is normal (or at least common)
and harmless.

Mark