NetWorker: How To Troubleshoot Network Related Issues

Summary: This KB provides an overview of how to troubleshoot network-related issues between NetWorker systems.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

Identify the Systems Involved.

It is important to identify which NetWorker systems are involved as this determines which port connections are required. The NetWorker port range must be opened. The port range can be returned by running nsrports on any NetWorker system: 
[root@networker ~]# nsrports
Service ports: 7937-9936 
Connection ports: 0-0
Other ports outside the service port range may be required depending on the processes involved. For example:
  • If the issue is regarding an authentication issue between a NetWorker user interface (NWUI, NMC) and the NetWorker server, port 9090 must also be verified.
  • If the issue is regarding the NMC not reporting job status details or returning workflow/action messages, ports 5672 (non-SSL) or 5671 (SSL) port must be open for the Message Queue Adapter Port.

IP Addresses and Hostnames

To identify the IP address of a system, the following command can be used:

Linux: ifconfig -a 
NOTE: On some systems, you can use the `hostname -i` or `ip a` commands.
 
Windows: ipconfig /all
 
The nslookup command can be used on both Linux and Windows systems to determine name resolution is working: nslookup HOSTNAME
 
Check the system's hosts file to see if any entries are created to alias the IP address to a specific address.
  • Linux: /etc/hosts
  • Windows: C:\Windows\System32\drivers\etc\hosts
NOTE: When using hosts files for address resolution, ensure correct formatting and avoid listing multiple IPs for the same hostname. Only the first entry is used; subsequent duplicates are ignored.

 

NetWorker Software

The following commands can be used to determine which NetWorker packages are installed on a system:

Linux: rpm -qa | grep lgto 
[root@networker ~]# rpm -qa | grep lgto
lgtoserv-19.7.0.1-1.x86_64
lgtonmc-19.7.0.1-1.x86_64
lgtoadpt-19.7.0.1-1.x86_64
lgtonode-19.7.0.1-1.x86_64
lgtonwuiserv-19.7.0.1-1.x86_64
lgtoclnt-19.7.0.1-1.x86_64
lgtoman-19.7.0.1-1.x86_64
lgtoauthc-19.7.0.1-1.x86_64
lgtoxtdclnt-19.7.0.1-1.x86_64
Windows: 
a) from a command prompt, run the following to open a wmic prompt: wmic
b) run the following wmic command to return installed Dell packages:
product where "Vendor = 'Dell EMC'" get name, IdentifyingNumber, PackageName 
C:\Users\Administrator.EMCLAB>wmic
wmic:root\cli>product where "Vendor = 'Dell EMC'" get name, IdentifyingNumber, PackageName
IdentifyingNumber                       Name                                PackageName
{09C46820-6736-41B9-AC6C-BF046A2826D6}  NetWorker                           NwClientMsi.msi
{172FB702-9DD3-4055-B51A-A9BA84A939F8}  NetWorker                           NwServerMsi.msi
{72B28AF4-3E5F-4D25-9783-BDC75834E8DE}  Config Checker                      CfgChkMsi.msi
{21D31D06-642E-4FDE-B5CE-FD5EB60CB5BA}  bbbwt                               BBBWT.msi
{B4A16C17-56BB-4E6A-930D-41ABCF450D44}  NetWorker                           NwStorageNodeMsi.msi
{C5A3D127-D4A2-467D-B59D-1325E990E3A3}  NetWorker Management Web UI Server  mcui.msi
{33B57DB7-A2DE-47FA-B3FC-E4913A44577C}  NetWorker Authentication Service    Authc.msi
{BF3656C8-B9EA-4307-8CC9-F942CBB36839}  NetWorker Extended Client           NwExtClientMsi.msi
{2823290C-7ED5-482E-80A3-EE1103413F47}  File system Agent Boost             FSAGENT.msi
{915EB72E-2207-42C1-A1BD-E80E956CEFE8}  NetWorker Management Console        NMC.msi
{DD0624DF-911C-4ED5-B2F0-B57EA6BEC3CE}  powerprotectagentsvc                AgentService.msi
 

Determining Listening Ports

The NetWorker nsrrpcinfo command can be used to determine which services and ports are listening on a NetWorker server:
Syntax: nsrrpcinfo -p HOSTNAME 
[root@networker ~]# nsrrpcinfo -p localhost
PROGRAM VERSION PROTOCOL PORT SERVICE       
100000  2       tcp      7938 nsrportmapper  Port Mapper
100000  2       udp      7938 nsrportmapper  Port Mapper
390436  1       tcp      9796 nsrexecd       GSS Authentication
390435  1       tcp      8176 nsrexecd       Resource Mirror
390113  1       tcp      7937 nsrexecd       Remote Execution
390440  1       tcp      9667 nsrexecd_nsrfa Remote File Access
390460  1       tcp      7999 auth_proxyd    Authentication Proxy
390103  2       tcp      8121 nsrd           Server
390109  2       tcp      8121 nsrd           Remote Monitoring
390110  1       tcp      8121 nsrd           Jukebox Management
390120  1       tcp      8121 nsrd           License Manager
390107  5       tcp      8885 nsrmmdbd       Media Database
390107  6       tcp      8885 nsrmmdbd       Media Database
390114  1       tcp      8588 nsrdispd       Dispatcher
390105  5       tcp      9845 nsrindexd      Index Database
390105  6       tcp      9845 nsrindexd      Index Database
390439  1       tcp      9198 nsrfa          Remote File Access
390433  1       tcp      8344 nsrjobd        Job Management
390111  1       tcp      9282 nsrsnmd        Storage Node Management
390438  1       tcp      8726 nsrlogd        Audit Logging
390104  905     tcp      8225 nsrmmd         Media Multiplexor
390104  405     tcp      9392 nsrmmd         Media Multiplexor
390104  305     tcp      9577 nsrmmd         Media Multiplexor
390104  205     tcp      9545 nsrmmd         Media Multiplexor
390402  1       tcp      9001 gstd           GST
390104  705     tcp      8070 nsrmmd         Media Multiplexor
390104  805     tcp      8213 nsrmmd         Media Multiplexor
NOTE: This lists most services; however, some processes/ports are not listed. For example, we do not see the AUTHC port (9090) returned in this result. Use this command to check listening ports on another system by entering its Fully Qualified Domain Name (FQDN) or IP address instead of localhost.

Other operating system commands can be used to verify if a port is listening. NetWorker also provides the nsrports command.
Syntax: nsrports -t HOSTNAME -p PORT 
[root@networker ~]# nsrports -t localhost -p 9090
Forward lookup for localhost
Query time:              0.000 sec
Canonical name (CNAME):  localhost
Address (AAAA):          ::1
Connect to port 9090:    Succeeded (0.000 sec)
Address (A):             127.0.0.1
Connect to port 9090:    Succeeded (0.000 sec)

Reverse lookup for ::1
Query time:              0.000 sec
Name:                    localhost6

Reverse lookup for 127.0.0.1
Query time:              0.000 sec
Name:                    localhost
NOTE: If a hostname or IP is specified, this command also checks for DNS resolution.


Other third-party tools (Not included with NetWorker) which can be used:

    • netstat: 

Linux: https://linux.die.net/man/8/netstat This hyperlink is taking you to a website outside of Dell Technologies.
Windows: https://docs.microsoft.com/windows-server/administration/windows-commands/netstat This hyperlink is taking you to a website outside of Dell Technologies.

The general command which works on both Linux and Windows is `netstat -ano` additional commands findstr or grep can be piped to the netstat command to filter for specific ports.

The general command which validates connectivity is `curl -v HOSTNAME:PORT` this command returns additional information; the line we are looking for will state something like: Connected to localhost (::1) port 9090 (#0)
Other messages regarding closed connections can be ignored if a "connected" message is returned.
The general command which validates connectivity is `Test-NetConnection -ComputerName HOSTNAME -port PORT`
  • It may be necessary to determine how many network hops are involved between two systems. The traceroute or tracert command can be used for this on Linux and Windows systems respectively. Using this type of command identifies which network systems are involved when communicating between two NetWorker systems. This may involve going over a WAN or firewalls.
  • ICMP ping can be used for monitoring for packet loss. By default Linux systems run a continuous ping unless a count is provided. To run a continuous ping on Windows systems, run: ping -t HOSTNAME
NOTE: By default ping does not timestamp. In some scenarios, it may be beneficial to correspond a timestamp when a network issue is observed with behavior that is observed in NetWorker. The following can be performed to generate a timestamped ping.

Linux: 
1. Run the following command: 
nohup ping ADDRESS | while read l; do echo `date` $l; done >> /nsr/logs/`hostname`_ping.log &
NOTE: nohup runs the command in the background even if the SSH session is terminated. Open a duplicate session to continue working. If CTRL+C is used in the session ping was run, the command is halted.

Example: 
[root@nsr ~]# nohup ping 192.168.9.106 | while read l; do echo `date` $l; done >> /nsr/logs/`hostname`_ping.log &
[1] 384206
[root@nsr ~]# nohup: ignoring input and redirecting stderr to stdout

[root@nsr ~]# tail -f /nsr/logs/nsr.amer.lan_ping.log
Mon Aug 19 04:09:43 PM EDT 2024 64 bytes from 192.168.9.106: icmp_seq=20 ttl=64 time=0.466 ms
Mon Aug 19 04:09:44 PM EDT 2024 64 bytes from 192.168.9.106: icmp_seq=21 ttl=64 time=0.494 ms
Mon Aug 19 04:09:45 PM EDT 2024 64 bytes from 192.168.9.106: icmp_seq=22 ttl=64 time=0.542 ms
Mon Aug 19 04:09:46 PM EDT 2024 64 bytes from 192.168.9.106: icmp_seq=23 ttl=64 time=0.513 ms
Mon Aug 19 04:09:47 PM EDT 2024 64 bytes from 192.168.9.106: icmp_seq=24 ttl=64 time=0.491 ms
Mon Aug 19 04:09:48 PM EDT 2024 64 bytes from 192.168.9.106: icmp_seq=25 ttl=64 time=0.492 ms

2. To stop the ping, get the PID of the process and terminate it with the kill command.

[root@nsr ~]# ps -ef | grep ping
gdm         3893    2389  0 Aug15 tty1     00:00:08 /usr/libexec/gsd-housekeeping
root      384206  383520  0 16:14 pts/1    00:00:00 ping 192.168.9.106
root      384220  383520  0 16:14 pts/1    00:00:00 grep --color=auto ping
[root@nsr ~]# kill -9 384206

Windows: 
1. Create a .bat file containing:
Example: timed-ping.bat 
@echo off
ping -t ADDRESS |find /v ""|cmd /q /v:on /c "for /l %%a in (0) do (set "data="&set /p "data="&if defined data echo(!date! !time! !data!)" >> "C:\Program Files\EMC NetWorker\nsr\logs\ping.out" 2<&1
2. From an admin command prompt, run the .bat file: timed-ping.bat
3. The script as shown outputs to the nsr\logs folder ping.out file: 
Mon 08/29/2022 12:40:36.53 Reply from 192.168.25.10: bytes=32 time<
Mon 08/29/2022 12:40:36.53 1ms TTL=64
Mon 08/29/2022 12:40:37.53 Reply from 192.168.25.10: bytes=32 time<
Mon 08/29/2022 12:40:37.53 1ms TTL=64
Mon 08/29/2022 12:40:38.53 Reply from 192.168.25.10: bytes=32 time<
Mon 08/29/2022 12:40:38.53 1ms TTL=64
Mon 08/29/2022 12:40:39.53 Reply from 192.168.25.10: bytes=32 time<
Mon 08/29/2022 12:40:39.53 1ms TTL=64
Mon 08/29/2022 12:40:40.53 Reply from 192.168.25.10: bytes=32 time<
Mon 08/29/2022 12:40:40.53 1ms TTL=64
NOTE: The script runs until canceled with CTRL+C or if the command prompt window is closed.
  • Wireshark is another third-party program which can be installed on Windows and Mac systems to monitor network traffic: https://www.wireshark.org/ This hyperlink is taking you to a website outside of Dell Technologies.

Affected Products

NetWorker

Products

NetWorker Family, NetWorker Series
Article Properties
Article Number: 000202820
Article Type: How To
Last Modified: 22 Oct 2025
Version:  7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.