If you are experiencing issues with the DrAuditor Client connecting to the DrAuditor service it can be indicative of an issue with the DrAuditor service.
Step one: determine if you are connecting to the service with the DrAuditor Client from the machine that hosts the DrAuditor Service or are you connecting form a different machine?
If your connection is from your local or a machine other than the DrAuditor machine, you need to pass in the name or IP address of the DrAuditor machine as opposed to the default “localhost”.
If you are passing in the correct name or IP of the DrAuditor machine, it may be an issue with the service itself stuck in a strange state. In most cases the solution will be to toggle the DrAuditor service.
Stop and restart the DrAuditor service and then try reconnecting with the DrAuditor client
If toggling the DrAuditor server/service does not resolve the issue or the service is not starting back up:
Please make sure the Windows NT user running the DrAuditor service is still an active user.
If this does not resolve the issue please contact Blue Elm.