Anonymous_User Absent Member.
Absent Member.
2863 views

Re: Login Script and Drive Mapping issue

I tried the patches you listed with seemingly no effect. Here is a copy of
the error that occurs for every mount point associated with this particular
server (Commodus).
********************************************************************
COMMODUS
LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be
completed.
[ROOT J:=COMMODUS/USERS:]
The error code was 8884.
********************************************************************
I appreciate the help thus far!


On Wed, 13 Jul 2005 15:19:18 GMT, curlet91@mio.uwosh.edu wrote:
>
> >Version 4.91 SP2.

>
> Do you mean version 4.9 SP2? The 890 error has been cause in the past
> by specific versions/SPs of clients. There are a number of post-4.9
> SP2 patches. While I see no listing of the 890 problem in the fixes
> in the patches, I suggest you try 49psp2_pkd.exe, 49psp2_dns_5.exe,
> 49psp2_nwfs_11.exe, and 49psp2_nwgina_13.exe.
>
> Please post the part of the login script that attempts to map to the
> server that results in the 430 errors.
>
> ---------------
> Donald Albury
> Novell Product Support Volunteer SysOp
> Sorry, no replies to e-mail responses
>
> "If something is so complicated that you can't
> explain it in 10 seconds, then it's probably not
> worth knowing anyway." Bill Waterson


Labels (1)
0 Likes
13 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

On Mon, 18 Jul 2005 14:37:19 GMT, curlet91@mio.uwosh.edu wrote:

>I tried the patches you listed with seemingly no effect. Here is a copy of
>the error that occurs for every mount point associated with this particular
>server (Commodus).
>********************************************************************
>COMMODUS
>LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
>LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be
>completed.
> [ROOT J:=COMMODUS/USERS:]
>The error code was 8884.
>********************************************************************


This could be a login script problem. Please post the portion of the
login script mapping to this server.

---------------
Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses

"If something is so complicated that you can't
explain it in 10 seconds, then it's probably not
worth knowing anyway." Bill Waterson
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

Here is the corresponding portion of the login script. I don't understand
why this problem is happening to only a few users when the same login
script is used for every user. I don't understand how but it really does
seem to be tied to whether or not the workstation has ZFD4 or
ZFD6.5(problematic).
******************************************************************
MAP ROOT H:=COMMODUS/DATA:Software
MAP ROOT I:=COMMODUS/DATA:Programs
MAP ROOT J:=COMMODUS/Users:
******************************************************************

> On Mon, 18 Jul 2005 14:37:19 GMT, curlet91@mio.uwosh.edu wrote:
>
> >I tried the patches you listed with seemingly no effect. Here is a copy of
> >the error that occurs for every mount point associated with this particular
> >server (Commodus).
> >********************************************************************
> >COMMODUS
> >LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
> >LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be
> >completed.
> > [ROOT J:=COMMODUS/USERS:]
> >The error code was 8884.
> >********************************************************************

>
> This could be a login script problem. Please post the portion of the
> login script mapping to this server.
>
> ---------------
> Donald Albury
> Novell Product Support Volunteer SysOp
> Sorry, no replies to e-mail responses
>
> "If something is so complicated that you can't
> explain it in 10 seconds, then it's probably not
> worth knowing anyway." Bill Waterson


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

On Mon, 18 Jul 2005 20:51:05 GMT, curlet91@mio.uwosh.edu wrote:

>Here is the corresponding portion of the login script. I don't understand
>why this problem is happening to only a few users when the same login
>script is used for every user. I don't understand how but it really does
>seem to be tied to whether or not the workstation has ZFD4 or
>ZFD6.5(problematic).
>******************************************************************
>MAP ROOT H:=COMMODUS/DATA:Software
>MAP ROOT I:=COMMODUS/DATA:Programs
>MAP ROOT J:=COMMODUS/Users:
>******************************************************************


Are these Win XP machines?

Quoting from TID 10085167:

Windows XP seems to behave differently in regards to how a MAP ROOT
function is used. It tends to MAP ROOT from paths other than just the
root of the volume.

To stop Windows XP from MAP ROOT'ing in this fashion, the environment
variable maprootoff can be set to 1.
This can be done from a login script, using the syntax 'DOS SET
MAPROOTOFF="1" ', or it can be added it to Windows XP as an
environment variable, by following the steps below:

Right-click on My Computer. Select Properties, then chose the Advanced
tab. Click the Environmental Variables button. Click New, and enter
variable name = maprootoff, variable value=1. Save this new entry,
and reboot.

---------------
Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses

"If something is so complicated that you can't
explain it in 10 seconds, then it's probably not
worth knowing anyway." Bill Waterson
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

> On Mon, 18 Jul 2005 20:51:05 GMT, curlet91@mio.uwosh.edu wrote:
>
> >Here is the corresponding portion of the login script. I don't understand
> >why this problem is happening to only a few users when the same login
> >script is used for every user. I don't understand how but it really does
> >seem to be tied to whether or not the workstation has ZFD4 or
> >ZFD6.5(problematic).
> >******************************************************************
> >MAP ROOT H:=COMMODUS/DATA:Software
> >MAP ROOT I:=COMMODUS/DATA:Programs
> >MAP ROOT J:=COMMODUS/Users:
> >******************************************************************

>
> Are these Win XP machines?


Yeah, all winxp machines. I tried the MAP root fix to no effect. The main
thing I don't understand here is that this problem is happening on
"COMMODUS" only. I have identical map commands for another Netware 6.5
server (same OS versions, SPs, and same tree) all in the same login script
used by the same users. For this other server the mapping is working
perfectly. It seems to be just a problem with "COMMODUS." Any other ideas?

>
> Quoting from TID 10085167:
>
> Windows XP seems to behave differently in regards to how a MAP ROOT
> function is used. It tends to MAP ROOT from paths other than just the
> root of the volume.
>
> To stop Windows XP from MAP ROOT'ing in this fashion, the environment
> variable maprootoff can be set to 1.
> This can be done from a login script, using the syntax 'DOS SET
> MAPROOTOFF="1" ', or it can be added it to Windows XP as an
> environment variable, by following the steps below:
>
> Right-click on My Computer. Select Properties, then chose the Advanced
> tab. Click the Environmental Variables button. Click New, and enter
> variable name = maprootoff, variable value=1. Save this new entry,
> and reboot.
>
> ---------------
> Donald Albury
> Novell Product Support Volunteer SysOp
> Sorry, no replies to e-mail responses
>
> "If something is so complicated that you can't
> explain it in 10 seconds, then it's probably not
> worth knowing anyway." Bill Waterson


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

Are you sure the problem server is in the SLP Scope ???


Try and hit "Display SLPDA" @ the console, and make sure it's in
contact with the SLPDA, and that the scopename is correct.

Also, you could, as a workaround, change the login script to use nds
syntax ???

MAP G:=.MYSERVER_VOL1.MYOU.MyO\USERS\ME

Also, try and turn of the "Bad Name Cache" in the client


--
Best Regards

Tommy Mikkelsen

IT Quality A/S
Denmark

Novell Support Forums SYSOP

Please Report back any success or failure, That way we all learn

Sorry, but no support through email

"I hate bugs".......Tommy Lee Jones, MIB

Be a GroupWiseR, go http://www.groupwiser.net

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

Looks like that could be it. Here's what I get
*****************************************************
COMMODUS:Display SLPDA

Total Active: 0 Total Inactive: 0
*****************************************************
How do i reconfigure SLP on that server to have the correct scope and settings?
Thanks!

> Are you sure the problem server is in the SLP Scope ???
>
>
> Try and hit "Display SLPDA" @ the console, and make sure it's in
> contact with the SLPDA, and that the scopename is correct.
>
> Also, you could, as a workaround, change the login script to use nds
> syntax ???
>
> MAP G:=.MYSERVER_VOL1.MYOU.MyO\USERS\ME
>
> Also, try and turn of the "Bad Name Cache" in the client
>
>
> --
> Best Regards
>
> Tommy Mikkelsen
>
> IT Quality A/S
> Denmark
>
> Novell Support Forums SYSOP
>
> Please Report back any success or failure, That way we all learn
>
> Sorry, but no support through email
>
> "I hate bugs".......Tommy Lee Jones, MIB
>
> Be a GroupWiseR, go http://www.groupwiser.net
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

curlet91@mio.uwosh.edu wrote:

> Looks like that could be it. Here's what I get
> *****************************************************
> COMMODUS:Display SLPDA
>
> Total Active: 0 Total Inactive: 0
> *****************************************************
> How do i reconfigure SLP on that server to have the correct scope and
> settings? Thanks!
>
> > Are you sure the problem server is in the SLP Scope ???
> >
> >
> > Try and hit "Display SLPDA" @ the console, and make sure it's in
> > contact with the SLPDA, and that the scopename is correct.
> >
> > Also, you could, as a workaround, change the login script to use nds
> > syntax ???
> >
> > MAP G:=.MYSERVER_VOL1.MYOU.MyO\USERS\ME
> >
> > Also, try and turn of the "Bad Name Cache" in the client
> >
> >
> > --
> > Best Regards
> >
> > Tommy Mikkelsen
> >
> > IT Quality A/S
> > Denmark
> >
> > Novell Support Forums SYSOP
> >
> > Please Report back any success or failure, That way we all learn
> >
> > Sorry, but no support through email
> >
> > "I hate bugs".......Tommy Lee Jones, MIB
> >
> > Be a GroupWiseR, go http://www.groupwiser.net
> >


Load Monitor, and select Server Parameters/ Service Location......


Also set discovery to 4, and edit the file named etc/slp.cfg before
doing that.


Then type set slp reset = on @ the console

--
Best Regards

Tommy Mikkelsen

IT Quality A/S
Denmark

Novell Support Forums SYSOP

Please Report back any success or failure, That way we all learn

Sorry, but no support through email

"I hate bugs".......Tommy Lee Jones, MIB

Be a GroupWiseR, go http://www.groupwiser.net

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

Seems to be fixed. I suppose it will take a week or two to be sure.
Thanks to both of you for the help!

> curlet91@mio.uwosh.edu wrote:
>
> > Looks like that could be it. Here's what I get
> > *****************************************************
> > COMMODUS:Display SLPDA
> >
> > Total Active: 0 Total Inactive: 0
> > *****************************************************
> > How do i reconfigure SLP on that server to have the correct scope and
> > settings? Thanks!
> >
> > > Are you sure the problem server is in the SLP Scope ???
> > >
> > >
> > > Try and hit "Display SLPDA" @ the console, and make sure it's in
> > > contact with the SLPDA, and that the scopename is correct.
> > >
> > > Also, you could, as a workaround, change the login script to use nds
> > > syntax ???
> > >
> > > MAP G:=.MYSERVER_VOL1.MYOU.MyO\USERS\ME
> > >
> > > Also, try and turn of the "Bad Name Cache" in the client
> > >
> > >
> > > --
> > > Best Regards
> > >
> > > Tommy Mikkelsen
> > >
> > > IT Quality A/S
> > > Denmark
> > >
> > > Novell Support Forums SYSOP
> > >
> > > Please Report back any success or failure, That way we all learn
> > >
> > > Sorry, but no support through email
> > >
> > > "I hate bugs".......Tommy Lee Jones, MIB
> > >
> > > Be a GroupWiseR, go http://www.groupwiser.net
> > >

>
> Load Monitor, and select Server Parameters/ Service Location......
>
>
> Also set discovery to 4, and edit the file named etc/slp.cfg before
> doing that.
>
>
> Then type set slp reset = on @ the console
>
> --
> Best Regards
>
> Tommy Mikkelsen
>
> IT Quality A/S
> Denmark
>
> Novell Support Forums SYSOP
>
> Please Report back any success or failure, That way we all learn
>
> Sorry, but no support through email
>
> "I hate bugs".......Tommy Lee Jones, MIB
>
> Be a GroupWiseR, go http://www.groupwiser.net
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue


You're welcome

--
Best Regards

Tommy Mikkelsen

IT Quality A/S
Denmark

Novell Support Forums SYSOP

Please Report back any success or failure, That way we all learn

Sorry, but no support through email

"I hate bugs".......Tommy Lee Jones, MIB

Be a GroupWiseR, go http://www.groupwiser.net

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

We have what seems like the same problem described by curlet91 in this
thread:
Some users sometimes; the same pool of users seemingly reporting
consistently but some less than daily, others oftener.

Often immediately fixed: [right click systray "N" | Netware Login | OK]
Drives Map.. baboom.
Other times fails repeatedly. Users may restart with out reporting,
intermittently fix results. Eventually everybody maps.

Some users never reporting.
All machines are XP, some are SP2 some are not.
Netware 6.5, Novell Client 4.91.0.20050216.

******************************

WMEC1:display SLPDA

192.168.1.6 : v? : INACTIVE : 'UNKNOWN SCOPE' : STATIC : 0 : 0MS
192.168.1.7 : v? : INACTIVE : 'UNKNOWN SCOPE' : STATIC : 0 : 0MS

Total Active: 0 Total Inactive: 2

******************************
...which I'm bound to admit looks incomplete, but might as well admit I
don't know what I'm looking at.

Client error log looks like

***************
Your current context is WMEC
User: Auser Context: WMEC
Your current tree is: WMEC
You are attached to server WMEC2.
WMEC1
LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
S1: = Z:. [WMEC2_SYS:LOGIN\NAV \]
The directory for drive Z: was deleted and the mapping was removed.
Good morning, Terri Walsh
Today is Wednesday, July 20.
WMEC1
LOGIN-LGNWNT32.DLL-890: The specified server is unknown.
LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not
be completed.
[ROOT INS S1:=WMEC1\SYS:PUBLIC]
The error code was 8884.
WMEC1

**-- reiterated for six (6) more drive mappings....

LOGIN-LGNWNT32.DLL-250: This utility was unable to set the default drive
to drive H:.

**-- My Documents is pointed at H: which failed to map in iteration
**--above

Drive M: = WMEC2_MAIL: \
Drives A,C,D map to a local disk.
Drive F: = WMEC2_SYS: \
Drive M: = WMEC2_MAIL: \

************

Once in a while, or on some machines(i'm not sure which) a windows
information screen appears at startup that says the same as the first
line of logged error:

LOGIN-LGNWNT32.DLL-890: The specified server is unknown.

*************************
Script goes:

IF MEMBER OF ".CN=SymantecAntiVirusUser.O=WMEC" THEN
MAP INS S1:=WMEC2\SYS:\LOGIN\NAV

**etc

MAP ROOT INS S1:=wmec1\SYS:PUBLIC

** etc for six more drives

map m:=wmec2\mail:
drive m:

********************

I though bad name cache had been turned off by ZenWorks several weeks
ago, but mine was turned on just now when i looked.
I almost never (but not never) have the problem on my own machine.

Anyway thanks for the pointers in general and I'll look here for any
specific comments on all of the above.

-=denny

Tommy Mikkelsen wrote:
> curlet91@mio.uwosh.edu wrote:
>
>
>>Looks like that could be it. Here's what I get
>>*****************************************************
>>COMMODUS:Display SLPDA
>>
>>Total Active: 0 Total Inactive: 0
>>*****************************************************
>>How do i reconfigure SLP on that server to have the correct scope and
>>settings? Thanks!
>>
>>
>>>Are you sure the problem server is in the SLP Scope ???
>>>
>>>
>>>Try and hit "Display SLPDA" @ the console, and make sure it's in
>>>contact with the SLPDA, and that the scopename is correct.
>>>
>>>Also, you could, as a workaround, change the login script to use nds
>>>syntax ???
>>>
>>>MAP G:=.MYSERVER_VOL1.MYOU.MyO\USERS\ME
>>>
>>>Also, try and turn of the "Bad Name Cache" in the client
>>>
>>>
>>>--
>>>Best Regards
>>>
>>>Tommy Mikkelsen
>>>
>>>IT Quality A/S
>>>Denmark
>>>
>>>Novell Support Forums SYSOP
>>>


>>>

>
>
> Load Monitor, and select Server Parameters/ Service Location......
>
>
> Also set discovery to 4, and edit the file named etc/slp.cfg before
> doing that.
>
>
> Then type set slp reset = on @ the console
>



--
Denny Wolfe
d e n n y at double you em eldercare dot oh ar gee
Holyoke, MA
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

On 7/22/2005 WMEC_desk wrote:

> WMEC1:display SLPDA
>
> 192.168.1.6 : v? : INACTIVE : 'UNKNOWN SCOPE' : STATIC : 0 : 0MS
> 192.168.1.7 : v? : INACTIVE : 'UNKNOWN SCOPE' : STATIC : 0 : 0MS
>
> Total Active: 0 Total Inactive: 2


Please post the DISPLAY SLPDA output from the 192.168.1.6 and
192.168.1.7

Also, I hope WMEC1 is not one of those servers. A DA should never
reference to itself.


--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

Edison Ortiz wrote:
> On 7/22/2005 WMEC_desk wrote:
>
>
>>WMEC1:display SLPDA
>>
>>192.168.1.6 : v? : INACTIVE : 'UNKNOWN SCOPE' : STATIC : 0 : 0MS
>>192.168.1.7 : v? : INACTIVE : 'UNKNOWN SCOPE' : STATIC : 0 : 0MS
>>
>>Total Active: 0 Total Inactive: 2

>
>
> Please post the DISPLAY SLPDA output from the 192.168.1.6 and
> 192.168.1.7
>
> Also, I hope WMEC1 is not one of those servers. A DA should never
> reference to itself.
>
>

hoping against hope. WMEC1 is x.x.1.6 ....
What is the predictive result of having the server reference itself?

It was configured as is before my time and (aside form the intermittent
mapping thing) is apparently working.

WMEC2 is x.x.1.7

***********
WMEC:display slpda

Total Active: 0 Total Inactive: 0

**************

--
Denny Wolfe
d e n n y at double you em eldercare dot oh ar gee
Holyoke, MA
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Login Script and Drive Mapping issue

On 7/25/2005 WMEC_desk wrote:

> hoping against hope. WMEC1 is x.x.1.6 ....
> What is the predictive result of having the server reference itself?
>
> It was configured as is before my time and (aside form the intermittent
> mapping thing) is apparently working.
>
> WMEC2 is x.x.1.7
>
> ***********
> WMEC:display slpda
>
> Total Active: 0 Total Inactive: 0


Remove the x.x.1.6 from WMEC1 in SLP.CFG and make sure to
enter the SCOPE name you've configured in NDS within MONITOR

At WMEC2, LOAD SPLDA and before doing so, make sure to have
the correct SCOPE name within MONITOR.

If any of these servers have the SCOPE name missing or you are
modifying it, you will need to reboot the server(s) for the changes
to take effect.


--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
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.