|
iSeries Navigator has a great way to tell if any user profiles are disabled for NetServer. Network Servers TCP/IP Right click on iSeries NetServer and select disabled user id's. Even has option to reset them. By the way, you can right click on iSeries NetServer and select Create Shortcut. Then to check for user id's you just open this up from your desk top and then you don't have to step through the tree. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Urbanek, Marty" <Marty_Urbanek@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 09/09/2004 10:08 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: disabled network neighborhood user Jim, One way it can get disabled is depending on how they estalish the connection to the NetServer share from the Windows PC. We do not have matching user ids and passwords between OS/400 and Windows. Therefore I need my users to estabish their connection to the share via the dialog that prompts for user/pwd. In order for this to happen, I request that they open up Windows Explorer and type the \\AS400name\sharename into the address bar, then get prompted and enter the apprpriate OS/400 user/pwd. This gets the connection with no problem. (I think doing a manual NET USE with appropriate user/pwd also works) However, if they disregard my request, and enter the path, for example, using Start/Run (definitely) or Internet Explorer (IIRC) then Windows defaults to sending the Windows user/pwd, which does not match what they need for OS/400. Furthermore, Windows does enough retries to exceed the limit and then we have the problem you described. In order to reset the condition, I simply do a CHGUSRPRF on the usrprf in question without changing anything, CHGUSRPRF USRPRF(blah). I do not know a way to proactively check whether it has been disabled. Only to watch for the message you mentioned after the fact. -Marty ------------------------------ date: Thu, 9 Sep 2004 09:59:40 -0400 from: "Jim Hawkins" <jim.hawkins@xxxxxxxxxxx> subject: 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. +++++++++++++++++++++++++++++++++++++++++++++++++++ -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.