samba - Jun 2002 - Clean install of RedHat 7.3, including samba - unable to connect to port 139

I did a clean install of Redhat 7.3 on a system.  The install 
included samba, samba-client, samba-common.  I moved the saved 
versions of smb.conf, smbusers and swbpasswd to /etc/samba.  Then I 
started up smb by issuing "/etc/init.d/smb start"   I have set smb to 
start upon reboot of the system.    I have rebooted the system 
several times.  smbd and nmbd start up, but clients cannot connect.

There are no unusual errors reported in the samba logs.  testparm of 
the configuration files reports no errors.

"smbclient -L host-having-problems"
adds the interfaces
Password:
Anonymous login successful
Domain=[Chemistry] OS=[Unix] Server=[Samba 2.2.3a]
tree connect failed:  NT_STATUS_WRONG_PASSWORD


If I do the same test from another RedHat samba server
"smbclient -L host-having-problems"
adds the interfaces
error connecting to xxx.xxx.xxx.xxx:139 (Connection refused)
error connecting to xxx.xxx.xxx.xxx (Connection refused)

I took the moderate security option when I did the clean install of 
the system.  By the way the second server was upgraded to 7.3.  It 
has no problem being a samba server.

Looks like your firewall is blocking it.

Try it after turning the FW off:

    service ipchains stop

and/or

    service iptables stop

depending on which you are running.

If you can connect now, check the firewall rules before turning them back
on.

Thomas

----- Original Message -----
From: Margaret Doll <Margaret_Doll@Brown.edu>
To: <samba@lists.samba.org>; valhalla <valhalla-list@redhat.com>
Sent: Sunday, June 09, 2002 4:09 PM
Subject: [Samba] Clean install of RedHat 7.3, including samba - unable to
connectto port 139

> I did a clean install of Redhat 7.3 on a system.  The install
> included samba, samba-client, samba-common.  I moved the saved
> versions of smb.conf, smbusers and swbpasswd to /etc/samba.  Then I
> started up smb by issuing "/etc/init.d/smb start"   I have set
smb to
> start upon reboot of the system.    I have rebooted the system
> several times.  smbd and nmbd start up, but clients cannot connect.
>
> There are no unusual errors reported in the samba logs.  testparm of
> the configuration files reports no errors.
>
> "smbclient -L host-having-problems"
> adds the interfaces
> Password:
> Anonymous login successful
> Domain=[Chemistry] OS=[Unix] Server=[Samba 2.2.3a]
> tree connect failed:  NT_STATUS_WRONG_PASSWORD
>
>
> If I do the same test from another RedHat samba server
> "smbclient -L host-having-problems"
> adds the interfaces
> error connecting to xxx.xxx.xxx.xxx:139 (Connection refused)
> error connecting to xxx.xxx.xxx.xxx (Connection refused)
>
> I took the moderate security option when I did the clean install of
> the system.  By the way the second server was upgraded to 7.3.  It
> has no problem being a samba server.
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>

Part of the problem was resolved by

service ipchains stop

I can connect on port 139 now, but I need an account and
passwd.

smbclient -L host-having-problems -U user1%passwd
works

smbclient -L host-having-problems
added interface ...
added interface ..
Password:
Anonymous login successful
Domain=[CHEMISTRY] OS=[UNIX} Server=[Samba 2.2.3a]
tree connect failed; NT_STATUS_WRONG_PASSWORD

Clients can access printer on the server, but they can't see
the server in the network neighborhood.  Some versions
of windows can find the server using the "Find Computer"
command some cannot.  Even when the client cannot
find the computer, I can create a printer for the client
which uses the print queue on the server by specifically
adding the path

	\\server\printer

I feel I still have a security problem.

socklist shows

	tcp 139 being used numerous times by smbd
	tcp 137 being used numerous times by nmbd
	udp various port numbers are being used by smbd and nmbd

>On 2002-06-09, Margaret Doll wrote:
>
>[snip]
>
>MD> If I do the same test from another RedHat samba server
>MD> "smbclient -L host-having-problems"
>MD> adds the interfaces
>MD> error connecting to xxx.xxx.xxx.xxx:139 (Connection refused)
>MD> error connecting to xxx.xxx.xxx.xxx (Connection refused)
>MD>
>MD> I took the moderate security option when I did the clean install of
>MD> the system.
>
>Well, does the "moderate security" option allow incoming traffic
to
>ports 137-139? If so, verify whether Samba is listening on ports 137
>to 139. Easy to use is "socklist" (from the procinfo rpm). If the
>firewall blocks ports 137-139, you need to configure it to allow
>access to the NETBIOS ports.
>
>And of course, you have verified your Samba setup on localhost?
>
>
>
>_______________________________________________
>Valhalla-list mailing list
>Valhalla-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/valhalla-list

-- 



					Margaret Doll  (401-863-1982)
					margaret_doll@brown.edu
					(401) 745-7306 (beeper)