Date: February 2007
NV Version: N/A
OS Version: N/A
Application version: N/A
Plugin version: N/A
Description:
Using 'telnet' as a simple troubleshooting tool to test connectivity between the Netvault server and clients behind a firewall.
Reason:
Netvault will only work with/through a firewall if the specific port range configured within the firewall is specified in the Netvault configurator. The range is specified using Netvault Configurator under the firewall tab. NetVault server and client needs to be configure for bi-directional communication.
For more information on setting up Netvault to work thru a firewall, please see KB 00001010 “How to set up NetVault to work through a firewall.” Also make sure the firewall is configure properly for bi-directional communication as well as meeting the pre-requisites and requirements on the “How to set up Netvault to work through a firewall.”
To see if the specified port range is configure to listen on both the server and the client and that the firewall is allowing traffic back and forth, telnet can be use as a simple troubleshooting tool to test whether the ports are open end-to-end.
From the server,
telnet
= client behind the firewall
= port in the range that is configure on both the Netvault server and client.
If the result is a message such as "Connecting to ..." and then nothing else, in all likelihood the connection has been successful. Press "CTRL" + "]" to exit.
If the result is a message such as "Connecting to ...Could not connect to the host on port : Connection failed", then there is no application on the client listening that port. Either NetVault is not configured/working correctly (or has not been restarted), or there is some other application (perhaps a local firewall) blocking connections on that port.
To see if the client can start the communication channel with the server, from the client behind the firewall,
telnet
If the result is a message such as "Connecting to ..." and then nothing else, in all likelihood the connection has been successful. Press "CTRL" + "]" to exit.
If the result is a message such as "Connecting to ...Could not connect to the host on port : Connection failed", then there is no application on the client listening that port. Either NetVault is not configured/working correctly (or has not been restarted), or there is some other application (perhaps a local firewall) blocking connections on that port.
Furthermore, to verify that the client is listen on the ports properly, from another machine on the same network as the client,
telnet
If the connection is successful, then the problem is most likely that the firewall is not allowing communication to the Netvault server on the intended ports.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center