I have problems ( can�t login ) to login to all NetWare FTP servers after installing SS 2.0.1 ( and no change after installing 2.0.2 ). Same problem is with NetWare Screen Saver on NW 6.5 servers.
![]() |
0 |
![]() |
I am not sure about FTP. But I know the scrsaver works. I have servers running edir881 and ss202 and i unlock scrsaver all the time. I am running nw65sp5
![]() |
0 |
![]() |
> I am not sure about FTP. But I know the scrsaver works. I have servers > running edir881 and ss202 and i unlock scrsaver all the time. I am running > nw65sp5 > Jeff, I�m on eDir 8.7.3.8, there is a problem. David
![]() |
0 |
![]() |
bambid@email.cz wrote: > I have problems ( can4t login ) to login to all NetWare FTP servers > after installing SS 2.0.1 ( and no change after installing 2.0.2 ). > Same problem is with NetWare Screen Saver on NW 6.5 servers. Renaming nmas.nlm solved all problems. But this isn?t solution for me. -- With XanaNews 1.18.1.3 on 22.8.2006 12:32:46 David
![]() |
0 |
![]() |
I skipped edir8738 and went to 881. On Tue, 22 Aug 2006 06:54:40 +0000, bambid wrote: >> I am not sure about FTP. But I know the scrsaver works. I have servers >> running edir881 and ss202 and i unlock scrsaver all the time. I am > running >> nw65sp5 >> > > Jeff, > I�m on eDir 8.7.3.8, there is a problem. > > David
![]() |
0 |
![]() |
Bambid wrote: > bambid@email.cz wrote: > > > I have problems ( can4t login ) to login to all NetWare FTP servers > > after installing SS 2.0.1 ( and no change after installing 2.0.2 ). > > Same problem is with NetWare Screen Saver on NW 6.5 servers. > > Renaming nmas.nlm solved all problems. But this isn?t solution for me. Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. -- With XanaNews 1.18.1.3 on 22.8.2006 18:23:21 David
![]() |
0 |
![]() |
Hi, I tested it as well, and its definately working fine. The only thing is if the user has Universal Password enabled, you have to provide the passwords with the correct cases. So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD definately handles the cases fine... Cheers, Akos Bambid wrote: > Bambid wrote: > >> bambid@email.cz wrote: >> >> > I have problems ( can4t login ) to login to all NetWare FTP servers >> > after installing SS 2.0.1 ( and no change after installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver on NW 6.5 servers. >> >> Renaming nmas.nlm solved all problems. But this isn?t solution for me. > > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. >
![]() |
0 |
![]() |
Akos Szechy wrote: > Hi, > > I tested it as well, and its definately working fine. The only thing > is if the user has Universal Password enabled, you have to provide > the passwords with the correct cases. > > So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD definately > handles the cases fine... > > Cheers, Akos > > Bambid wrote: > > > Bambid wrote: > > > >> bambid@email.cz wrote: > >> > >> > I have problems ( can4t login ) to login to all NetWare FTP > servers >> > after installing SS 2.0.1 ( and no change after > installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver > on NW 6.5 servers. >> > >> Renaming nmas.nlm solved all problems. But this isn?t solution for > me. > > > > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. > > Hi Alois, I my setup I had tryed everything possible with UP, I created password policy without UP enabled too. Users that I used to login to FTP server and / or ScreenSaver console haven?t UP enabled or haven?t any password policy and still wasn?t possible to login. After downgrade NMAS to 2.4.0 version all this problems gone. I had some interesting side effect, I use Novell Border Manager and had major problems with single sign-on via Client Trust. After NMAS downgrade all problems were solved. -- With XanaNews 1.18.1.3 on 23.8.2006 10:05:37 David
![]() |
0 |
![]() |
Hi, Well, I can only say that its also working for me, so I would suggest to open an SR with Novell, if you want this solved for the future... Thanks, Akos Bambid wrote: > Akos Szechy wrote: > >> Hi, >> >> I tested it as well, and its definately working fine. The only thing >> is if the user has Universal Password enabled, you have to provide >> the passwords with the correct cases. >> >> So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD definately >> handles the cases fine... >> >> Cheers, Akos >> >> Bambid wrote: >> >> > Bambid wrote: >> > >> >> bambid@email.cz wrote: >> >> >> >> > I have problems ( can4t login ) to login to all NetWare FTP >> servers >> > after installing SS 2.0.1 ( and no change after >> installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver >> on NW 6.5 servers. >> >> >> Renaming nmas.nlm solved all problems. But this isn?t solution for >> me. >> > >> > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. >> > > > Hi Alois, > I my setup I had tryed everything possible with UP, I created password > policy without UP enabled too. > > Users that I used to login to FTP server and / or ScreenSaver console > haven?t UP enabled or haven?t any password policy and still wasn?t > possible to login. After downgrade NMAS to 2.4.0 version all this > problems gone. > > I had some interesting side effect, I use Novell Border Manager and had > major problems with single sign-on via Client Trust. After NMAS > downgrade all problems were solved. >
![]() |
0 |
![]() |
No, this is a known issue (at least the screen saver part). Screen saver does you the service of capitalizing all characters in your password when using NMAS for some reason, or something like that. Checking for TID....guess I can't find one right now. May need to write one. Anyway, the scrsaver.nlm that comes with OES SP2 (NW 6.5.6) should have this fixed. There is already a bug entered and resolved so it may be released on its own as well but I doubt it. As a temporary work around I believe you can create a new UP policy, have it explicitly say that no UP will be set, and assign that to the user unlocking the screen. This is often an admin who does not need a UP anyway. Good luck. > Hi, > > Well, I can only say that its also working for me, so I would suggest to > open an SR with Novell, if you want this solved for the future... > > Thanks, Akos > > Bambid wrote: > > > Akos Szechy wrote: > > > >> Hi, > >> > >> I tested it as well, and its definately working fine. The only thing > >> is if the user has Universal Password enabled, you have to provide > >> the passwords with the correct cases. > >> > >> So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD definately > >> handles the cases fine... > >> > >> Cheers, Akos > >> > >> Bambid wrote: > >> > >> > Bambid wrote: > >> > > >> >> bambid@email.cz wrote: > >> >> > >> >> > I have problems ( can4t login ) to login to all NetWare FTP > >> servers >> > after installing SS 2.0.1 ( and no change after > >> installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver > >> on NW 6.5 servers. >> > >> >> Renaming nmas.nlm solved all problems. But this isn?t solution for > >> me. > >> > > >> > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. > >> > > > > > Hi Alois, > > I my setup I had tryed everything possible with UP, I created password > > policy without UP enabled too. > > > > Users that I used to login to FTP server and / or ScreenSaver console > > haven?t UP enabled or haven?t any password policy and still wasn?t > > possible to login. After downgrade NMAS to 2.4.0 version all this > > problems gone. > > > > I had some interesting side effect, I use Novell Border Manager and had > > major problems with single sign-on via Client Trust. After NMAS > > downgrade all problems were solved. > > >
![]() |
0 |
![]() |
As another note may also be able to use upper-case password to get around it... Good luck. > Hi, > > Well, I can only say that its also working for me, so I would suggest to > open an SR with Novell, if you want this solved for the future... > > Thanks, Akos > > Bambid wrote: > > > Akos Szechy wrote: > > > >> Hi, > >> > >> I tested it as well, and its definately working fine. The only thing > >> is if the user has Universal Password enabled, you have to provide > >> the passwords with the correct cases. > >> > >> So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD definately > >> handles the cases fine... > >> > >> Cheers, Akos > >> > >> Bambid wrote: > >> > >> > Bambid wrote: > >> > > >> >> bambid@email.cz wrote: > >> >> > >> >> > I have problems ( can4t login ) to login to all NetWare FTP > >> servers >> > after installing SS 2.0.1 ( and no change after > >> installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver > >> on NW 6.5 servers. >> > >> >> Renaming nmas.nlm solved all problems. But this isn?t solution for > >> me. > >> > > >> > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. > >> > > > > > Hi Alois, > > I my setup I had tryed everything possible with UP, I created password > > policy without UP enabled too. > > > > Users that I used to login to FTP server and / or ScreenSaver console > > haven?t UP enabled or haven?t any password policy and still wasn?t > > possible to login. After downgrade NMAS to 2.4.0 version all this > > problems gone. > > > > I had some interesting side effect, I use Novell Border Manager and had > > major problems with single sign-on via Client Trust. After NMAS > > downgrade all problems were solved. > > >
![]() |
0 |
![]() |
Its a known issue with screen saver and nwconfig. Both should be fixed in SP6. The workaround is correct :-) However, I tested with NWFTPD and its not a problem there. Even if you specify "Novell", you have to use "Novell" with FTP client, so it does not accept "novell"...so, its definately UP enabled. Cheers, Akos ab@novell.com wrote: > No, this is a known issue (at least the screen saver part). Screen saver > does you the service of capitalizing all characters in your password when > using NMAS for some reason, or something like that. Checking for > TID....guess I can't find one right now. May need to write one. Anyway, > the scrsaver.nlm that comes with OES SP2 (NW 6.5.6) should have this > fixed. > There is already a bug entered and resolved so it may be released on its > own as well but I doubt it. > > As a temporary work around I believe you can create a new UP policy, have > it explicitly say that no UP will be set, and assign that to the user > unlocking the screen. This is often an admin who does not need a UP > anyway. > > Good luck. > > > > > >> Hi, >> >> Well, I can only say that its also working for me, so I would suggest to >> open an SR with Novell, if you want this solved for the future... >> >> Thanks, Akos >> >> Bambid wrote: >> >> > Akos Szechy wrote: >> > >> >> Hi, >> >> >> >> I tested it as well, and its definately working fine. The only thing >> >> is if the user has Universal Password enabled, you have to provide >> >> the passwords with the correct cases. >> >> >> >> So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD definately >> >> handles the cases fine... >> >> >> >> Cheers, Akos >> >> >> >> Bambid wrote: >> >> >> >> > Bambid wrote: >> >> > >> >> >> bambid@email.cz wrote: >> >> >> >> >> >> > I have problems ( can4t login ) to login to all NetWare FTP >> >> servers >> > after installing SS 2.0.1 ( and no change after >> >> installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver >> >> on NW 6.5 servers. >> >> >> >> Renaming nmas.nlm solved all problems. But this isn?t solution for >> >> me. >> >> > >> >> > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. >> >> > >> > >> > Hi Alois, >> > I my setup I had tryed everything possible with UP, I created password >> > policy without UP enabled too. >> > >> > Users that I used to login to FTP server and / or ScreenSaver console >> > haven?t UP enabled or haven?t any password policy and still wasn?t >> > possible to login. After downgrade NMAS to 2.4.0 version all this >> > problems gone. >> > >> > I had some interesting side effect, I use Novell Border Manager and had >> > major problems with single sign-on via Client Trust. After NMAS >> > downgrade all problems were solved. >> > >>
![]() |
0 |
![]() |
Hi Ab, I tried to create password policy, where wasn�t UP enabled, but this doesn�t solved my problem, only backrev of NMAS helped me. David > No, this is a known issue (at least the screen saver part). Screen saver > does you the service of capitalizing all characters in your password when > using NMAS for some reason, or something like that. Checking for > TID....guess I can't find one right now. May need to write one. Anyway, > the scrsaver.nlm that comes with OES SP2 (NW 6.5.6) should have this fixed. > There is already a bug entered and resolved so it may be released on its > own as well but I doubt it. > > As a temporary work around I believe you can create a new UP policy, have > it explicitly say that no UP will be set, and assign that to the user > unlocking the screen. This is often an admin who does not need a UP anyway. > > Good luck. > > > > > > > Hi, > > > > Well, I can only say that its also working for me, so I would suggest to > > open an SR with Novell, if you want this solved for the future... > > > > Thanks, Akos > > > > Bambid wrote: > > > > > Akos Szechy wrote: > > > > > >> Hi, > > >> > > >> I tested it as well, and its definately working fine. The only thing > > >> is if the user has Universal Password enabled, you have to provide > > >> the passwords with the correct cases. > > >> > > >> So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD definately > > >> handles the cases fine... > > >> > > >> Cheers, Akos > > >> > > >> Bambid wrote: > > >> > > >> > Bambid wrote: > > >> > > > >> >> bambid@email.cz wrote: > > >> >> > > >> >> > I have problems ( can4t login ) to login to all NetWare FTP > > >> servers >> > after installing SS 2.0.1 ( and no change after > > >> installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver > > >> on NW 6.5 servers. >> > > >> >> Renaming nmas.nlm solved all problems. But this isn?t solution for > > >> me. > > >> > > > >> > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. > > >> > > > > > > > Hi Alois, > > > I my setup I had tryed everything possible with UP, I created password > > > policy without UP enabled too. > > > > > > Users that I used to login to FTP server and / or ScreenSaver console > > > haven?t UP enabled or haven?t any password policy and still wasn?t > > > possible to login. After downgrade NMAS to 2.4.0 version all this > > > problems gone. > > > > > > I had some interesting side effect, I use Novell Border Manager and had > > > major problems with single sign-on via Client Trust. After NMAS > > > downgrade all problems were solved. > > > > > >
![]() |
0 |
![]() |
TID# 10101057 > As another note may also be able to use upper-case password to get around it... > > Good luck. > > > > > > Hi, > > > > Well, I can only say that its also working for me, so I would suggest to > > open an SR with Novell, if you want this solved for the future... > > > > Thanks, Akos > > > > Bambid wrote: > > > > > Akos Szechy wrote: > > > > > >> Hi, > > >> > > >> I tested it as well, and its definately working fine. The only thing > > >> is if the user has Universal Password enabled, you have to provide > > >> the passwords with the correct cases. > > >> > > >> So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD definately > > >> handles the cases fine... > > >> > > >> Cheers, Akos > > >> > > >> Bambid wrote: > > >> > > >> > Bambid wrote: > > >> > > > >> >> bambid@email.cz wrote: > > >> >> > > >> >> > I have problems ( can4t login ) to login to all NetWare FTP > > >> servers >> > after installing SS 2.0.1 ( and no change after > > >> installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver > > >> on NW 6.5 servers. >> > > >> >> Renaming nmas.nlm solved all problems. But this isn?t solution for > > >> me. > > >> > > > >> > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. > > >> > > > > > > > Hi Alois, > > > I my setup I had tryed everything possible with UP, I created password > > > policy without UP enabled too. > > > > > > Users that I used to login to FTP server and / or ScreenSaver console > > > haven?t UP enabled or haven?t any password policy and still wasn?t > > > possible to login. After downgrade NMAS to 2.4.0 version all this > > > problems gone. > > > > > > I had some interesting side effect, I use Novell Border Manager and had > > > major problems with single sign-on via Client Trust. After NMAS > > > downgrade all problems were solved. > > > > > >
![]() |
0 |
![]() |
....and TID# 3006961 :-D Cheers, Akos ab@novell.com wrote: > TID# 10101057 > > > > >> As another note may also be able to use upper-case password to get around > it... >> >> Good luck. >> >> >> >> >> > Hi, >> > >> > Well, I can only say that its also working for me, so I would suggest >> > to open an SR with Novell, if you want this solved for the future... >> > >> > Thanks, Akos >> > >> > Bambid wrote: >> > >> > > Akos Szechy wrote: >> > > >> > >> Hi, >> > >> >> > >> I tested it as well, and its definately working fine. The only thing >> > >> is if the user has Universal Password enabled, you have to provide >> > >> the passwords with the correct cases. >> > >> >> > >> So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD >> > >> definately handles the cases fine... >> > >> >> > >> Cheers, Akos >> > >> >> > >> Bambid wrote: >> > >> >> > >> > Bambid wrote: >> > >> > >> > >> >> bambid@email.cz wrote: >> > >> >> >> > >> >> > I have problems ( can4t login ) to login to all NetWare FTP >> > >> servers >> > after installing SS 2.0.1 ( and no change after >> > >> installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver >> > >> on NW 6.5 servers. >> >> > >> >> Renaming nmas.nlm solved all problems. But this isn?t solution >> > >> >> for >> > >> me. >> > >> > >> > >> > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. >> > >> > >> > > >> > > Hi Alois, >> > > I my setup I had tryed everything possible with UP, I created >> > > password policy without UP enabled too. >> > > >> > > Users that I used to login to FTP server and / or ScreenSaver console >> > > haven?t UP enabled or haven?t any password policy and still wasn?t >> > > possible to login. After downgrade NMAS to 2.4.0 version all this >> > > problems gone. >> > > >> > > I had some interesting side effect, I use Novell Border Manager and >> > > had major problems with single sign-on via Client Trust. After NMAS >> > > downgrade all problems were solved. >> > > >> > >>
![]() |
0 |
![]() |
Ok, while we are playing with AB...:-D ....just to give you a hint: it might be usefull, if you want to play with it, to enable DSTRACE +NMAS and see what is happening there. Cheers, Akos bambid@email.cz wrote: > Hi Ab, > I tried to create password policy, where wasn�t UP enabled, but this > doesn�t solved my problem, only backrev of NMAS helped me. > > David > >> No, this is a known issue (at least the screen saver part). Screen saver >> does you the service of capitalizing all characters in your password when >> using NMAS for some reason, or something like that. Checking for >> TID....guess I can't find one right now. May need to write one. Anyway, >> the scrsaver.nlm that comes with OES SP2 (NW 6.5.6) should have this > fixed. >> There is already a bug entered and resolved so it may be released on its >> own as well but I doubt it. >> >> As a temporary work around I believe you can create a new UP policy, have >> it explicitly say that no UP will be set, and assign that to the user >> unlocking the screen. This is often an admin who does not need a UP > anyway. >> >> Good luck. >> >> >> >> >> >> > Hi, >> > >> > Well, I can only say that its also working for me, so I would suggest > to >> > open an SR with Novell, if you want this solved for the future... >> > >> > Thanks, Akos >> > >> > Bambid wrote: >> > >> > > Akos Szechy wrote: >> > > >> > >> Hi, >> > >> >> > >> I tested it as well, and its definately working fine. The only thing >> > >> is if the user has Universal Password enabled, you have to provide >> > >> the passwords with the correct cases. >> > >> >> > >> So 'novell' is not the same as 'Novell' or 'noVell'. NWFTPD > definately >> > >> handles the cases fine... >> > >> >> > >> Cheers, Akos >> > >> >> > >> Bambid wrote: >> > >> >> > >> > Bambid wrote: >> > >> > >> > >> >> bambid@email.cz wrote: >> > >> >> >> > >> >> > I have problems ( can4t login ) to login to all NetWare FTP >> > >> servers >> > after installing SS 2.0.1 ( and no change after >> > >> installing 2.0.2 ). >> > Same problem is with NetWare Screen Saver >> > >> on NW 6.5 servers. >> >> > >> >> Renaming nmas.nlm solved all problems. But this isn?t solution > for >> > >> me. >> > >> > >> > >> > Downgrade to NMAS 2.4.0 from NW 6.5 SP5 solved all my problems. >> > >> > >> > > >> > > Hi Alois, >> > > I my setup I had tryed everything possible with UP, I created > password >> > > policy without UP enabled too. >> > > >> > > Users that I used to login to FTP server and / or ScreenSaver console >> > > haven?t UP enabled or haven?t any password policy and still wasn?t >> > > possible to login. After downgrade NMAS to 2.4.0 version all this >> > > problems gone. >> > > >> > > I had some interesting side effect, I use Novell Border Manager and > had >> > > major problems with single sign-on via Client Trust. After NMAS >> > > downgrade all problems were solved. >> > > >> > >>
![]() |
0 |
![]() |