Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
12168 views

Error 8804 when mapping drive

I have client 4.91 SP2 on W2K & Win XP machines. If a user reboots the
computer and login to the network as soon as the login GUI comes up, user
will get error 8804 when mapping to the network drive. The mapping is
pointing to SERVER_VOLNAME instead of the UNC path.

If the user waits till the hard drive still blinking i.e. finishes the
booting process, user will login without error. If the user login and got
the mapping error, the user will have to use the Novell Login connection,
clear the connection and then login again and then the mapping will be fine.

The DS is syncing properly and the above still happens.

I have tried the 4.91 SP3 client and the problem still exists.

Any idea or if other people are experiencing the same issue.

Thanks
NW admin
Labels (1)
0 Likes
10 Replies
Anonymous_User Absent Member.
Absent Member.

Error 8804 when mapping drive

If I had to guess, you are logging in prior to SLP being fully initialized
and the resolution is failing.

I would try setting the mapping in the logon script to use DS Syntax...

Example - Map S:=.MYServer_VOL1.MYOU.MYO

This will use DS Resolution to find the volume which I often find to be the
fastest and most reliable method.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Error 8804 when mapping drive

I think your comment kind of explaining my environment. I have been adding
multiple NW 6.5 servers on the same subnet but have not configured SLP.
However, in the Novell client, I specify the preferred server and the
mapping of the drive is on the same server so it would still use SLP?

Thanks
NW admin

> If I had to guess, you are logging in prior to SLP being fully initialized
> and the resolution is failing.
>
> I would try setting the mapping in the logon script to use DS Syntax...
>
> Example - Map S:=.MYServer_VOL1.MYOU.MYO
>
> This will use DS Resolution to find the volume which I often find to be the
> fastest and most reliable method.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Error 8804 when mapping drive

I doubt it is using SLP, but you could still try that syntax.

Another option is to disable "Bad Name Cache"

This could also relate to timing in which an attachment is attempted to a
server before the network is fully up, it could fail to attach to that box
and fail to logon.

Can you manually browse to the server immediately after the map fails?
If no, you are probably having the server placed in bad cache.
If you can, then bad name cache is not likely the issue.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Error 8804 when mapping drive

The NW 6.5 servers are added more than 3 months ago and we only start
getting error 8804 for the past month. I always use the SERNAME_VOLNAME for
the mapping and the preferred server is the file server that the mapping is
running on.

I will check the browsing option next time when users get error 8804 again.

Thanks
NW Admin

> I doubt it is using SLP, but you could still try that syntax.
>
> Another option is to disable "Bad Name Cache"
>
> This could also relate to timing in which an attachment is attempted to a
> server before the network is fully up, it could fail to attach to that box
> and fail to logon.
>
> Can you manually browse to the server immediately after the map fails?
> If no, you are probably having the server placed in bad cache.
> If you can, then bad name cache is not likely the issue.
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Error 8804 when mapping drive

I should also toss out "licensing" as a possible issue as well.

With older versions of NetWare a 25-user license got you 25-concurrent
users on a single server.

With NetWare versions of NetWare a 25-user license gets you 25
Non-Concurrent users across an unlimited number of servers.

This means if you have 30 people who logon but no more than 20 at a time,
you will still need 30 licenses.

The new model works out really well for folks with multiple servers but
less so for folks with one server. (If you had two servers in the example
above you would need to buy (2) sets of 20-licenses (40 total) while in the
new model you would only need a single license for 30. With more servers
the benefeit really grows.)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Error 8804 when mapping drive

I did look at the license before and I have available license for both the
NW 5.1 servers and NW 6.5 user counts.

Regards
NW Admin

> I should also toss out "licensing" as a possible issue as well.
>
> With older versions of NetWare a 25-user license got you 25-concurrent
> users on a single server.
>
> With NetWare versions of NetWare a 25-user license gets you 25
> Non-Concurrent users across an unlimited number of servers.
>
> This means if you have 30 people who logon but no more than 20 at a time,
> you will still need 30 licenses.
>
> The new model works out really well for folks with multiple servers but
> less so for folks with one server. (If you had two servers in the example
> above you would need to buy (2) sets of 20-licenses (40 total) while in the
> new model you would only need a single license for 30. With more servers
> the benefeit really grows.)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Error 8804 when mapping drive

The NSS volume object is SEVERNAME_VOL1 under organization .COMPANY.

I tried "map r:=.SERVERNAME_VOL1.COMPANY and got:

MAP-4.13 (970813) PTF-400: You attempted to map a network drive to unmapped
driv
e
or to a local drive.

Am I missing something?

Thanks
NW Admin

> I did look at the license before and I have available license for both the
> NW 5.1 servers and NW 6.5 user counts.
>
> Regards
> NW Admin
>
> > I should also toss out "licensing" as a possible issue as well.
> >
> > With older versions of NetWare a 25-user license got you 25-concurrent
> > users on a single server.
> >
> > With NetWare versions of NetWare a 25-user license gets you 25
> > Non-Concurrent users across an unlimited number of servers.
> >
> > This means if you have 30 people who logon but no more than 20 at a time,
> > you will still need 30 licenses.
> >
> > The new model works out really well for folks with multiple servers but
> > less so for folks with one server. (If you had two servers in the example
> > above you would need to buy (2) sets of 20-licenses (40 total) while in the
> > new model you would only need a single license for 30. With more servers
> > the benefeit really grows.)

>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Error 8804 when mapping drive

Im missing it too.
There are some examples of using DS to map objects here......

http://www.novell.com/documentation/linux_client/login/data/bvuw4no.html

Perhaps you can see a syntax error that I missing at this point in tim.

> MAP-4.13 (970813) PTF-400: You attempted to map a network drive to

unmapped > drive

I find this error slightly humorous in nature because it's like 'Duh! Of
course I tried to map a network drive to an unmapped drive 😆
0 Likes
Anonymous_User Absent Member.
Absent Member.

Error 8804 when mapping drive

It is very weird, I was able to map to the R drive using the syntax below
once only and I get the same mapping error again.

map r: = .SERVERNAME_VOLNAME.COMPANY\

Well, I will setup SLP on the new server by end of this week and hopefully
I don't have to use the DS syntax.

Thanks
NWAdmin


> Im missing it too.
> There are some examples of using DS to map objects here......
>
> http://www.novell.com/documentation/linux_client/login/data/bvuw4no.html
>
> Perhaps you can see a syntax error that I missing at this point in tim.
>
> > MAP-4.13 (970813) PTF-400: You attempted to map a network drive to

> unmapped > drive
>
> I find this error slightly humorous in nature because it's like 'Duh! Of
> course I tried to map a network drive to an unmapped drive 😆


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Error 8804 when mapping drive

try adding a colon ( : ) to the end.

map r:=.SERVERNAME_VOL1.COMPANY:

Besure you use the fully distinguised name for the volume

On Dec 12, 6:08 am, nwad...@domain.com wrote:
> The NSS volume object is SEVERNAME_VOL1 under organization .COMPANY.
>
> I tried "map r:=.SERVERNAME_VOL1.COMPANY and got:
>
> MAP-4.13 (970813) PTF-400: You attempted to map a network drive to unmapped
> driv
> e
> or to a local drive.
>
> Am I missing something?
>
> Thanks
> NW Admin
>
> > I did look at the license before and I have available license for both the
> > NW 5.1 servers and NW 6.5 user counts.

>
> > Regards
> > NW Admin

>
> > > I should also toss out "licensing" as a possible issue as well.

>
> > > With older versions of NetWare a 25-user license got you 25-concurrent
> > > users on a single server.

>
> > > With NetWare versions of NetWare a 25-user license gets you 25
> > > Non-Concurrent users across an unlimited number of servers.

>
> > > This means if you have 30 people who logon but no more than 20 at a time,
> > > you will still need 30 licenses.

>
> > > The new model works out really well for folks with multiple servers but
> > > less so for folks with one server. (If you had two servers in the example
> > > above you would need to buy (2) sets of 20-licenses (40 total) while in the
> > > new model you would only need a single license for 30. With more servers
> > > the benefeit really grows.)


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.