Without NetRAID Assistant, the client(s) and server(s) connect normally, but the
NetRAID Assistant cannot connect to any servers
For NetRAID Assistant to connect to a server, it must resolve the server via
TCP/IP. Ping the server by name from the client or server that will run HP
NetRAID Assistant. If this is unsuccessful, then the client or server that will run
HP NetRAID Assistant cannot resolve the server using TCP/IP. Confirm the
The IP addresses are unique.
The subnet mask is not causing a group resolution problem.
The hosts file contains correct names and IP addresses for all servers with
HP NetRAID Series adapters to be managed.
No response when connecting to a server; may get Server Not Responding
message after several minutes
The server is likely to be down and the connection attempt/timeout may take two
minutes before a message is generated. Be sure the selected server is up.
If the server is still not up when the timeout message is
displayed, HP NetRAID Assistant will exit.
Can't unload raidserv.nlm
If the adapter in a NetWare server is being accessed by a configuration utility (HP
NetRAID Assistant in Full Access mode or HP NetRAID Config), the
raidserv.nlm module cannot be unloaded until the adapter is no longer being
accessed. This prevents a critical operation in the adapter, such as a disk rebuild,
from being interrupted.
HP NetRAID Assistant does not list any servers when started (other than "local")
When HP NetRAID Assistant starts, the Main Screen only lists
"<clientname>(Local)" in the pull-down list of servers. The Registration Server
may be down, or no servers may have checked in with it.
Be sure that the Registration Server is working and that it started before the other
servers. Servers can only log into the Registration Server when the access server
(NT) or raidserv.nlm (NetWare) executes.