> My money is on the switch :-). This is a classic "my tcp connection
> went away and I don't know why" error message.
>
> Jeremy.
Your money was invested well ;-)
In our situation the problems disappeared for now (cross the fingers!) with
a new hub, what makes sense because of a fine working Wi
Hi, if it is a bug it is relate to winxp 64 versions,
i had never such problems with suse/samba during all upgrades from first
samba 3 release up to now
on different servers 32/64 intel /amd with mutliple nics
perhaps somthing is allready in bugzilla about win xp 64?
Regards
Beschorner Daniel
On Tue, Mar 07, 2006 at 03:51:34PM +0100, Beschorner Daniel wrote:
> We have a similar or same problem with one of our servers after upgrade from
> 3.0.14 to 3.0.21x (incidentally??).
>
> The log shows things like:
>
> write_data: write failure in writing to client 192.168.17.249. Error Broken
>
We have a similar or same problem with one of our servers after upgrade from
3.0.14 to 3.0.21x (incidentally??).
The log shows things like:
write_data: write failure in writing to client 192.168.17.249. Error Broken
pipe
[2006/03/06 20:46:47, 0] lib/util_sock.c:get_peer_addr(1225)
getpeername
Hi Bjoern,
in general there is no problem with suse samba etc
ich have very large samba domains up and running, but dont forget
samba 3 is acting like win nt 4 server ( pdc )
its not an active dir controller as win 2003 server
if you need acitve dir for i.e exchange version higher than 5.5
you hav
Hello mailing-list,
this is my first post and i hope that you enjoy my very bad but
sometimes funny english.
My Problem is the following:
First of all, my server-config:
Samba Version 3.0.20b-3.4-SUSE
on a
SUSE Linux Enterprise Server 9
with Kernel 2.6.5-7.252-smp
Now the problem is, that s