-
Title
Troubleshooting NetVault network connections / connectivity. -
Description
Tools to troubleshoot NetVault network connections / connectivity.
-
Resolution
When using the various tools to troubleshoot the network we need to understand what each tool can provide and when to use a specific tool. Tools that can be used for troubleshooting the network: Ping, Telnet, Netsh, Netstat, lsof, nmap / zenmap & Wireshark.
PING
When troubleshooting network issues such as “Failed to start Plugin” (kb article 1759). Using the command of “PING” is normally used to check latency on the network. PING uses “Internet Control Message Protocol” (ICMP). ICMP is a control protocol, meaning that it does not carry application data, but rather information about the status of the network itself. Using “PING” can only establish that there is communications and the latency between the devices. It does not validate ports or status of ports or which protocol is available.
TELNET
When using the command “telnet”, the user can specify the destination using IP address or name and which port to communication to. TELNET allows us to communicate using a specific port and verify that certain ports are accessible. TELNET does not provide information which ports are open or what protocol is being used. The command to use telnet is: “telnet ”. For more information, see NetVault Knowledge Based article titled: “Using 'telnet' to test NetVault connectivity thru a firewall”.
NETSH (windows only)
On Windows machines there may a utility called “netsh” that provides information on which ports are open on the server and the protocol being used. The command is “netsh firewall show state”. For more information see NetVault Knowledge Based article titled “How to check Windows firewall using netsh command line utility, to see if ports are open”. Example: C:\>netsh firewall show state
NETSTAT / LSOF (linux /unix)
Checks the network stack and which ports are currently in use.
NMAP / ZENMAP (unix, linux / windows)
Nmap ("Network Mapper") is a free and open source (license) utility. Using the “nmap” command as follows; “"nmap -sTU -O localhost”, provides which ports are listening for TCP and UDP connections from the network. Zenmap uses a GUI interface instead of the command line that namp uses.
WIRESHARK (Windows, Linux and Mac OS X 10.5.5 and above)
Wireshark is a free and open source utility. Using the Wireshark’s GUI you are able to capture data and analyze data. When looking for NetVault communications you will need to filter on TCP and UDP protocols and look for ports 20031 and above.
NOTE: We provide the above troubleshooting information to assist you to determine if the ports and protocols are available for the NetVault software.
Resources:
NMAP: http://nmap.org/
Wireshark: http://www.wireshark.org/
NetVault Knowledge Based articles
“Using 'telnet' to test NetVault connectivity thru a firewall”.
“How to check Windows firewall using netsh command line utility, to see if ports are open.” -
Additional Information
BakBone SFDC Solution Number: 00005452