FW: Netware Client 4.2.0 password generate problems
Just got off the phone with Tivoli level l. Seems to be if I use a password like 1xyx it works as designed but if I use xyx1 or xyx is does not work. I'm off to level 2 land. -Original Message- From: Jim Kirkman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 28, 2001 8:49 AM To: [EMAIL PROTECTED] Subject: Re: Netware Client 4.2.0 password generate problems Yes, I have experienced this very same behavior. Given that it was happening during testing of Netware cluster backups I quickly canned 4.2 and went back to 4.1.1_18. I've got enough problems trying to get the cluster nodes to run successfully to have to worry about this as well. I like Corey's response, just shrug and say Netware Patrick Boutilier wrote: Has anybody got password generate working properly with the new 4.2.0 client on Netware? I am using Netware 5.1 SP2 and I can not get the Node password to be saved in the new tsm.pwd file. The TSA and NDS username/password are save fine but everytime I run dsmc q sess I am asked for the Node password. dsmc q TSA and dsmc q TSA NDS work fine (other than having to provide the Node password each time). I do have passwordaccess generate in my dsm.opt file. Anyone else noticed this behaviour? -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Antwort: Re: Netware Client 4.2.0 password generate problems
Hello, I have similar symptoms with the TSM 4.2 client for Linux. I opened a problem record with IBM. Please do the same, because the more problem records exists, the earlier the problem might get fixed. Best regards Gerhard Gerhard Rentschler email: [EMAIL PROTECTED] Manager Central Servers Services Regional Computing Center tel: ++49/711/6855806 University of Stuttgartfax: ++49/711/682357 Allmandring 30a D 70550 Stuttgart Germany Jim Kirkman [EMAIL PROTECTED] Gesendet von: ADSM: Dist Stor Manager [EMAIL PROTECTED] 28.08.2001 14:48 Bitte antworten an jim_kirkman An: [EMAIL PROTECTED] Kopie: Thema: Re: Netware Client 4.2.0 password generate problems Yes, I have experienced this very same behavior. Given that it was happening during testing of Netware cluster backups I quickly canned 4.2 and went back to 4.1.1_18. I've got enough problems trying to get the cluster nodes to run successfully to have to worry about this as well. I like Corey's response, just shrug and say Netware Patrick Boutilier wrote: Has anybody got password generate working properly with the new 4.2.0 client on Netware? I am using Netware 5.1 SP2 and I can not get the Node password to be saved in the new tsm.pwd file. The TSA and NDS username/password are save fine but everytime I run dsmc q sess I am asked for the Node password. dsmc q TSA and dsmc q TSA NDS work fine (other than having to provide the Node password each time). I do have passwordaccess generate in my dsm.opt file. Anyone else noticed this behaviour? -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: Netware Client 4.2.0 password generate problems
speaking of things Netwarish, there seems to be an issue with backing up folders, and maybe files, with an underscore(_) in the name, as in zfs_agnt or _netware. anyone else...? seems specific to cluster nodes but not 100% sure about that. Gerhard Rentschler wrote: Hello, I have similar symptoms with the TSM 4.2 client for Linux. I opened a problem record with IBM. Please do the same, because the more problem records exists, the earlier the problem might get fixed. Best regards Gerhard An: [EMAIL PROTECTED] Kopie: Thema: Re: Netware Client 4.2.0 password generate problems Yes, I have experienced this very same behavior. Given that it was happening during testing of Netware cluster backups I quickly canned 4.2 and went back to 4.1.1_18. I've got enough problems trying to get the cluster nodes to run successfully to have to worry about this as well. I like Corey's response, just shrug and say Netware Patrick Boutilier wrote: Has anybody got password generate working properly with the new 4.2.0 client on Netware? I am using Netware 5.1 SP2 and I can not get the Node password to be saved in the new tsm.pwd file. The TSA and NDS username/password are save fine but everytime I run dsmc q sess I am asked for the Node password. dsmc q TSA and dsmc q TSA NDS work fine (other than having to provide the Node password each time). I do have passwordaccess generate in my dsm.opt file. Anyone else noticed this behaviour? -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884 -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Re: Netware Client 4.2.0 password generate problems
There appears to be a limit of 8 characters for NSS volumes - don't know if this is what you were trying to do? As for the password generate thing, it's works fine here using 5.1 and 4.2 Rob [EMAIL PROTECTED] 28/08/2001 16:05:10 speaking of things Netwarish, there seems to be an issue with backing up folders, and maybe files, with an underscore(_) in the name, as in zfs_agnt or _netware. anyone else...? seems specific to cluster nodes but not 100% sure about that. Gerhard Rentschler wrote: Hello, I have similar symptoms with the TSM 4.2 client for Linux. I opened a problem record with IBM. Please do the same, because the more problem records exists, the earlier the problem might get fixed. Best regards Gerhard An: [EMAIL PROTECTED] Kopie: Thema: Re: Netware Client 4.2.0 password generate problems Yes, I have experienced this very same behavior. Given that it was happening during testing of Netware cluster backups I quickly canned 4.2 and went back to 4.1.1_18. I've got enough problems trying to get the cluster nodes to run successfully to have to worry about this as well. I like Corey's response, just shrug and say Netware Patrick Boutilier wrote: Has anybody got password generate working properly with the new 4.2.0 client on Netware? I am using Netware 5.1 SP2 and I can not get the Node password to be saved in the new tsm.pwd file. The TSA and NDS username/password are save fine but everytime I run dsmc q sess I am asked for the Node password. dsmc q TSA and dsmc q TSA NDS work fine (other than having to provide the Node password each time). I do have passwordaccess generate in my dsm.opt file. Anyone else noticed this behaviour? -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884 -- Jim Kirkman AIS - Systems UNC-Chapel Hill 966-5884
Netware Client 4.2.0 password generate problems
Has anybody got password generate working properly with the new 4.2.0 client on Netware? I am using Netware 5.1 SP2 and I can not get the Node password to be saved in the new tsm.pwd file. The TSA and NDS username/password are save fine but everytime I run dsmc q sess I am asked for the Node password. dsmc q TSA and dsmc q TSA NDS work fine (other than having to provide the Node password each time). I do have passwordaccess generate in my dsm.opt file. Anyone else noticed this behaviour?
