samba - Sep 2009 - Port 7

I am running Samba 3.3.2 on Ubuntu 9.04 and /proc/version states "Linux
version 2.6.28-15-server (buildd at yellow) (gcc version 4.3.3 (Ubuntu
4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 20:09:37 UTC 2009".  Recently,
to support a new client on my home network (running Windows 7 RTM 32-bit), I
modified my smb.conf file.  The Windows 7 client had refused to connect to
Samba with an error stating "More data available."  Prompt Googling of
this
issue returned a workaround involving adding "smb ports = 139" to my
config
file.  Everything seemed to work fine since the change, except I noticed
that Samba is now listening on TCP port 7.  This port is historically used
by inetd or xinetd running an ECHO service.  I have confirmed that it is
definitely Samba listening on port 7, and that Samba is now echoing data
sent to that port.
In short, why does Samba open TCP port 7 and run an ECHO service when "smb
ports = 139" is specified in the configuration file?

On Mon, Sep 07, 2009 at 05:20:52AM -0500, Anthony Accurso
wrote:
> I am running Samba 3.3.2 on Ubuntu 9.04 and /proc/version states
"Linux
> version 2.6.28-15-server (buildd at yellow) (gcc version 4.3.3 (Ubuntu
> 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 20:09:37 UTC 2009". 
Recently,
> to support a new client on my home network (running Windows 7 RTM 32-bit),
I
> modified my smb.conf file.  The Windows 7 client had refused to connect to
> Samba with an error stating "More data available."  Prompt
Googling of this
> issue returned a workaround involving adding "smb ports = 139" to
my config
> file.  Everything seemed to work fine since the change, except I noticed
> that Samba is now listening on TCP port 7.  This port is historically used
> by inetd or xinetd running an ECHO service.  I have confirmed that it is
> definitely Samba listening on port 7, and that Samba is now echoing data
> sent to that port.
How did you confirm that it's Samba listening there?
> In short, why does Samba open TCP port 7 and run an ECHO service when
"smb
> ports = 139" is specified in the configuration file?
I'm very surprised that Samba listens there. To be honest, I
don't believe that yet before you said how you confirmed
this :-)

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20090907/51405db4/attachment.pgp>

On Mon, Sep 7, 2009 at 5:27 AM, Volker Lendecke
<Volker.Lendecke at sernet.de> wrote:
>
> On Mon, Sep 07, 2009 at 05:20:52AM -0500, Anthony Accurso wrote:
> > I am running Samba 3.3.2 on Ubuntu 9.04 and /proc/version states
"Linux
> > version 2.6.28-15-server (buildd at yellow) (gcc version 4.3.3 (Ubuntu
> > 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 20:09:37 UTC 2009". 
Recently,
> > to support a new client on my home network (running Windows 7 RTM
32-bit), I
> > modified my smb.conf file.  The Windows 7 client had refused to
connect to
> > Samba with an error stating "More data available."  Prompt
Googling of this
> > issue returned a workaround involving adding "smb ports =
139" to my config
> > file.  Everything seemed to work fine since the change, except I
noticed
> > that Samba is now listening on TCP port 7.  This port is historically
used
> > by inetd or xinetd running an ECHO service.  I have confirmed that it
is
> > definitely Samba listening on port 7, and that Samba is now echoing
data
> > sent to that port.
> >
> > In short, why does Samba open TCP port 7 and run an ECHO service when
"smb
> > ports = 139" is specified in the configuration file?
>
> How did you confirm that it's Samba listening there?
>
> Volker
>
Output of "fuser 7/tcp" identifies PID 650.  Output of "ps
650"
identifies "/usr/sbin/smbd -D".  That's the hard way.  The easy
way
was stopping Samba and watching port 7 close (via nmap).

Hi Anthony,

On Mon, Sep 07, 2009 at 05:20:52AM -0500, Anthony Accurso
wrote:
> I am running Samba 3.3.2 on Ubuntu 9.04 and /proc/version states
"Linux
> version 2.6.28-15-server (buildd at yellow) (gcc version 4.3.3 (Ubuntu
> 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 20:09:37 UTC 2009". 
Recently,
> to support a new client on my home network (running Windows 7 RTM 32-bit),
I
> modified my smb.conf file.  The Windows 7 client had refused to connect to
> Samba with an error stating "More data available."  Prompt
Googling of this
> issue returned a workaround involving adding "smb ports = 139" to
my config
> file.  Everything seemed to work fine since the change, except I noticed
> that Samba is now listening on TCP port 7.  This port is historically used
> by inetd or xinetd running an ECHO service.  I have confirmed that it is
> definitely Samba listening on port 7, and that Samba is now echoing data
> sent to that port.
> In short, why does Samba open TCP port 7 and run an ECHO service when
"smb
> ports = 139" is specified in the configuration file?
Did you try something like "testparm -s  | grep 7" in order to
guarantee
that there is no other line in smb.conf which defines a port 7? I'm also
using "smb ports=139" - port 7 is closed:-) (but this is with Samba
version 3.3.4).

Axel