MAP and Clustered volume name

[Sylvain Gagnon]

I thought to ask here first since it is related to the DOS/Windows
Client32.

I've managed to login to my Netware 5.1 server using IP (confirm from
the station network address in Monitor). Once logged in, I can map to
Server/volume: or nds_volune_name: no problem but I CAN'T do the same
for NWCS 'virtual' server or volume. I get the 'specified server is
unknown'. The map.exe I'm using is version 4.13 (970813). The SAME
command throught a DOS Command prompt in Win9x works no problem (same
map.exe file). Is this 'normal' behaviour or am I doing something wrong?

Thanks

[Barry St.John [SysOp]]

You have to use a specific naming convention for clusters:

map <drive:>=.clustername_volumename.context

-or-

You can use the secondary IP address of the volume followed by the volume
name only:

map <drive:>= \\nnn.nnn.nnn.nnn\volumename

-Barry. [Novell Support Connection SysOp]

[Sylvain Gagnon]

The "map <drive:>=.clustername_volumename.context" didn't work. It told the
the physical server cannot be found. I haven't tried mapping to
nnn.nnn.nnn.nnn yet.

"Barry St.John [SysOp]" a écrit :

[Steven Krijnen]

Hi Sylvain Gagnon

I have the same discussion going under the Clustered Volumes forum.
Anyway I have tried mapping to nnn.nnn.nnn.nnn yet.

It doesn't work for me under DOS, but works fine under Win9x/NT.

I have been reading the forums quite a bit and have come to the
conclusion that we are not the only ones suffering with this issue.
Can Novell please test this, or upgrade the DOS client. We are not in
a position yet to completely remove DOS in our environment.

Steven Krijnen
New Zealand

* Sent from Novell Discussion Forums http://novell.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

[Barry St.John [SysOp]]

In article <09749678...@usw-ex0106-048.remarq.com>, Steven Krijnen
wrote:

> ...or upgrade the DOS client.

This is not likely to happen. There hasn't been any DOS development done
in about a year. You can certainly issue an enhancement request, though.
If Novell receives enough requests for this to warrant putting the
resources into fixing it, they just might do it.

http://support.novell.com/enhancement