Re: [Samba] Samba 3.0.10 errors

2005-01-25 Thread James Kosin
I'm trying to track down these errors myself.  They are usually 
attributed to a virus or trojan that happens to be on the network...  
The weird part about them, is they do come from valid IPs on the subnet 
in some cases and are related to specific machine IPs.  So, I'm not sure 
why samba is unable to reference an IP.  Unless, it isn't suffing that 
information because of the invalid placed requests and these are just 
errors in the return packets.

First, check to be sure you don't have a virus or trojan running rampid 
on your network.  You can find out what IP numbers they are by using a 
tool like ethreal to capture the IP traffic and compare the timestamps 
on the IP traffic you collect with the time stamps in the samba logfiles.

I would be glad if someone could find out what this was as well.
James
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Samba 3.0.10 errors

2005-01-24 Thread Giovani Moda - MR Informtica
Hello,
I'm constantly getting those errors on my samba server:
[2005/01/24 11:04:16, 0] lib/util_sock.c:read_socket_data(384)
 read_socket_data: recv failure for 4. Error = Connection reset by peer
[2005/01/24 16:54:32, 0] lib/util_sock.c:get_peer_addr(1000)
 getpeername failed. Error was Transport endpoint is not connected
There are logs created with the client's IP numbers, filled with the errors 
mentioned above, and a log file named 0.0.0.0.log, also with those errors. 
The things is: there should NOT be log files named after the client's IP 
number, since my smb.conf have a log file = /var/log/samba/%m.log entry.

There are also log files ( the expected ones) named after the client's 
netbios named that contains no errors at all.

It appears that samba is, sometimes, unable to get the netbios name of the 
clients. I haven't seen those on other versions of samba, so I'm guessing 
that's not a default (or normal) operation.

Everything seems to be working fine, but these error messages are kinda 
worrying me. Any idea of what those are?

My configuration is samba-3.0.10, PDC, security = user. No winbind, no 
openldap, no ADS. All the clients are Windows XP SP2. Simples as it can be. 
But still, those errors.

I have tried all the settings I know, I've searched everywhere, but no luck 
on getting those fixed.

Any ideas would be much appreciated.
Thanks advanced;
Giovani 


--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba