Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NMAS: no default login sequence defined for this user

36 views
Skip to first unread message

Patrick Hasenjager

unread,
Dec 10, 2009, 3:11:08 PM12/10/09
to
All of a sudden, all of our campus computers started receiving this
message when attempting to log in. If you logged in workstation only,
then logged into the Novell client, it worked properly.

To fix the issue, we had to make a change to the Login Policy object and
then revert the change. After that, everything started working properly.

We have no idea what could have caused the issue as no changes were made
to anything in NMAS for quite some time. Anyone have any thoughts as to
what could have changed?

Peter Kuo

unread,
Dec 10, 2009, 10:34:55 PM12/10/09
to
"All of a sudden" as in one morning, or middle of the day or ?? This
symptom is "generally" caused by a change in eDir version (upgrading from
8.7.3.x to 8.8.x) or NMAS on the server(s).

--


Peter
eDirectory Rules!
http://www.DreamLAN.com

Patrick Hasenjager

unread,
Dec 11, 2009, 10:54:58 AM12/11/09
to
On 12/10/2009 9:34 PM, Peter Kuo wrote:
> "All of a sudden" as in one morning, or middle of the day or ?? This
> symptom is "generally" caused by a change in eDir version (upgrading
> from 8.7.3.x to 8.8.x) or NMAS on the server(s).
>

All of a sudden as in the middle of the day... It worked properly at
around 9:30, but at 10:00 we had people complaining they weren't able to
login. We have not upgraded eDir version or the NMAS version on any
server for quite some time. I believe the last time was back in May.

Peter Kuo

unread,
Dec 12, 2009, 1:35:12 AM12/12/09
to
Patrick Hasenjager wrote:

> It worked properly at around 9:30, but at 10:00 we had people
complaining they weren't able to login.

That is pretty wild -- which suggests something changed within the DS (as
not in an upgrade, but perhaps an actual change [accidentically?], or
corruption) or a temp. WAN/LAN link outage causing a sync issue or
inability to locate the Login Policy object? Unless it is reproducable, it
would be hard to determine what the initial cause was.

Patrick Hasenjager

unread,
Dec 14, 2009, 11:18:37 AM12/14/09
to

We have issues on occasion with Macs not being able to authenticate
using AFP, which may correlate, but this usually only happens after one
of the AFP servers is restarted.

As far as we can tell, nothing was changed. It is possible this has
happened before, but we really haven't been using NMAS until about six
months ago when we enabled Universal Password.

We were just trying to see if anyone else had seen something like this
before. As we all know around here, it doesn't matter if anyone else
has seen it... if it can happen, it will happen here.

Thanks for your assistance.

0 new messages