[Samba] Impossible to access folders
Thomas Vito
shoktai at gmail.com
Wed Jul 23 12:01:28 GMT 2008
Thanks Rubin. I am kinda of desperate right now with Samba.
[root at amsdev-dv09 ~]# ps aux|grep smb
root 4543 0.0 0.1 17480 3336 ? Ss Jul22 0:00 smbd -D
root 5094 0.0 0.0 17480 1484 ? S Jul22 0:00 smbd -D
root 27818 0.0 0.0 3912 656 pts/2 R+ 13:56 0:00 grep smb
[root at amsdev-dv09 ~]# smbstatus -v 10
using configfile = /etc/samba/smb.conf
Samba version 3.0.28-1.el5_2.1
PID Username Group Machine
-------------------------------------------------------------------
Opened /var/cache/samba/connections.tdb
Service pid machine Connected at
-------------------------------------------------------
No locked files
[root at amsdev-dv09 ~]# service smb status
smbd (pid 27883 27882 27820 27819 5094 4543) is running...
nmbd (pid 4546) is running...
[root at amsdev-dv09 ~]# /etc/init.d/iptables stop
Flushing firewall rules: [ OK ]
Setting chains to policy ACCEPT: filter [ OK ]
Unloading iptables modules: [ OK ]
I promise i have changed anything ;)
2008/7/23 Rubin Bennett <rbennett at thatitguy.com>:
>
> On Wed, 2008-07-23 at 09:57 +0200, Thomas Vito wrote:
> > Well, what i meant (i was not very clear) is that i could access for a
> > while the share but after a system restart (and i haven't changed
> > anything to my setup, i just wanted to reboot to see what happens), i
> > am now unable to access the share anymore.
> >
> Well that's what you get for rebooting :^P
>
> I guess at this point I'd try a smbstatus and make sure that Samba is in
> fact running and correctly. If it was working and it's not now after a
> reboot, you're basically going to have to start your troubleshooting all
> over again. *something* changed, or it would be working like it was
> before the reboot :)
>
> If nothing changed in your smbd.conf and you're not able to access the
> share, I would look at things external to samba. Again the most likely
> are things like iptables etc..
>
> IIRC testparm will run even if smbd is not started.
>
> Rubin
>
> > The smbd.log file contains:
> >
> >
> > [2008/07/23 09:48:17, 0] lib/util_sock.c:get_peer_addr(1224)
> > getpeername failed. Error was Transport endpoint is not connected
> > [2008/07/23 09:48:17, 0] lib/util_sock.c:get_peer_addr(1224)
> > getpeername failed. Error was Transport endpoint is not connected
> > [2008/07/23 09:48:17, 0]
> > auth/auth_util.c:create_builtin_administrators(792)
> > create_builtin_administrators: Failed to create Administrators
> > [2008/07/23 09:48:17, 0] auth/auth_util.c:create_builtin_users(758)
> > create_builtin_users: Failed to create Users
> >
> > I have checked iptables:
> >
> > [root at amsdev-dv09 ~]# iptables -L
> > Chain INPUT (policy ACCEPT)
> > target prot opt source destination
> >
> > Chain FORWARD (policy ACCEPT)
> > target prot opt source destination
> >
> > Chain OUTPUT (policy ACCEPT)
> > target prot opt source destination
> >
> > And tested smb.conf:
> >
> > [root at amsdev-dv09 ~]# testparm
> > Load smb config files from /etc/samba/smb.conf
> > Processing section "[share]"
> > Loaded services file OK.
> > Server role: ROLE_STANDALONE
> > Press enter to see a dump of your service definitions
> >
> > [global]
> > workgroup = ACME
> > realm = EU.ACME.COM
> > server string = %h
> > security = SHARE
> > passdb backend = tdbsam
> > username map = /etc/samba/smbusers
> > local master = No
> > dns proxy = No
> > wins server = 10.130.12.120
> > ldap ssl = no
> > cups options = raw
> >
> > [share]
> > path = /home/acn/share
> > read only = No
> > guest ok = Yes
> >
> > [root at amsdev-dv09 ~]# smbd -V
> > Version 3.0.28-1.el5_2.1
> >
> >
> > 2008/7/22 Rubin Bennett <rbennett at thatitguy.com>:
> > On Tue, 2008-07-22 at 12:25 +0200, Thomas Vito wrote:
> > > I changed the share name. I was able to access the share
> > finally. I am
> > > now getting those errors after a sytem reboot:
> > > [2008/07/22 12:21:49, 0] lib/util_sock.c:get_peer_addr(1224)
> > > getpeername failed. Error was Transport endpoint is not
> > connected
> > > [2008/07/22 12:22:13, 0] lib/util_sock.c:write_data(562)
> > > write_data: write failure in writing to client
> > 10.130.101.85. Error
> > > Connection reset by peer
> > > [2008/07/22 12:22:13, 0] lib/util_sock.c:send_smb(761)
> > > Error writing 4 bytes to client. -1. (Connection reset by
> > peer)
> > >
> > >
> > > On the XP side i get the network path was not found.
> > >
> >
> >
> > The 'endpoint is not connected' errors are common; I see them
> > all over
> > the place without impacting functionality. I've researched
> > those and
> > they seem to be largely ignored.
> >
> > So you can access the shares, but I'm not clear on what client
> > you're
> > using if XP still doesn't work? smbclient? from localhost?
> > So Windows
> > clients universally cannot access the share, or do you have
> > some that
> > can (i.e. Win2k works but XP does not)?
> >
> > If nothing but the local machine can access the share I'd be
> > very
> > suspicious that there is still some firewalling on the server:
> > iptables -L
> > should return something like this:
> > Chain INPUT (policy ACCEPT)
> > target prot opt source destination
> >
> > Chain FORWARD (policy ACCEPT)
> > target prot opt source destination
> >
> > Chain OUTPUT (policy ACCEPT)
> > target prot opt source destination
> >
> > If your iptables returned much more then
> > run /etc/init.d/iptables stop
> > (presuming you're on a RedHat-ish system).
> >
> > If some clients can access but others can't we'll have to dig
> > a little
> > deeper.
> >
> > Rubin
> >
> >
> > > XP is online they can ping with the samba server. The samba
> > server has
> > > the firewall disabled and Selinux disabled too. I have read
> > on some
> > > other ports that it could be a port issue. Any ideas?
> > >
> > > Thank you
> > >
> > > 2008/7/22 Rubin Bennett <rbennett at thatitguy.com>:
> > > I've actually seen this a number of times.
> > >
> > > Change your share name in smb.conf from [Share] to
> > [share] and
> > > I'll bet
> > > it works fine.
> > >
> > > I haven't picked it apart as to why this happens,
> > but it seems
> > > like
> > > there's something about the case sensitivity/
> > insensitivity
> > > between *nix
> > > and *doze that disagree when the share is defined
> > with mixed
> > > case.
> > >
> > > Has anyone else seen this besides me? It seems
> > fairly
> > > consistent
> > > between versions and flavors of Linux and Samba in
> > my
> > > experience.
> > >
> > > HTH,
> > > Rubin
> > >
> > >
> > > On Mon, 2008-07-21 at 22:30 -0500, Adam Williams
> > wrote:
> > > > are you trying to connect to \\server\acn or \
> > \server\share?
> > > >
> > > > Thomas Vito wrote:
> > > > > Hello,
> > > > >
> > > > > On a RHEL 5 U2 server i am trying again to setup
> > samba
> > > this time in user
> > > > > mode, see smb.conf below:
> > > > >
> > > > > [global]
> > > > > workgroup = ACME
> > > > > realm = EU.ACME.COM
> > > > > server string = %h
> > > > > password server =
> > amsterdam-dc01.eu.acme.com
> > > > > passdb backend = tdbsam
> > > > > local master = No
> > > > > dns proxy = No
> > > > > wins server = 10.130.12.120
> > > > > ldap ssl = no
> > > > > idmap uid = 16777216-33554431
> > > > > idmap gid = 16777216-33554431
> > > > > cups options = raw
> > > > >
> > > > > [printers]
> > > > > comment = All Printers
> > > > > path = /var/spool/samba
> > > > > printable = Yes
> > > > > browseable = No
> > > > >
> > > > > [Share]
> > > > > path = /home/acn
> > > > > write list = acn, tci
> > > > > read only = No
> > > > > guest ok = Yes
> > > > >
> > > > > I have created two users acn and tci then used
> > smbpasswd
> > > to create their
> > > > > password.
> > > > > I have created the share folder on the samba
> > > folder /home/acn and even tried
> > > > > a chmod 777 on it.
> > > > > Each time i try to connect to the share i get
> > either an
> > > error from windows
> > > > > client : No network provider accepted the given
> > network
> > > path. Sometimes i
> > > > > get a login prompt, enter my cred tci and
> > password, then
> > > after a few minutes
> > > > > i get The specified network name is no longer
> > available
> > > > >
> > > > > Here is the smbd.log:
> > > > >
> > > > > [2008/07/21 17:17:31, 0]
> > > lib/util_sock.c:get_peer_addr(1224)
> > > > > getpeername failed. Error was Transport
> > endpoint is not
> > > connected
> > > > > [2008/07/21 17:17:31, 0]
> > > lib/util_sock.c:get_peer_addr(1224)
> > > > > getpeername failed. Error was Transport
> > endpoint is not
> > > connected
> > > > > [2008/07/21 17:17:31, 0]
> > lib/util_sock.c:read_data(534)
> > > > > read_data: read failure for 4 bytes to client
> > 0.0.0.0.
> > > Error = Connection
> > > > > reset by peer
> > > > >
> > > > > [root at amsdev-dv09 ~]# smbd -V
> > > > > Version 3.0.28-1.el5_2.1
> > > > >
> > > >
> > >
> > > --
> > > Rubin Bennett
> > > RB Technologies
> > > http://thatitguy.com
> > > rbennett at thatitguy.com
> > > (802)223-4448
> > >
> > > "They that can give up essential liberty to obtain a
> > little
> > > temporary security deserve neither liberty nor
> > safety"
> > > --Benjamin Franklin, Historical Review of
> > Pennsylvania, 1759
> > >
> > >
> > > --
> > > To unsubscribe from this list go to the following
> > URL and read
> > > the
> > > instructions:
> > https://lists.samba.org/mailman/listinfo/samba
> > >
> > >
> >
> > --
> >
> > Rubin Bennett
> > RB Technologies
> > http://thatitguy.com
> > rbennett at thatitguy.com
> > (802)223-4448
> >
> > "They that can give up essential liberty to obtain a little
> > temporary security deserve neither liberty nor safety"
> > --Benjamin Franklin, Historical Review of Pennsylvania, 1759
> >
> >
> > --
> > To unsubscribe from this list go to the following URL and read
> > the
> > instructions: https://lists.samba.org/mailman/listinfo/samba
> >
> >
> >
> --
> Rubin Bennett
> RB Technologies
> http://thatitguy.com
> rbennett at thatitguy.com
> (802)223-4448
>
> "They that can give up essential liberty to obtain a little
> temporary security deserve neither liberty nor safety"
> --Benjamin Franklin, Historical Review of Pennsylvania, 1759
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/listinfo/samba
>
More information about the samba
mailing list