One, due
Cause someone to contact me their mac computer connection is not shared directory of Windows, Windows PC connection is normal, there is no error, the connection box shake twice gone
Second, troubleshoot
1, I would like to see mstsc login server, the results also log server is not on, error, error Remote Desktop can not even verify the identity of the remote computer, because of the time difference between your computer and the remote computer.
Suspected of Windows Server clock synchronization something is wrong. Fortunately, after a while children and other connected, view logs, and sure enough clock synchronization failed:
Fortunately, later you can connect to, or else only use local accounts connected to
2, again with mac shared directory access, or not, this is why? Reference article or not after https://blog.csdn.net/u013897534/article/details/81393814 operation. A few days ago obviously also good, is it Windows or mac update some of the content of lead? View Windows update records, recently did not install the new patch.
Check the system log again, found an error connecting domain controller failure:
So the next ping dns server, packet loss really serious, and that did understand, is due to dns server connection is not on - domain controller can not resolve the domain name server - not on the domain controller server connection - a domain account login fails .
Thus stable dns replacement address (network modifications and Sharing Center), connected to the mac again, can be connected properly.
IV Summary
This concludes the fault reason:
in general are caused by dns server connection timeout, dns server previously set less stable, after the connection fails, the domain controller and domain name ntp server can not resolve a stable, resulting in a problem: the host server and the time difference leading to a remote connection fails, also had a problem: the domain controller name resolution fails, the connection is not on the domain controller server, resulting in a domain account to log user can not login
solution: modify the local connection dns configuration, the replacement for the stable dns server address to