samba: unreachable - admin prohibited
Hi
SYS: redhat fedora 4, samba 3.0.14a-2
This is the first time I have had trouble configuring samba but I am completely stuck.
I have a basic smb.conf (see below) and testparm says it's fine. The path to the one share exists and the permissions a 0777. However no clients can reach it. Unix smbclient can not access it:
[root]# smbclient -L polaris
Error connecting to 194.200.237.132 (No route to host) Connection to polaris failed
Windows clients says permission denied and the network path was not found. NT4 server-manager sees the server but can't reach it. net rpc join fails with "Unable to find a suitable server"
tcpdump reports:
"unreachable - admin prohibited" when I listen on the interface for incoming traffic from a client.
I can ping the server from other hosts (by hostname if the host has the server in its hosts file or by IP otherwise) but I am pretty sure this is a network/access problem.
The one area I am not sure about is the firewall. I left this enabled during the install of redhat. The iptables are listed at the end of this mail. portscan shows 139 running with netbios-ssn so I am not sure if this means traffic is allowed through or not.
Does anyone have any ideas?
Thanx.
Dp.
============== iptables ================
Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere
Chain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhere
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain RH-Firewall-1-INPUT (2 references)
target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmp any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT ipv6-auth-- anywhere anywhere ACCEPT udp -- anywhere 224.0.0.251 udp
dpt:5353
ACCEPT udp -- anywhere anywhere udp
dpt:ipp
ACCEPT all -- anywhere anywhere state
RELATED,ESTABLISHED
ACCEPT tcp -- anywhere anywhere state
NEW tcp dpt:ssh
ACCEPT tcp -- anywhere anywhere state
NEW tcp dpt:http
ACCEPT tcp -- anywhere anywhere state
NEW tcp dpt:ftp
ACCEPT tcp -- anywhere anywhere state
NEW tcp dpt:smtp
REJECT all -- anywhere anywhere reject-
with icmp-host-prohibited
=============== End iptables ============
=======smb.conf ==========
[global]
workgroup = mygroup
server string = 132
netbios name = polaris
#hosts allow = 196.218.237.128/255.255.255.128 printcap name = /etc/printcap
#load printers = yes
cups options = raw
guest account = samba
log file = /var/log/samba/%m.log
max log size = 50
security = domain
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = no
default case = lower
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
template shell = /bin/false
winbind use default domain = yes
[share]
comment = scanning drive
path = /data/share
public = yes
writable = yes
create mask = 0777
browseable = yes
=============== end of smb.conf ==========
Hi Dermot
On Fri, July 29, 2005 12:10 pm, Dermot Paikkos wrote:
[...snipped...]
Quoted 3 lines
tcpdump reports:
"unreachable - admin prohibited" when I listen on the interface for incoming traffic from a client.
It's a firewall issue, not a Samba issue. This message basically means that there is an IPTables rule which prevents access to that port.
J
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 4 lines · Scott Taylor
Quoted 2 lines · Dermot Paikkos
Hi
Quoted 9 lines
Quoted 6 lines
The one area I am not sure about is the firewall. I left this enabled during the install of redhat. The iptables are listed at the end of this mail. portscan shows 139 running with netbios-ssn so I am not sure if this means traffic is allowed through or not.
Does anyone have any ideas?
I don't see any SMB or NMB allowed in your IPTABLES rulez.
I guess the next question is how do I add a rule for smb and nmb or can I just turn it off to confirm that this is the source of the problem?
Quoted 30 lines
Quoted 16 lines
============== iptables ================
Chain FORWARD (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhereChain INPUT (policy ACCEPT)
target prot opt source destination
RH-Firewall-1-INPUT all -- anywhere anywhereChain OUTPUT (policy ACCEPT)
target prot opt source destinationChain RH-Firewall-1-INPUT (2 references)
target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT icmp -- anywhere anywhere icmpQuoted 13 lines
any ACCEPT ipv6-crypt-- anywhere anywhere ACCEPT
ipv6-auth-- anywhere anywhere ACCEPT udp --
anywhere 224.0.0.251 udp dpt:5353 ACCEPT udp
-- anywhere anywhere udp dpt:ipp ACCEPT
all -- anywhere anywhere state
RELATED,ESTABLISHED ACCEPT tcp -- anywhere
anywhere state NEW tcp dpt:ssh ACCEPT tcp --
anywhere anywhere state NEW tcp dpt:http
ACCEPT tcp -- anywhere anywhere state
NEW tcp dpt:ftp ACCEPT tcp -- anywhere anywhere
state NEW tcp dpt:smtp REJECT all -- anywhere
anywhere reject- with icmp-host-prohibited
Quoted 3 lines
--
Scott
~~
Dermot Paikkos * [email protected]
Network Administrator @ Science Photo Library
Phone: 0207 432 1100 * Fax: 0207 286 8668
Quoted 11 lines · Dermot Paikkos
Quoted 9 lines · Scott Taylor
Quoted 7 lines · Dermot Paikkos
Hi
The one area I am not sure about is the firewall. I left this enabled during the install of redhat. The iptables are listed at the end of this mail. portscan shows 139 running with netbios-ssn so I am not sure if this means traffic is allowed through or not.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Does anyone have any ideas?
I don't see any SMB or NMB allowed in your IPTABLES rulez.
I guess the next question is how do I add a rule for smb and nmb or can I just turn it off to confirm that this is the source of the problem?
Firewall rules are set in the "setup" program in your distro, if I recall correctly. To check if the firewall is indeed the culprit, try this:/usr/sbin/iptables -F
That will wipe the firewall temporarily, not including the NAT and mangle tables (in case your box works as a gateway). To clean the NAT and mangle tables too, use these:/usr/sbin/iptables -t nat -F/usr/sbin/iptables -t mangle -F
J
Quoted 6 lines · Jens Knoell
Quoted 3 lines · Dermot Paikkos
I guess the next question is how do I add a rule for smb and nmb or can I just turn it off to confirm that this is the source of the problem?
Quoted 8 lines
Firewall rules are set in the "setup" program in your distro, if I recall correctly. To check if the firewall is indeed the culprit, try
this:/usr/sbin/iptables-FThat will wipe the firewall temporarily, not including the NAT and mangle tables (in case your box works as a gateway). To clean the NAT and mangle tables too, use these:
/usr/sbin/iptables-t nat -F/usr/sbin/iptables-t mangle -F
Well something has changed as I seem to be getting through;
[root@proxima ~]# smbclient -L polaris Password:
session setup failed: NT_STATUS_CANT_ACCESS_DOMAIN_INFO
This looks like the samba server isn't communicting with the PDC. so then;
Quoted 1 line
net rpc join mydomain -U administrator%password
Joined domain SPL.
Quoted 1 line
[root@proxima ~]# smbclient -L polaris
Password:
session setup failed: NT_STATUS_LOGON_FAILURE
A better error. The windows client can finally see it.
Thanx Jens & Scott. I guess I'll have to rtfm to configure the iptables or turn them off.
Dp.
A message that is not in the archive (sent off-list or not yet received): 42EA9A54.3516.CAC929@localhost
Quoted 4 lines · Dermot Paikkos
Yes, found it. Not in the place your'd expect it.
Disabled now. I guess I don't have to print out the iptable man pages :-).
Good thing you didn't try that, there is no man page, only "info" (the new man?) pages. :(
Quoted 1 line
Thanx scott.
You are welcome. Happy weekend. :)
--
Scott