howard.kwasniewski@clorox.com
2003-Jan-15 21:09 UTC
[Samba] Samba and system 390 Unix system services
I am new to working with samba. We have used samba for years connecting our windows systems to Unix systems services on OS390. Starting in and around November 2002 we can no longer connect. I have gone through the troubleshooting techniques. Our Samba system is up running, the mount points are correct and the config file tested out correctly. If any one is doing this could you please forward some advice. Thanks, Howard
On Wed, 15 Jan 2003 howard.kwasniewski@clorox.com wrote:> I am new to working with samba. We have used samba for years connecting > our windows systems to Unix systems services on OS390. Starting in and > around November 2002 we can no longer connect. I have gone through the > troubleshooting techniques. Our Samba system is up running, the mount > points are correct and the config file tested out correctly. If any one is > doing this could you please forward some advice.I think that the USS port of Samba isn't a real supported one by the Samba team. But still, something probably has been changed and that resulted that Samba doesn't work anymore. You probably are best to look in the samba logs if you can see any error messages. Also letting this list know these logs, and also the level of samba, level of the clients,... will us the opportunity to help you out. Kind regards, Tim Verhoeven -- ==========================================================================Tim Verhoeven Linux & Open Source Specialist GSM : 0496 / 693 453 + e-business solutions Email : dj@4ict.com + consulting URL : www.sin.khk.be/~dj/ + Server consolidation ===========================================================================
howard.kwasniewski@clorox.com
2003-Jan-16 17:36 UTC
[Samba] Samba and system 390 Unix system services
Here is a copy of our Samba log. 10/14/02 05:47:33 dhcp-68-244.clorox.com (168.189.68.244) connect to service sysmgt as user BPXROOT (uid=0,gid=0) (pid 67108985) 10/14/02 05:47:39 dhcp-68-244.clorox.com (168.189.68.244) connect to service sysmgt as user BPXROOT (uid=0,gid=0) (pid 67108985) 10/14/02 05:48:54 dhcp-68-244.clorox.com (168.189.68.244) closed connection to service sysmgt 10/14/02 07:21:03 dhcp-68-244.clorox.com (168.189.68.244) connect to service sysmgt as user BPXROOT (uid=0,gid=0) (pid 67108985) 10/14/02 07:21:51 dhcp-68-244.clorox.com (168.189.68.244) closed connection to service sysmgt 10/14/02 12:14:33 dhcp-68-244.clorox.com (168.189.68.244) closed connection to service sysmgt accept: EDC5122I Input/output error.Got SIGHUP accept: EDC5122I Input/output error.Got SIGHUP Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed 11/01/02 04:19:23 dhcp-54-109.clorox.com (168.189.54.109) connect to service hostcomp as user BPXROOT (uid=0,gid=0) (pid 33555250) Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed 11/01/02 04:19:28 dhcp-54-109.clorox.com (168.189.54.109) connect to service hostcomp as user BPXROOT (uid=0,gid=0) (pid 33555250) 11/01/02 04:20:39 dhcp-54-109.clorox.com (168.189.54.109) closed connection to service hostcomp Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed 11/01/02 05:57:07 dhcp-54-109.clorox.com (168.189.54.109) connect to service hostcomp as user BPXROOT (uid=0,gid=0) (pid 33555250) 11/01/02 05:57:58 dhcp-54-109.clorox.com (168.189.54.109) closed connection to service hostcomp 11/01/02 11:03:10 dhcp-54-109.clorox.com (168.189.54.109) closed connection to service hostcomp Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed 11/08/02 07:15:26 dhcp-54-109.clorox.com (168.189.54.109) connect to service hostcomp as user BPXROOT (uid=0,gid=0) (pid 83886430) Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed 11/08/02 07:15:33 dhcp-54-109.clorox.com (168.189.54.109) connect to service hostcomp as user BPXROOT (uid=0,gid=0) (pid 83886430) 11/08/02 07:16:36 dhcp-54-109.clorox.com (168.189.54.109) closed connection to service hostcomp Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed Get_Hostbyname(dhcp-54-109.clorox.com): lookup failureMatchname failed 11/08/02 09:27:12 dhcp-54-109.clorox.com (168.189.54.109) connect to service hostcomp as user BPXROOT (uid=0,gid=0) (pid 83886430) 11/08/02 09:28:23 dhcp-54-109.clorox.com (168.189.54.109) closed connection to service hostcomp 11/08/02 11:05:12 dhcp-54-109.clorox.com (168.189.54.109) closed connection to service hostcomp accept: EDC5122I Input/output error.Got SIGHUP bind failed on port 139 (EDC8115I Address already in use.) Got SIGHUP Got SIGHUP 12/20/02 13:23:44 couldn't find service c 12/20/02 13:23:44 couldn't find service c Got SIGHUP accept: EDC5122I Input/output error.Got SIGHUP accept: EDC5122I Input/output error.Got SIGHUP Got SIGHUP <dj@4ict.com>@lists.samba.org on 01/16/2003 03:51:32 AM Sent by: samba-admin@lists.samba.org To: <howard.kwasniewski@clorox.com> cc: <samba@lists.samba.org> Subject: Re: [Samba] Samba and system 390 Unix system services On Wed, 15 Jan 2003 howard.kwasniewski@clorox.com wrote:> I am new to working with samba. We have used samba for years connecting > our windows systems to Unix systems services on OS390. Starting in and > around November 2002 we can no longer connect. I have gone through the > troubleshooting techniques. Our Samba system is up running, the mount > points are correct and the config file tested out correctly. If any oneis> doing this could you please forward some advice.I think that the USS port of Samba isn't a real supported one by the Samba team. But still, something probably has been changed and that resulted that Samba doesn't work anymore. You probably are best to look in the samba logs if you can see any error messages. Also letting this list know these logs, and also the level of samba, level of the clients,... will us the opportunity to help you out. Kind regards, Tim Verhoeven -- ==========================================================================Tim Verhoeven Linux & Open Source Specialist GSM : 0496 / 693 453 + e-business solutions Email : dj@4ict.com + consulting URL : www.sin.khk.be/~dj/ + Server consolidation ========================================================================== -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba