RE: CPIB682 - User profile &1 disabled for IBM i Support for Windows Network Neighborhood access.

We solved this by deleting/adding the mapped drives to our Win login scripts.

NET USE * /delete /yes

NET USE Y: \\LPAR name\folder name

Paul

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Mark Waterbury
Sent: Friday, October 23, 2020 1:59 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: CPIB682 - User profile &1 disabled for IBM i Support for Windows Network Neighborhood access.

________________________________
CAUTION: This email originated from outside of the PENCOR network. Do not click on any links or open attachments unless the sender is known, and the content is verified as safe.
________________________________

Rob,

I think that's the whole problem right there in a nutshell...

When you connect to a Windows share, you can specify to have it "automatically reconnect on re-boot."

So, what happens when a user changed their password in the meantime?

The next time they reboot Windows, when it tries to "auto-reconnect" the "shares," I think this is what ends up disabling the user profile... (or at least the "NetServer userID), -- it might not happen on the first "share", but if you have multiple shares defined ...? :-/

Perhaps we need an RFE for this, but I am not certain how to word that or how exactly it should be resolved or fixed?

Hope that helps,

Mark S. Waterbury

On Friday, October 23, 2020, 1:53:19 PM EDT, Rob Berendt <rob@xxxxxxxxx> wrote:

I was kind of hoping that a reboot would have done that but I'll keep that in mind.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2fwww.dekko.com&umid=f0f33a30-9d57-4409-a2e6-3afb62eae5ec&auth=438b0784514c1757bd202125ca4db8b0abdb021e-e094d44a877b91d6a68dee1003cc251f87508186

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.midrange.com%2fmailman%2flistinfo%2fmidrange%2dl&umid=f0f33a30-9d57-4409-a2e6-3afb62eae5ec&auth=438b0784514c1757bd202125ca4db8b0abdb021e-a75f1dc202256ba888927ac325ae05e31803be61
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2farchive.midrange.com%2fmidrange%2dl&umid=f0f33a30-9d57-4409-a2e6-3afb62eae5ec&auth=438b0784514c1757bd202125ca4db8b0abdb021e-86ed07dc93e964db4a15daa3af57f9942b8ee624.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2famazon.midrange.com&umid=f0f33a30-9d57-4409-a2e6-3afb62eae5ec&auth=438b0784514c1757bd202125ca4db8b0abdb021e-72d4d5212f274dac2f16afd8a78e3c469e0443e2