client Netvault service keeps going down seconds after being started.
Initially this may be an issue either with a lack of disk space on the partition where the Netvault client software has been installed or it could be due to a lack of shared memory resources on the client machine. It may also be however that the client machine is unable to receive acknowledgements over the network from the Network server
Initially check there is sufficient disk space on the disk where Netvault client has been installed. If Windows check the service is running with 'interact with desktop' enabled (Computer->Manage->Services, right click on nvpmgr->properties->logon). Also open the nvconfigurator go to Process Manager and ensure the field 'shared memory used for process table' is set to at least 16000.
If the problem remains enable trace on the machine (nvconfigurator->general->generate debugging files). Attempt to restart the service once more. After it goes down go to the resulting trace directory and look at the comms manager (trace. If the following are seen it means the local process manager is unable to start as it cannot start the local comms manager until an acknowledgement is received from the Netvault server it was initally added to:
Program manager of the client is unable to spawn the Comms Manager:
0 MESSAGE :4040 261 1 134743 Unexpected network error
0 PMGR :4040 112 0 134743 Failed to connect process manager to comms manager
Do forward and reverse DNS Lookups between the Netvault server and the client machine using nslookup <host_name/ip_address>
You will probably find that DNS is resolving incorrectly between the machines which needs to be addressed by the Network Admin.
