Information on some typical MCU logs

*JoinNet Disconnect, recv return fails, error = 10054/0x2746
The connection is disconnected because of error 10054.
it is typically caused by network error.
check 
https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668%28v=vs.85%29.aspx
for more information

*JoinNet Disconnect, recv return fails, error = 10053/0x2745
The connection is disconnected because of error 10053.
check 
https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668%28v=vs.85%29.aspx
for more information

*JoinNet Disconnect, recv return fails, error = xxxxx/yyyy
The connection is disconnected because of error xxxxx.
check 
https://msdn.microsoft.com/en-us/library/windows/desktop/ms740668%28v=vs.85%29.aspx
for more information

*JoinNet Disconnect, timeout
The connection is disconnected by MCU because the JoinNet client doesn't respond for ~1minute
typically caused by network problem

*JoinNet Disconnect, too slow(>5s) being kicked out
MCU ask a JoinNet to leave. Normally JoinNet will leave immediately. If the JoinNet still stay connected after 5 seconds, MCU will force the JoinNet out.
typically caused by network problem.

*JoinNet Disconnect, send error1
*JoinNet Disconnect, send error2
The connection is disconnected by MCU because MCU detect error when trying to send some data.
typically caused by network problem.

*JoinNet Disconnect, remote close
The connection is disconnected by peer.
typically caused by quitting JoinNet or network problem.

*JoinNet Disconnect, command xxx return error yyy
The connection is disconnected due to protocol error
Please report to HomeMeeting for investigation