Anonymous_User Absent Member.
Absent Member.
1606 views

Novell 4.91 SP4 Problems

We are trying to test Novell Client 4.91 SP4 (edir is 8.7.3.9 and Universal Password is enabled ) and 8 out of every 10 PCs we install it on can't login. Tree or Server not found. If you clock on the Advanced tab and then the NMAS tab it says the user is not a valid NMAS user. Downgrading to 4.91 SP 3 fixes the problem.

Anyone seen this? Any fixes?

Thanks,

Al

Al Hidalgo
Enterprise Systems Support Analyst
Information Technology
University Hospitals
ahidalgo@salud.unm.edu
Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Novell 4.91 SP4 Problems

"Al Hidalgo" <AHidalgo@salud.unm.edu> wrote:

> We are trying to test Novell Client 4.91 SP4 (edir is 8.7.3.9
> and Universal Password is enabled ) and 8 out of every 10 PCs
> we install it on can't login. Tree or Server not found. If you
> clock on the Advanced tab and then the NMAS tab it says the
> user is not a valid NMAS user. Downgrading to 4.91 SP 3 fixes
> the problem.


Can't say I've seen it yet.

I suspect the "tree or server not found" and the "the eDirectory user,
context, tree or server name was not valid" are just both reporting
the same underlying condition: the server name and/or tree name
provided could not be resolved.

By what name resolution method was the server or tree name provided
supposed to be successfully resolved? (e.g. By DNS? By SLP via a
DHCP-supplied DA? By SLP by a configured DA? By SLP via multicast?)

It does not appear that the SRVLOC.SYS driver changed at all between
4.91 SP3 and 4.91 SP4. The NWDNS.SYS driver did; citing an update to
allow it to use a Windows group policy-assigned DNS suffix list.

(I suppose on a long shot, maybe there was a non-successful DNS suffix
list being supplied by group policy all along, and now the installed
NWDNS.SYS is actually using it? But that should only be applicable if
the names were being resolved through DNS.)

Eric Young had reported here during the 4.91 SP4 beta that the way in
which 4.91 SP4 had been changed to ensure Windows started SRVLOC
before the Novell Client was causing a failure to start SRVLOC (and
therefore, a failure to start NWFS) on some machines.

So perhaps also check the Windows "System" event log to see if the
Windows service control manager is reporting a failure to start any
Novell Client-related services or drivers.

I guess that's something else I should also confirm: You are talking
about the released 4.91 SP4 from download.novell.com, and not one of
the pre-release 4.91 SP4 betas?

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

Re: Novell 4.91 SP4 Problems

Alan Adams wrote:
> "Al Hidalgo" <AHidalgo@salud.unm.edu> wrote:
>
>> We are trying to test Novell Client 4.91 SP4 (edir is 8.7.3.9
>> and Universal Password is enabled ) and 8 out of every 10 PCs
>> we install it on can't login. Tree or Server not found. If you
>> clock on the Advanced tab and then the NMAS tab it says the
>> user is not a valid NMAS user. Downgrading to 4.91 SP 3 fixes
>> the problem.

>
> Can't say I've seen it yet.
>
> I suspect the "tree or server not found" and the "the eDirectory user,
> context, tree or server name was not valid" are just both reporting
> the same underlying condition: the server name and/or tree name
> provided could not be resolved.
>
> By what name resolution method was the server or tree name provided
> supposed to be successfully resolved? (e.g. By DNS? By SLP via a
> DHCP-supplied DA? By SLP by a configured DA? By SLP via multicast?)
>
> It does not appear that the SRVLOC.SYS driver changed at all between
> 4.91 SP3 and 4.91 SP4. The NWDNS.SYS driver did; citing an update to
> allow it to use a Windows group policy-assigned DNS suffix list.
>
> (I suppose on a long shot, maybe there was a non-successful DNS suffix
> list being supplied by group policy all along, and now the installed
> NWDNS.SYS is actually using it? But that should only be applicable if
> the names were being resolved through DNS.)
>
> Eric Young had reported here during the 4.91 SP4 beta that the way in
> which 4.91 SP4 had been changed to ensure Windows started SRVLOC
> before the Novell Client was causing a failure to start SRVLOC (and
> therefore, a failure to start NWFS) on some machines.
>
> So perhaps also check the Windows "System" event log to see if the
> Windows service control manager is reporting a failure to start any
> Novell Client-related services or drivers.
>
> I guess that's something else I should also confirm: You are talking
> about the released 4.91 SP4 from download.novell.com, and not one of
> the pre-release 4.91 SP4 betas?
>
> Alan Adams
> alancrumbadams@drcrumb.com
> (for email, remove the crumbs)

I found this in the readme: maybe this could be your issue?
http://www.novell.com/documentation/noclienu/clientreadme/data/ncw_readme_sp4.html#bupggh6
3.1 Login Fails when Specifying the Default NMAS Login Sequence

By default, the Novell Client attempts to perform an NMAS™ login using
the NMAS login sequence that is configured in eDirectory. If nothing is
specified, the Novell Client uses the default NMAS login sequence. This
automatic fallback to the default can fail when logging in against an
NMAS 2.3.4.1 server.

In the Login dialog box, select Advanced, select the NMAS tab, and then
select NDS in the Sequence drop-down menu.
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.