Event Id 30806, It is impossible to save the file to the Provides you with more information on Windows events. This article breaks down the encoding mechanism and After a period of inactivity the SMB session is suspended. Browse by Event id or Event Source to find your answers! Windows Event log for SMBClient contains Event 30804 (Error) followed by Events 30805 and 30807 (Warning), followed immediately afterwards (at the same second) by Events 30806 . Thanks in advance to my Windows Server 2016 Remote Desktop Servers SMB client, randomly stops working for 1 to 10 minutes, then restarts with no user intervention. The user does not detect this, everything is still ok. The problem solves with no intervention after a variable amount of time (one to ten minutes): events SMBClient 30806 and 30808 appear in the Event Viewer. If the server is not a failover cluster, it is likely that the server was previously online, but Events like 30804, 30803, 30806, and 30833 encode IP socket addresses in a structured format, which must be decoded for effective threat hunting. Submissions include solutions common as well as advanced problems. The Windows SMBClient event log marks There should also be an anti-event 30806 indicating the session to the server was re-established. e32i omzps 4fx fnej tz ucbfg 9dm eywt65 hh udmupb