[SOLVED] Samba port closed?

damacas · 2012-06-30 16:40:06

I tried to connect to my home computer via samba yesterday...something that I do regularly, and was not allowed to connect. Samba has been running fine for +1 year on this machine with no problems.

In reviewing various google search results it seems that some how port 139 is now closed, which I guess would explain why I can no longer connect.

# nmap -p 139 -sT 192.155.0.*

Starting Nmap 6.01 ( http://nmap.org ) at 2012-06-30 12:18 EDT
Nmap scan report for 192.155.0.1

Nmap scan report for 192.155.0.122
Host is up (0.00010s latency).
PORT    STATE  SERVICE
139/tcp closed netbios-ssn

a little more

# nmap -sT 192.155.0.122

Starting Nmap 6.01 ( http://nmap.org ) at 2012-06-30 12:36 EDT
Nmap scan report for 192.155.0.122
Host is up (0.00015s latency).
Not shown: 998 closed ports
PORT     STATE SERVICE
111/tcp  open  rpcbind
6543/tcp open  mythtv

Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds

I did not have iptables installed...but following other suggestions I installed and found:

# iptables -vnL
Chain INPUT (policy ACCEPT 1867 packets, 2016K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 1298 packets, 107K bytes)
 pkts bytes target     prot opt in     out     source               destination

So, any ideas on how I get port 139 open again?

TIA

Jeff

Last edited by damacas (2012-07-03 01:02:34)

damacas · 2012-06-30 18:02:23

Downgraded samba 3.6.6-1 => 3.6.5-3 and all works again.

Anyone else notice strange things happening with this update?

Last edited by damacas (2012-06-30 18:03:01)

Gcool · 2012-07-01 07:56:02

Run "ss -ap" (with the problematic samba version obviously) and verify that the samba process is actually bound to a socket (and on the correct interface) and that no other processes are trying to listen on the same port.

Also, check the logs (/var/log/messages/log and /var/log/errors.log) for any clues.

damacas · 2012-07-02 16:17:52

Samba does not appear in any of the entries when I run ss -ap using the problematic samba version.

errors.log shows the following when I switch to newer version of samba

Jul  2 12:07:59 localhost smbd[16035]: [2012/07/02 12:07:59.536828,  0] auth/auth_util.c:707(get_guest_info3)
Jul  2 12:07:59 localhost smbd[16035]:   SamInfo3_for_guest: Unable to locate guest account [pcguest]!
Jul  2 12:07:59 localhost smbd[16035]: [2012/07/02 12:07:59.537265,  0] smbd/server.c:1235(main)
Jul  2 12:07:59 localhost smbd[16035]:   ERROR: failed to setup guest info.

Gcool · 2012-07-02 16:55:41

Judging from that output, I take it you have something amongst the lines of the following in your samba config:

guest account = pcguest

Double check that the "pcguest" account actually exists on your system

damacas · 2012-07-02 18:52:20

Yes, that was it. Apparently samba 3.6.5 didn't have a problem with accounts that were not setup in the system...however, 3.6.6 does.

Thanks for your help Gcool.

Inxsible · 2012-07-02 18:57:23

please mark as [SOLVED]...

Arch Linux

#1 2012-06-30 16:40:06

[SOLVED] Samba port closed?

#2 2012-06-30 18:02:23

Re: [SOLVED] Samba port closed?

#3 2012-07-01 07:56:02

Re: [SOLVED] Samba port closed?

#4 2012-07-02 16:17:52

Re: [SOLVED] Samba port closed?

#5 2012-07-02 16:55:41

Re: [SOLVED] Samba port closed?

#6 2012-07-02 18:52:20

Re: [SOLVED] Samba port closed?

#7 2012-07-02 18:57:23

Re: [SOLVED] Samba port closed?

Board footer