[no subject]
2015-10-04 17:53:22
To all ADSM Win32 users,
We have a few customers reported a problem with Win 32 client level 3.1.0.5
that
it's using the node name to construct the filespace name (ie, \\nodename\c$)
instead
of the machine name (ie, \\machinename\c$) if the node name & the machine
name
don't match. The apar # is IC21959. The problem is due to the fact that
the
node name
in dsm.opt is specified before the domain statement. This will be fixed
ASAP.
Problem:
machine name defined as MACHINE1
in dsm.opt: nodename FILESERVER1
domain c:
when you issue dsmc i, you get message
ANS1134E Drive \\FILESERVER1\C$ is an invalid drive
specification
Work around:
Modify dsm.opt so that the domain statement appears before the nodename.
domain c:
nodename FILESERVER1
Regards,
Joanne Nguyen
ADSM Client Development
=
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
|
|
|