When the NetVault Service starts, it attempts to resolve all client IP addresses listed in the machines.dat file, which resides in the etc directory under the NetVault installation directory. Resolving all client addresses can cause a significant delay in the service startup and the machine can appear unresponsive during this time. You can reduce or avoid the startup delay by specifying the addresses that are not to be resolved during startup.
1 |
In the Navigation pane, click Change Settings. |
• |
To configure default settings for a NetVault Client, click Choose machine. In the Choose machine drawer, select the client, and click Go to settings. |
3 |
4 |
• |
Comma separated list of networks and addresses not to resolve: To reduce or avoid the startup delay, specify the addresses that are not to be resolved during startup. |
• |
The clients that are offline and listed on the Manage Clients page can also cause the startup delay. To speed up the process, you can remove the clients that are offline or no longer in use. |
• |
In a domain managed by a Windows-based NetVault Server, you may experience a long delay as the service attempts to resolve all client IP addresses using the NBNS (NetBIOS Name Service) protocol. In this environment, you can use the Comma separated list of networks and addresses not to resolve setting to reduce the startup delay. |
5 |
Click Apply to apply the new settings and close the dialog box. |
Use the following procedure to change the default port on the NetVault Server and all clients.
1 |
Open the file nvnmgr.cfg in a text editor. You can find this file in the config directory under the NetVault installation directory. |
Use the following procedure to change the default port on the NetVault Server and all clients.
1 |
Open the file configure.cfg in a text editor. You can find this file in the config directory under the NetVault installation directory. |
2 |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center