connecton reset by peer - socket problem

MCCALL,DON (HP-USA,ex1) don_mccall at
Thu Oct 11 06:04:03 GMT 2001

Hello John,
this sort of thing usually points to a routing or network issue
below samba;  I'm not familiar with networking on redhat, or 
ip aliasing on that platform, but assuming you have

interfaces = 192.168.whatever/ 'realip'/'realipsubnetmask'

along with your allow hosts line

then I would start looking at my routing tables, etc. and reverse lookup
implementation (samba has to do reverse lookups when allow hosts line is 

Another thing you could do to further isolate the issue is to temporarily
REMOVE the 'allow hosts' line and see if WITHOUT this, the problem goes 
away.  If it does, it's then almost certainly a reverse lookup/routing

Hope this helps,

-----Original Message-----
From: John Chiu [mailto:john-chiu at]
Sent: Wednesday, October 10, 2001 10:40 PM
To: samba at
Subject: connecton reset by peer - socket problem

i set up a samba on redhat with a 192.168.x.x ip and and alias of a real
ip.  on the lan i have win nt and win 2k with real ip that can access
the samba without difficulty, but when the win 98/me workstations, with
192.168.x.x ip's, try to connect to the samba, it would be either very
slow, or saying that the lan is busy, or cannot connect at all.  then,
in the samba, i'll see the log saying that "error on writing 4 bytes to
socket 5 (or 6), connection reset by peer, exit now...".

and, the samba  does not seem to be visible on the "network
neighbourhood" stably.  i have specifically written a statement of
"allow hosts = 192.168.0. (followed with the real ips for the win
nt/2k)" in the config file.  i'm very much annoyed by this.

pls pls pls help to point out what have i done wrong

To unsubscribe from this list go to the following URL and read the

More information about the samba mailing list