Log files can be taken as per this kb, Win SCP mis attached, we can only find the reason after having look into logs.
1 of 1 people found this helpful
are the DCs that the MWG is connected to located on the same network? Hopefully in the same datacenter? Are you having large amounts of latency between MWG and the DCs? The most common reason is that the DC simply can not keep up with the requests or the latency between the MWG and the DCs is large. MWG is located in the US and MWG was setup for use DNS for DC lookup, and the DC that was returned was in Asia. Obviously this is not a wise setup if that is the case.
Make sure MWG is setup with hardcoded DCs and not using DNS.
The "heartbeat failed" message could mean a couple of different things. Perhaps you have the proxy settings set and the domain memebership issue caused your GUI access to fail.
Pinging isnt representative of what is necessary for a domain membership connection to function properly. MWG must be able to resolve the DC forward and backwards (so you must check DNS too), etc...
There is the authentication debug log which should be turned on for "Managment event" (AND ONLY MANAGMENT EVENTS):
If this is on, then you can find the logs under Troubleshooting > Log Files > Debug > mwg-core_Auth.debug.log.
This will show why a domain controller connection went down.
Thanks Jon, just what I was looking for. I wasn't sure what log file would have the information I need. This debug log was it, thanks again!