"No response from server" appears when adding a Normal Server to the ServerProtect for Microsoft Windows/Novell Netware Information Server

Support
Solution ID Last Updated
0111665 Apr. 24, 2013 1:23 AM (PST)


Product / Version Platform
ServerProtect for Microsoft Windows/Novell Netware - 5.8;
Netware - version 6.5, Windows - 2003 Enterprise, Windows - 2003 Standard, Windows - 2008 Enterprise, Windows - 2008 Standard

Problem Description

After your install the Normal Server, the system would not add it to the Information Server (IS). When trying to add the Normal Server (NS) using the management console, you receive the following error message:
No response from server

Solution

This issue occurs when you run the ServerProtect for Microsoft Windows/Novell Netware setup on the server to install only the NS component.
To resolve this issue, do any of the following:
[ Expand All ]

 

Option I: Use the TCP/IP protocol instead of Remote Procedure Call (RPC)

  1. On the IS, go to the \Program Files\trend\Sprotect folder and back up the TMRPC.ini file.
  2. Open and edit the TMRPC.ini file.
  3. Look for the entry of the NS that you want to add. This may be the server name or IP address. If it does not exist, add the entry and give it the value "2".
    Example:
    server1=2 or xxx.xxx.xxx.xxx=2
  4. Save and close the TMRPC.ini file.
  5. Restart the Trend ServerProtect Agent service.
  6. On the Normal Server that could not be added to IS, go to the \Program Files\trend\Sprotect folder.
  7. Back up and edit the TMRPC.ini file.
  8. Look for the entry of the IS that you want to add. This may be the server name or IP address. If it does not exist, add the entry and give it the value "2".
    Example:
    server1=2 or xxx.xxx.xxx.xxx=2
  9. Save and close the TMRPC.ini file.
  10. Restart the Trend Server Protect service.
  11. Log on to the ServerProtect management console and retry adding the NS.

 

Option II: Use the Registry Editor

  1. Open the Registry Editor.
    Important: Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems.
  2. Go to HKLM/Software/Microsoft/Rpc/ClientProtocols.
    If there is no entry for Client Protocols in the registry, then recreate the whole key. Do the following:
    1. In the Registry Editor, create the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols subkey.
    2. Make sure that the following values are available:
      Name Type Data
      -------------------------------
      ncacn_http REG_SZ rpcrt4.dll
      ncacn_ip_tcp REG_SZ rpcrt4.dll
      ncacn_nb_tcp REG_SZ rpcrt4.dll
      ncacn_np REG_SZ rpcrt4.dll
      ncadg_ip_udp REG_SZ rpcrt4.dll
    3. Restart your computer.
  3. If you have another working Normal Server, then export the same registry key and then import it on the target server.
  4. Restart the server and try again.


Rate this Solution
Did this article help you?

Please provide your comments to help us improve this solution.

 
  *This form is an automated system. General questions, technical, sales and product-related issues submitted through this form will not be answered.
 
 

Connect with us on