Chunduru, Krishnachaithanya
2017-Aug-16 09:34 UTC
[Samba] FW: Samba access problem after upgrading the host OS
Hi All, Recently I have migrated my host OS from Aix 6.1 to Aix 7.1, after upgrade the users are having access problem to the shares as they have mapped to network drives. I have added the user IP address in the smb.conf "hosts allow" and the /etc/hosts.allow file. But still the users are not able to connect to the server. I'm able to telnet the ports 139 and 445 but the ports 137,138 are not connecting. The error screenshot says " XXXX is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The account is not authorized to login in from this station." The log shows the below entries. [2017/08/16 03:43:23, 1] lib/util_sock.c:get_peer_name(1191) Gethostbyaddr failed for XXXX [2017/08/16 03:43:23, 2] lib/access.c:check_access(323) Allowed connection from XXXX (XXXX) [2017/08/16 03:43:37, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client XXXX. Error = Connection reset by peer [2017/08/16 05:26:15, 1] lib/util_sock.c:get_peer_name(1191) Gethostbyaddr failed for XXXX [2017/08/16 05:26:15, 2] lib/access.c:check_access(323) Allowed connection from XXXX (XXXX) [2017/08/16 05:26:28, 0] lib/util_sock.c:read_data(534) read_data: read failure for 4 bytes to client XXXX. Error = Connection reset by peer Can someone please help on these issue. Regards, Krishna This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Rowland Penny
2017-Aug-16 09:56 UTC
[Samba] FW: Samba access problem after upgrading the host OS
On Wed, 16 Aug 2017 15:04:52 +0530 "Chunduru, Krishnachaithanya via samba" <samba at lists.samba.org> wrote:> Hi All, > > Recently I have migrated my host OS from Aix 6.1 to Aix 7.1, after > upgrade the users are having access problem to the shares as they > have mapped to network drives. >What version of Samba where you using and what are using now ? And, as usual, can you post your smb.conf Rowland
Chunduru, Krishnachaithanya
2017-Aug-16 10:36 UTC
[Samba] FW: Samba access problem after upgrading the host OS
Hi,
I didn't updated my samba version on this server. I was using the same old
version pware.samba-3.0.28.rte. Nothing was changed from the samba side.
-bash-4.2$ cat /usr/local/samba/lib/smb.conf
[global]
workgroup = ICCAN
server string = XXXX
encrypt passwords = No
passdb backend = tdbsam
log file = /var/log/samba/%m.log
log level = 2
max log size = 2000
preferred master = No
local master = No
domain master = No
domain logons = No
dns proxy = No
wins server = XXXX, XXXX
hosts allow = XXXX.,
[dms]
comment = DMS
path = /apps/dms
read only = no
force user = nfoprint
force group = dms
force create mode = 0770
force directory mode = 2770
inherit permissions = yes
guest ok = no
browseable = yes
valid users = @dms
hide special files = yes
printable = no
[dms2]
comment = DMSv2
path = /apps/dms2
read only = no
force user = nfopr2
force group = dms2
force create mode = 0770
force directory mode = 2770
inherit permissions = yes
guest ok = no
browseable = yes
valid users = @dms2
hide special files = yes
printable = no
[music]
comment = MUSIC
path = /apps/music
read only = no
force group = music
force create mode = 0760
force directory mode = 2770
inherit permissions = yes
guest ok = no
browseable = yes
valid users = @music
hide special files = yes
printable = no
[musicqa]
comment = MUSICQA
path = /apps/music_qa
read only = no
force group = musicqa
force create mode = 0760
force directory mode = 2770
inherit permissions = yes
guest ok = no
browseable = yes
valid users = @musicqa
hide special files = yes
printable = no
[printers]
comment = All Printers
path = /usr/spool/samba
printable = Yes
browseable = No
[tmp]
comment = Temporary file space
path = /tmp
read only = No
I'm working on upgrade the samba to 4.5.7 on my test server, if that is
working then I will try to integrate it with AD.
Regards,
Krishna
-----Original Message-----
From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland Penny
via samba
Sent: Wednesday, August 16, 2017 3:27 PM
To: samba at lists.samba.org
Subject: Re: [Samba] FW: Samba access problem after upgrading the host OS
On Wed, 16 Aug 2017 15:04:52 +0530
"Chunduru, Krishnachaithanya via samba" <samba at
lists.samba.org> wrote:
> Hi All,
>
> Recently I have migrated my host OS from Aix 6.1 to Aix 7.1, after
> upgrade the users are having access problem to the shares as they have
> mapped to network drives.
>
What version of Samba where you using and what are using now ?
And, as usual, can you post your smb.conf
Rowland
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.