|
It means that they tried to connect to NetServer and failed. This most often is because they have a drive mapped to it, changed their Windows password, and Windows banged three tries off trying to connect. Disabled for NetServer is not the same as having the user profile disabled. There are a couple of ways of seeing if the user has been disabled for just NetServer: API calls, Ops Navigator, etc. For Ops Navigator, drill down to TCP/IP servers, right click on NetServer and select "Disabled Users". Most kinds of maintenance on the user profile will enable NetServer connectivity again. Check out http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/index.htm?info/ rzahl/rzahlpoadministernet.htm. > > message: 8 > date: Thu, 9 Sep 2004 09:59:40 -0400 > from: "Jim Hawkins" <jim.hawkins@xxxxxxxxxxx> > subject: disabled network neighborhood user > > Periodically, we get messages like this. > > User profile xxxxxxxx disabled for iSeries Support for Windows Network > Neighborhood access. > > Users do not seem to be affected by this disabled profile. So my > questions are: > 1) What causes users to be disabled in this manner? What is it that they > are doing? I know that they exceeding the maximum number of sign on > attempts, but where, doing what? > 2) How is this reset, or how can I see if a user has this disabled? I > don't see anything in WRKUSRPRF to reset the network neighborhood access. > The traditional profile remains enabled.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.