Highlighted
Absent Member.
Absent Member.
2049 views

Bug in newest clint 491sp2

There is a bug in newest client on windows 2000, when you want to relogin
your user account on the station after for example the night, you can use
any password you want and the network disks will be remap with all
proviliges for that user,

good luck,
best regards
Marcin Kowalczyk
Credit Agricole Poland - Lukas Bank Lodz

Labels (1)
0 Likes
5 Replies
Highlighted
Absent Member.
Absent Member.

Re: Bug in newest clint 491sp2

Hi,

mkowalczyk@lukas.com.pl wrote:
>
> There is a bug in newest client on windows 2000, when you want to relogin
> your user account on the station after for example the night, you can use
> any password you want and the network disks will be remap with all
> proviliges for that user,


Not a bug, but working as designed, and has been that way for a looong
time, it's not new behaviour.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Bug in newest clint 491sp2

You don't read my post : any password you want for example :
user: smith
password: google

User log in and after night they want to remap network drive and he uses
Novell login fron N in right corner, then He can write in password field
anything like : fuufle or anything else,

I know about auto authentificate funcion in netware client, so it is not
the answer for my post,
Best Regards
MK

> Hi,
>
> mkowalczyk@lukas.com.pl wrote:
> >
> > There is a bug in newest client on windows 2000, when you want to

relogin
> > your user account on the station after for example the night, you can

use
> > any password you want and the network disks will be remap with all
> > proviliges for that user,

>
> Not a bug, but working as designed, and has been that way for a looong
> time, it's not new behaviour.
>
> CU,
> --
> Massimo Rosen
> Novell Product Support Forum Sysop
> No emails please!
> http://www.cfc-it.de


0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Bug in newest clint 491sp2

mkowalczyk@lukas.com.pl wrote:
> You don't read my post : any password you want for example :
> user: smith
> password: google
>
> User log in and after night they want to remap network drive and he uses
> Novell login fron N in right corner, then He can write in password field
> anything like : fuufle or anything else,
>
> I know about auto authentificate funcion in netware client, so it is not
> the answer for my post,
> Best Regards
> MK
>
>
>>Hi,
>>
>>mkowalczyk@lukas.com.pl wrote:
>>
>>>There is a bug in newest client on windows 2000, when you want to

>
> relogin
>
>>>your user account on the station after for example the night, you can

>
> use
>
>>>any password you want and the network disks will be remap with all
>>>proviliges for that user,

>>
>>Not a bug, but working as designed, and has been that way for a looong
>>time, it's not new behaviour.
>>
>>CU,
>>--
>>Massimo Rosen
>>Novell Product Support Forum Sysop
>>No emails please!
>>http://www.cfc-it.de

>
>


Well he's right. It's not new behaviour. It's been that way forever.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Bug in newest clint 491sp2

mkowalczyk@lukas.com.pl wrote:

> You don't read my post : any password you want for example :
> user: smith
> password: google
>
> User log in and after night they want to remap network drive and he uses
> Novell login fron N in right corner, then He can write in password field
> anything like : fuufle or anything else,


Just to elaborate on why people are saying "it's been that way
forever", if a Windows workstation is currently logged into an NDS
tree successfully, running the Novell login again for the same user
and NDS tree (from red 'N' in system tray, using LOGINW32.EXE, etc.)
does not actually cause a new login to occur.

So long as you've specified the same user and NDS tree, the Novell
login sees that you're already logged in to that NDS tree as that
user, and realizes no new login needs to occur. As such, you're
really just running login scripts again, and the password, if you
bothered to provide one, was never used or required (because you're
already logged in).

So perhaps clarify what you mean by "relogin" and "after night". If
you want users to have to re-supply credentials in the morning to get
logged back into the Windows machine & the network, then at night they
should be using the Windows "Log Off" function from the Start menu so
that you've logged out of both Windows and any Novell/NetWare
connections that had been established.

If instead they are running SYS:PUBLIC\LOGOFF.EXE or similar to try
and clear only the Novell connections (but are staying logged in to
Windows overnight), then its possible that the workstations are
becoming reconnected to NDS and are therefore already logged in by the
time morning comes.

Before logging in to Novell in the morning, use the "Novell
Connections..." dialog to view the workstation's existing connections
before attempting to login. If you see that the workstation is
already logged into the NDS tree as the user you're about to login as,
then the password provided is going to be irrelevant because you're
actually already logged in.

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Bug in newest clint 491sp2

Thank you for answering my post
Best regards
Marcin Kowalczyk

> mkowalczyk@lukas.com.pl wrote:
>
> > You don't read my post : any password you want for example :
> > user: smith
> > password: google
> >
> > User log in and after night they want to remap network drive and he

uses
> > Novell login fron N in right corner, then He can write in password

field
> > anything like : fuufle or anything else,

>
> Just to elaborate on why people are saying "it's been that way
> forever", if a Windows workstation is currently logged into an NDS
> tree successfully, running the Novell login again for the same user
> and NDS tree (from red 'N' in system tray, using LOGINW32.EXE, etc.)
> does not actually cause a new login to occur.
>
> So long as you've specified the same user and NDS tree, the Novell
> login sees that you're already logged in to that NDS tree as that
> user, and realizes no new login needs to occur. As such, you're
> really just running login scripts again, and the password, if you
> bothered to provide one, was never used or required (because you're
> already logged in).
>
> So perhaps clarify what you mean by "relogin" and "after night". If
> you want users to have to re-supply credentials in the morning to get
> logged back into the Windows machine & the network, then at night they
> should be using the Windows "Log Off" function from the Start menu so
> that you've logged out of both Windows and any Novell/NetWare
> connections that had been established.
>
> If instead they are running SYS:PUBLIC\LOGOFF.EXE or similar to try
> and clear only the Novell connections (but are staying logged in to
> Windows overnight), then its possible that the workstations are
> becoming reconnected to NDS and are therefore already logged in by the
> time morning comes.
>
> Before logging in to Novell in the morning, use the "Novell
> Connections..." dialog to view the workstation's existing connections
> before attempting to login. If you see that the workstation is
> already logged into the NDS tree as the user you're about to login as,
> then the password provided is going to be irrelevant because you're
> actually already logged in.
>
> Alan Adams
> alancrumbadams@drcrumb.com
> (for email, remove the crumbs)


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.