|
No connection could be made because the target machine actively refused it |
|
|
|
Resources -
Troubleshooting Guide
|
|
No connection could be made because the target machine actively refused it Cause 1: Giga Vault Storage application is not running in the system. Resolution: In Windows OS. -
Confirm if the Giga Vault Storage application [Giga Vault Storage.exe] is running in the system by using "Task Manager". If the application is not running, start Giga Vault Storage through the Giga Vault Storage system tray application. In Linux OS Verify if the Giga Vault Storage application is running in the system by executing the command 'ps -e |grep Giga Vault Storage'. -
If the application is not running, it can be started by running the "sh startGiga Vault Storage.sh" script in <Giga Vault Storage_HOME> directory. Cause 2: The Giga Vault Storage webconsole is unable to connect the Giga Vault Storage applications UI communication port [by default, 32005]. Resolution: Confirm if the Giga Vault Storage is in the listening mode at the UI communication port. In Windows OS Verify this by running the command 'netstat -an | find "32005"' in the command prompt to check if the port 32005 is in LISTEN state. Run the "telnet <machine name> 32005" command in command prompt to confirm if the webconsole can access the Giga Vault Storage application UI communication port. If any personnel firewall/intrusion detection tools are installed in the system, try adding the Giga Vault Storage.exe, SGTray.exe applications and 32005 default port in the NAT/Firewall configuration's exception list and login to the Giga Vault Storage’s webconsole. In Linux OS. Verify this by running the command 'netstat -an | find "32005"' in the command prompt to check if the port 32005 is in LISTEN state. Run the "telnet <machine name> 32005" command in command prompt to confirm if the webconsole can access the Giga Vault Storage application UI communication port.
|