cgaa183 Absent Member.
Absent Member.
9455 views

OES2sp2 miggui Failed to mount volume

Trying to migrate NW65SP8 (DS8.8.4) to OES2sp2.
miggui is running on the OES2sp2 server which is patched up to date using rug.
Source and target servers are in the came container in the DS.
I can define the source and target servers and get to the point where I want to configure the migration of volumes, but then I get a failure. The log (minus the timestamps for clarity) reads:

ERROR - FILESYSTEM:volmount.rb:Command to mount source: ruby /opt/novell/migration/sbin/volmount.rb -s 138.37.100.118 -a "cn=joshua,ou=sys,o=qmw" -c cp437 -f "/var/opt/novell/migration/cc18/fs/mnt/source" -m -t NW65
INFO - FILESYSTEM:volmount.rb:*****************Command output start**********************************
INFO - FILESYSTEM:volmount.rb:
INFO - FILESYSTEM:volmount.rb:Information: ncpmount using code page 437
INFO - FILESYSTEM:volmount.rb:Information: ncpshell command executed as: LC_ALL=en_US.UTF-8 /opt/novell/ncpserv/sbin/ncpshell --volumes --ip=138.37.100.118 --u="joshua.sys.qmw"
INFO - FILESYSTEM:volmount.rb:Information: Mounting Volume = _ADMIN
INFO - FILESYSTEM:volmount.rb:Information: Executing command: /opt/novell/ncl/bin/nwmap -s 138.37.100.118 -d /var/opt/novell/migration/cc18/fs/mnt/source/_ADMIN -v _ADMIN
INFO - FILESYSTEM:volmount.rb:Fatal: Failed to mount volume _ADMIN for server 138.37.100.118
INFO - FILESYSTEM:volmount.rb:Fatal: SystemCallError, Unknown error 1008 - Failed to mount volume _ADMIN for server 138.37.100.118 .

I tried executing what appears to be the offending command by hand:
ruby /opt/novell/migration/sbin/volmount.rb -s 138.37.100.118 -a "cn=joshua,ou=sys,o=qmw" -c cp437 -f "K" -m -t NW65 -p password --debug

which produces the output:
Information: ncpmount using code page 437
Information: ncpshell command executed as: LC_ALL=en_US.UTF-8 /opt/novell/ncpserv/sbin/ncpshell --volumes --ip=138.37.100.118 --u="joshua.sys.qmw"
Information: Mounting Volume = _ADMIN
Information: Executing command: /opt/novell/ncl/bin/nwmap -s 138.37.100.118 -d K/_ADMIN -v _ADMIN
Fatal: Failed to mount volume _ADMIN for server 138.37.100.118
Fatal: SystemCallError, Unknown error 1008 - Failed to mount volume _ADMIN for server 138.37.100.118 .
Information: File K/_ADMIN/Novell/Cluster/PoolConfig.xml does not exist. No cluster resources attached
Information: Mounting Volume = SYS
Information: Executing command: /opt/novell/ncl/bin/nwmap -s 138.37.100.118 -d K/SYS -v SYS
Fatal: Failed to mount volume SYS for server 138.37.100.118
Information: unmounting all mounted volumes
Information: Executing command:/opt/novell/ncl/bin/nwlogout -f -s QMWCC18
Cannot perform logout: Cannot connect to server:[QMWCC18]. Error:NWCCOpenConnByName:
Information: Command Output:
Information: Executing command: rm K/*
rm: cannot remove `K/*': No such file or directory
Fatal: SystemCallError, Unknown error 1008 - Failed to mount volume SYS for server 138.37.100.118 .

SLP shows both servers, they are on the same network as each other, and the firewall is turned off.
Does anyone have any idea what may be causing the mount failure or what error 1008 might be?

Tim
Labels (1)
0 Likes
12 Replies
Anonymous_User Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

cgaa183 wrote:
> Trying to migrate NW65SP8 (DS8.8.4) to OES2sp2.
> miggui is running on the OES2sp2 server which is patched up to date
> using rug.
> Source and target servers are in the came container in the DS.
> I can define the source and target servers and get to the point where I
> want to configure the migration of volumes, but then I get a failure.
> The log (minus the timestamps for clarity) reads:
>
> ERROR - FILESYSTEM:volmount.rb:Command to mount source: ruby
> /opt/novell/migration/sbin/volmount.rb -s 138.37.100.118 -a
> "cn=joshua,ou=sys,o=qmw" -c cp437 -f
> "/var/opt/novell/migration/cc18/fs/mnt/source" -m -t NW65
> INFO - FILESYSTEM:volmount.rb:*****************Command output
> start**********************************
> INFO - FILESYSTEM:volmount.rb:
> INFO - FILESYSTEM:volmount.rb:Information: ncpmount using code page
> 437
> INFO - FILESYSTEM:volmount.rb:Information: ncpshell command executed
> as: LC_ALL=en_US.UTF-8 /opt/novell/ncpserv/sbin/ncpshell --volumes
> --ip=138.37.100.118 --u="joshua.sys.qmw"
> INFO - FILESYSTEM:volmount.rb:Information: Mounting Volume = _ADMIN
> INFO - FILESYSTEM:volmount.rb:Information: Executing command:
> /opt/novell/ncl/bin/nwmap -s 138.37.100.118 -d
> /var/opt/novell/migration/cc18/fs/mnt/source/_ADMIN -v _ADMIN
> INFO - FILESYSTEM:volmount.rb:Fatal: Failed to mount volume _ADMIN for
> server 138.37.100.118
> INFO - FILESYSTEM:volmount.rb:Fatal: SystemCallError, Unknown error
> 1008 - Failed to mount volume _ADMIN for server 138.37.100.118 .
>
> I tried executing what appears to be the offending command by hand:
> ruby /opt/novell/migration/sbin/volmount.rb -s 138.37.100.118 -a
> "cn=joshua,ou=sys,o=qmw" -c cp437 -f "K" -m -t NW65 -p password
> --debug
>
> which produces the output:
> Information: ncpmount using code page 437
> Information: ncpshell command executed as: LC_ALL=en_US.UTF-8
> /opt/novell/ncpserv/sbin/ncpshell --volumes --ip=138.37.100.118
> --u="joshua.sys.qmw"
> Information: Mounting Volume = _ADMIN
> Information: Executing command: /opt/novell/ncl/bin/nwmap -s
> 138.37.100.118 -d K/_ADMIN -v _ADMIN
> Fatal: Failed to mount volume _ADMIN for server 138.37.100.118
> Fatal: SystemCallError, Unknown error 1008 - Failed to mount volume
> _ADMIN for server 138.37.100.118 .
> Information: File K/_ADMIN/Novell/Cluster/PoolConfig.xml does not
> exist. No cluster resources attached
> Information: Mounting Volume = SYS
> Information: Executing command: /opt/novell/ncl/bin/nwmap -s
> 138.37.100.118 -d K/SYS -v SYS
> Fatal: Failed to mount volume SYS for server 138.37.100.118
> Information: unmounting all mounted volumes
> Information: Executing command:/opt/novell/ncl/bin/nwlogout -f -s
> QMWCC18
> Cannot perform logout: Cannot connect to server:[QMWCC18].
> Error:NWCCOpenConnByName:
> Information: Command Output:
> Information: Executing command: rm K/*
> rm: cannot remove `K/*': No such file or directory
> Fatal: SystemCallError, Unknown error 1008 - Failed to mount volume SYS
> for server 138.37.100.118 .
>
> SLP shows both servers, they are on the same network as each other, and
> the firewall is turned off.
> Does anyone have any idea what may be causing the mount failure or what
> error 1008 might be?
>
> Tim
>
>

Can you check 'rcnovfsd' service running on your target OES2SP2 server?
I believe novell client service is not running. From OES2SP2 onwards,
Migration Tools uses novell client service to map volumes of the source
server.

Try re-starting the service should resolve this issue.
0 Likes
hbloupot
New Member.

Re: OES2sp2 miggui Failed to mount volume

Hi,

We have exactly the same problem. I just checked, the rcnovfsd is running.

Regards,

Hans
0 Likes
mfinn Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

We have the same issue as well. It worked perfectly when I first installed the server using OES2 SP1. After the upgrade to OES2 SP2, the migration tool reports it can't mount the source volumes. I followed all the TIDs I could find, reloaded nvfs,etc. it still fails.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

mfinn wrote:
> We have the same issue as well. It worked perfectly when I first
> installed the server using OES2 SP1. After the upgrade to OES2 SP2, the
> migration tool reports it can't mount the source volumes. I followed
> all the TIDs I could find, reloaded nvfs,etc. it still fails.
>
>

Migration Tools uses ncpmount command to mount the volumes in OES2SP1.
But we heard a couple of issues where ncpmount fails to mount the source
server volumes. So we started using novell client service which got
released in OES2SP2 to map source volumes.

There is an issue that after installing novell-client, sometimes the
service won't start. In that case, we need to start the service manually
for Migration Tools to use. It is documented in trouble shoot section
http://www.novell.com/documentation/oes2/mig_tools_lx/?page=/documentation/oes2/mig_tools_lx/data/bookinfo.html#bookinfo

If you observe the volumes are not getting mapped by Migration Tools
even after starting the 'rcnovfsd' service, then you can file an SR with
Novell.

Thanks,
Ramesh
0 Likes
hbloupot
New Member.

Re: OES2sp2 miggui Failed to mount volume

Ramesh;1897644 wrote:
mfinn wrote:
> We have the same issue as well. It worked perfectly when I first
> installed the server using OES2 SP1. After the upgrade to OES2 SP2, the
> migration tool reports it can't mount the source volumes. I followed
> all the TIDs I could find, reloaded nvfs,etc. it still fails.
>
>

Migration Tools uses ncpmount command to mount the volumes in OES2SP1.
But we heard a couple of issues where ncpmount fails to mount the source
server volumes. So we started using novell client service which got
released in OES2SP2 to map source volumes.

There is an issue that after installing novell-client, sometimes the
service won't start. In that case, we need to start the service manually
for Migration Tools to use. It is documented in trouble shoot section
Novell Documentation

If you observe the volumes are not getting mapped by Migration Tools
even after starting the 'rcnovfsd' service, then you can file an SR with
Novell.

Thanks,
Ramesh


Hi,

We did a workaround where we just use the migfiles executable in /opt/novell/migration/sbin and that works fine.
./migfiles -s <ip-source> -v <source-volume-name> -V <target-volume-name> -i After that you just fill out the questions and it copies.

Regards,

Hans
0 Likes
rob_collins Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

hbloupot;1897684 wrote:
Hi,

We did a workaround where we just use the migfiles executable in /opt/novell/migration/sbin and that works fine.
./migfiles -s <ip-source> -v <source-volume-name> -V <target-volume-name> -i After that you just fill out the questions and it copies.

Regards,

Hans


Does this include the trustees etc or would you have to run the command line tools for this afterwards? Why did Novell have to change this. It worked perfectly.
0 Likes
gldavis1 Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

There was a tid written for some ruby issues after upgrading to SP2, this may be related to this issue. See URL...


http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7004949&sliceId=2&docTypeID=DT_TID_1_1&dialogID=107391110&stateId=0%200%20107387663
0 Likes
cgaa183 Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

Thankyou all for helpful suggestions, I'll go through them.

1. novfsd
/etc/rc.d/novfsd status
running

/etc/rc.d/novfsd restart
Stopping Novell novfs daemon...
done
Starting Novell novfs daemon...

No Config File Found - Using Defaults
novfsd: Novell Client for Linux Daemon
Copyright 1992-2005, by Novell, Inc. All rights reserved.
Version 3.0.1-503
done

Nothing changes, so I don't think that was the problem in this case.

2. try using migfiles
/opt/novell/migration/sbin/migfiles -s 138.37.100.118 -v APPS -V APPS

The result:
Error:
Error: nbackup: Unable to retrieve the Target Service Name list from 138.37.100.118
Error:
Fatal: nbackup command failed to execute: nbackup: Connection denied

This might be informative to someone who knows a little more than me. I wonder if I can call it with options to get more information. I have just re-checked I can attach and mount volumes with the same username from another system.

3. ruby version

rpm -qa |grep ruby
ruby-1.8.4-17.20
rubygems-0.9.2-4.4
rubygem-needle-1.3.0-1.5
rubygem-net-sftp-1.1.0-1.5
ruby-devel-1.8.4-17.20
rubygem-net-ssh-1.0.9-1.5

Doesn't appear to be an afflicted version and migfiles --help tells me all about the options available.


As #2 looked interesting I thought I'd look at it a bit more. I turned up TID 7001767. The reason migfiles failed for me was that SMDR and TSAFS weren't loaded, at least I don't get the error and file migration appears to start now they are loaded, though it does appear to have ceased copying files rather prematurely....

Going back to volmount.rb I now realise its using ncpfs, and not a lightweight Novell client. So I tried mounting a volume by hand:

qmwcc28:~ # ncpmount -S 138.37.100.118 -U joshua.sys.qmw K
Logging into 138.37.100.118 as JOSHUA.SYS.QMW
Password:
ncpmount: Server not found (0x8847) when trying to find 138.37.100.118

A bit of a giveaway, but why doesn't it work?
It seems I need to use -A DNSname -S servername and then it works.
The next important bit seems to be
/opt/novell/ncpserv/sbin/ncpshell --volumes --ip=138.37.100.118 --u="joshua.sys.qmw"
which executed by hand lists volumes correctly with the output:
Please enter your password ?
[0] SYS
[1] _ADMIN
[2] APPS
3 NCP Volumes Mounted

"ncpshell" appears to be from Novell's client for Linux so I don't understand why we'd be trying to use that if we're using ncpfs, and we already know which volumes are mounted by looking in the folder in which we mounted the server using ncpfs. AFAICS is used to invoke NLMs on NetWare remotely using OES so its not testing anything we don't already know.

This takes me inevitably to "nwmap". "nwmap" is also from Novell's client for Linux so maybe the ncpfs stuff is unnecessary.
/opt/novell/ncl/bin/nwmap -s 138.37.100.118 -d sys -v SYS
produces:
map: server not Found:138.37.100.118 - drive sys not mapped

nwmap doesn't ask for a username. Maybe I'm wrong, but as far as the Novell client goes I don't think it can have attached or logged into the source server (ncpfs having a different connection table and ncpshell asking the remote server to return the answer). I can't actually see where /volmount.rb is calling nwmap at the moment but the results I get my calling it at the command prompt with the same options given in the log are the same.

I've tried logging in using nwlogin, but that fails too saying:
Cannot perform login: The system could not log you into the network.
Make sure that the name and connection information are correct, then type your password again.

ncl_scanner -T does list NDS trees but I suspect its only querying an SLP server and nothing more useful. ncl_scanner -S produces:
INFORMATION FOR SERVER [QMWCC18] :
Server Name : [QMWCC18]
Bindery : [FALSE]
eDirectory Context : []
should it show a context?

Looking at the files of the Novell client on the system, it looks a rather cut down set with no config files. Even having introduced protocol.conf the situation is not improved, but I'm now sure the problem lies in this area. Possibly a full client installation is required, or maybe there is something else wrong which is preventing the client from working correctly. namcd is looking suspect.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

cgaa183 wrote:
> Thankyou all for helpful suggestions, I'll go through them.
>
> 1. novfsd
> /etc/rc.d/novfsd status
>
> running
>
> /etc/rc.d/novfsd restart
> Stopping Novell novfs daemon...
>
> done
> Starting Novell novfs daemon...
>
> No Config File Found - Using Defaults
> novfsd: Novell Client for Linux Daemon
> Copyright 1992-2005, by Novell, Inc. All rights reserved.
> Version 3.0.1-503
>
> done
>
> Nothing changes, so I don't think that was the problem in this case.
>

did you restart the server after installing OES2 SP2?

> 2. try using migfiles
> /opt/novell/migration/sbin/migfiles -s 138.37.100.118 -v APPS -V APPS
>
> The result:
> Error:
> Error: nbackup: Unable to retrieve the Target Service Name list from
> 138.37.100.118
> Error:
> Fatal: nbackup command failed to execute: nbackup: Connection denied
>

migfiles is not able to connect to the TSA on the source server. Either
TSAFS is not loaded on the source server or not able to locate the TSA
using SLP.

> This might be informative to someone who knows a little more than me. I
> wonder if I can call it with options to get more information. I have
> just re-checked I can attach and mount volumes with the same username
> from another system.
>
> 3. ruby version
>
> rpm -qa |grep ruby
> ruby-1.8.4-17.20
> rubygems-0.9.2-4.4
> rubygem-needle-1.3.0-1.5
> rubygem-net-sftp-1.1.0-1.5
> ruby-devel-1.8.4-17.20
> rubygem-net-ssh-1.0.9-1.5
>
> Doesn't appear to be an afflicted version and migfiles --help tells
> me all about the options available.
>
>
> As #2 looked interesting I thought I'd look at it a bit more. I turned
> up TID 7001767. The reason migfiles failed for me was that SMDR and
> TSAFS weren't loaded, at least I don't get the error and file migration
> appears to start now they are loaded, though it does appear to have
> ceased copying files rather prematurely....
>
> Going back to volmount.rb I now realise its using ncpfs, and not a
> lightweight Novell client. So I tried mounting a volume by hand:
>
> qmwcc28:~ # ncpmount -S 138.37.100.118 -U joshua.sys.qmw K
> Logging into 138.37.100.118 as JOSHUA.SYS.QMW
> Password:
> ncpmount: Server not found (0x8847) when trying to find 138.37.100.118
>
> A bit of a giveaway, but why doesn't it work?
> It seems I need to use -A DNSname -S servername and then it works.
> The next important bit seems to be
> /opt/novell/ncpserv/sbin/ncpshell --volumes --ip=138.37.100.118
> --u="joshua.sys.qmw"
> which executed by hand lists volumes correctly with the output:
> Please enter your password ?
> [0] SYS
> [1] _ADMIN
> [2] APPS
> 3 NCP Volumes Mounted
>
> "ncpshell" appears to be from Novell's client for Linux so I don't
> understand why we'd be trying to use that if we're using ncpfs, and we
> already know which volumes are mounted by looking in the folder in which
> we mounted the server using ncpfs. AFAICS is used to invoke NLMs on
> NetWare remotely using OES so its not testing anything we don't already
> know.
>
> This takes me inevitably to "nwmap". "nwmap" is also from Novell's
> client for Linux so maybe the ncpfs stuff is unnecessary.
> /opt/novell/ncl/bin/nwmap -s 138.37.100.118 -d sys -v SYS
> produces:
> map: server not Found:138.37.100.118 - drive sys not mapped
>


ncpmount uses udp as the default. Add the option -o tcp to the ncpmount
command then mount should work.


> nwmap doesn't ask for a username. Maybe I'm wrong, but as far as the
> Novell client goes I don't think it can have attached or logged into the
> source server (ncpfs having a different connection table and ncpshell
> asking the remote server to return the answer). I can't actually see
> where /volmount.rb is calling nwmap at the moment but the results I get
> my calling it at the command prompt with the same options given in the
> log are the same.
>

if there is an existing connection to the same tree, nwmap does not ask
for user name. Use the command "nwconnections" to check the existing
connections. Use nwlogout to logout the connection. check
/var/opt/novell/nclmnt/root/ for any stale entries.

> I've tried logging in using nwlogin, but that fails too saying:
> Cannot perform login: The system could not log you into the network.
> Make sure that the name and connection information are correct, then
> type your password again.
>
> ncl_scanner -T does list NDS trees but I suspect its only querying an
> SLP server and nothing more useful. ncl_scanner -S produces:
> INFORMATION FOR SERVER [QMWCC18] :
> Server Name : [QMWCC18]
> Bindery : [FALSE]
> eDirectory Context : []
> should it show a context?
>
> Looking at the files of the Novell client on the system, it looks a
> rather cut down set with no config files. Even having introduced
> protocol.conf the situation is not improved, but I'm now sure the
> problem lies in this area. Possibly a full client installation is
> required, or maybe there is something else wrong which is preventing the
> client from working correctly. namcd is looking suspect.
>
>

You do not need all files for Novel Client. If you want

You can logout all connections using the command "nwlogout -a" and try
the nwmap command again.
"/opt/novell/ncl/bin/nwmap -s 138.37.100.118 -d
/var/opt/novell/migration/cc18/fs/mnt/source/SYS -v SYS"

Looks like the novell client is failed to resolve the IP address. You
can do the following to configure different name resolution methods in
the following way:
Create a file: /etc/opt/novell/ncl/protocol.conf with data.
Name_Resolution_Providers=NCP,SLP,DNS
then restart rcnovfsd deamon using the command "rcnovfsd restart"

do you see any NCP errors in the network packet trace?

regards
Praveen
0 Likes
jpardo Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

Hi all,

I have the same problem, in my scenario have cluster and i can resolv the problem enable "cluster" option and "show cluster volumes nodes2 in tsa.cfg. Can change this setting in sys:\etc\sms\tsa.cfg, now all work fine.
Jose





Praveen Kumar;1902122 wrote:
cgaa183 wrote:
> Thankyou all for helpful suggestions, I'll go through them.
>
> 1. novfsd
> /etc/rc.d/novfsd status
>
> running
>
> /etc/rc.d/novfsd restart
> Stopping Novell novfs daemon...
>
> done
> Starting Novell novfs daemon...
>
> No Config File Found - Using Defaults
> novfsd: Novell Client for Linux Daemon
> Copyright 1992-2005, by Novell, Inc. All rights reserved.
> Version 3.0.1-503
>
> done
>
> Nothing changes, so I don't think that was the problem in this case.
>

did you restart the server after installing OES2 SP2?

> 2. try using migfiles
> /opt/novell/migration/sbin/migfiles -s 138.37.100.118 -v APPS -V APPS
>
> The result:
> Error:
> Error: nbackup: Unable to retrieve the Target Service Name list from
> 138.37.100.118
> Error:
> Fatal: nbackup command failed to execute: nbackup: Connection denied
>

migfiles is not able to connect to the TSA on the source server. Either
TSAFS is not loaded on the source server or not able to locate the TSA
using SLP.

> This might be informative to someone who knows a little more than me. I
> wonder if I can call it with options to get more information. I have
> just re-checked I can attach and mount volumes with the same username
> from another system.
>
> 3. ruby version
>
> rpm -qa |grep ruby
> ruby-1.8.4-17.20
> rubygems-0.9.2-4.4
> rubygem-needle-1.3.0-1.5
> rubygem-net-sftp-1.1.0-1.5
> ruby-devel-1.8.4-17.20
> rubygem-net-ssh-1.0.9-1.5
>
> Doesn't appear to be an afflicted version and migfiles --help tells
> me all about the options available.
>
>
> As #2 looked interesting I thought I'd look at it a bit more. I turned
> up TID 7001767. The reason migfiles failed for me was that SMDR and
> TSAFS weren't loaded, at least I don't get the error and file migration
> appears to start now they are loaded, though it does appear to have
> ceased copying files rather prematurely....
>
> Going back to volmount.rb I now realise its using ncpfs, and not a
> lightweight Novell client. So I tried mounting a volume by hand:
>
> qmwcc28:~ # ncpmount -S 138.37.100.118 -U joshua.sys.qmw K
> Logging into 138.37.100.118 as JOSHUA.SYS.QMW
> Password:
> ncpmount: Server not found (0x8847) when trying to find 138.37.100.118
>
> A bit of a giveaway, but why doesn't it work?
> It seems I need to use -A DNSname -S servername and then it works.
> The next important bit seems to be
> /opt/novell/ncpserv/sbin/ncpshell --volumes --ip=138.37.100.118
> --u="joshua.sys.qmw"
> which executed by hand lists volumes correctly with the output:
> Please enter your password ?
> [0] SYS
> [1] _ADMIN
> [2] APPS
> 3 NCP Volumes Mounted
>
> "ncpshell" appears to be from Novell's client for Linux so I don't
> understand why we'd be trying to use that if we're using ncpfs, and we
> already know which volumes are mounted by looking in the folder in which
> we mounted the server using ncpfs. AFAICS is used to invoke NLMs on
> NetWare remotely using OES so its not testing anything we don't already
> know.
>
> This takes me inevitably to "nwmap". "nwmap" is also from Novell's
> client for Linux so maybe the ncpfs stuff is unnecessary.
> /opt/novell/ncl/bin/nwmap -s 138.37.100.118 -d sys -v SYS
> produces:
> map: server not Found:138.37.100.118 - drive sys not mapped
>


ncpmount uses udp as the default. Add the option -o tcp to the ncpmount
command then mount should work.


> nwmap doesn't ask for a username. Maybe I'm wrong, but as far as the
> Novell client goes I don't think it can have attached or logged into the
> source server (ncpfs having a different connection table and ncpshell
> asking the remote server to return the answer). I can't actually see
> where /volmount.rb is calling nwmap at the moment but the results I get
> my calling it at the command prompt with the same options given in the
> log are the same.
>

if there is an existing connection to the same tree, nwmap does not ask
for user name. Use the command "nwconnections" to check the existing
connections. Use nwlogout to logout the connection. check
/var/opt/novell/nclmnt/root/ for any stale entries.

> I've tried logging in using nwlogin, but that fails too saying:
> Cannot perform login: The system could not log you into the network.
> Make sure that the name and connection information are correct, then
> type your password again.
>
> ncl_scanner -T does list NDS trees but I suspect its only querying an
> SLP server and nothing more useful. ncl_scanner -S produces:
> INFORMATION FOR SERVER [QMWCC18] :
> Server Name : [QMWCC18]
> Bindery : [FALSE]
> eDirectory Context : []
> should it show a context?
>
> Looking at the files of the Novell client on the system, it looks a
> rather cut down set with no config files. Even having introduced
> protocol.conf the situation is not improved, but I'm now sure the
> problem lies in this area. Possibly a full client installation is
> required, or maybe there is something else wrong which is preventing the
> client from working correctly. namcd is looking suspect.
>
>

You do not need all files for Novel Client. If you want

You can logout all connections using the command "nwlogout -a" and try
the nwmap command again.
"/opt/novell/ncl/bin/nwmap -s 138.37.100.118 -d
/var/opt/novell/migration/cc18/fs/mnt/source/SYS -v SYS"

Looks like the novell client is failed to resolve the IP address. You
can do the following to configure different name resolution methods in
the following way:
Create a file: /etc/opt/novell/ncl/protocol.conf with data.
Name_Resolution_Providers=NCP,SLP,DNS
then restart rcnovfsd deamon using the command "rcnovfsd restart"

do you see any NCP errors in the network packet trace?

regards
Praveen
0 Likes
bogdansk Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

This seems to be one of my issues, but when I try to exeecute:

rug in -c OES2-SP2-POOL ruby

I get:

ERROR: 'ruby' is not available
0 Likes
Highlighted
gleahy Absent Member.
Absent Member.

Re: OES2sp2 miggui Failed to mount volume

This worked for me: 7001767 (smdr config)
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.