Trying to figure out a problem where the server not responds to rdp or smb connections after being not used for around 3 hours (i.e. all users are out and only background services running). Two onboard 1GB Nics are teamed switch-dependent LACP mode with Mikrotik RB2011iL 802.3ad l2+l3 hash policy. The connection restores after one of two randomly:
- Logging in through supermicro kvm interface and entering credentials (connection restores itself and server starts responding again, which is weird for me)
- Same as 1 but connection restores only after teaming network interface is restarted manually.
Looks like the server is going sleep for some reason, but some of services are still up, for example I can establish an L2TP connection to router, which sends a RADIUS request to the server (so the radius request goes ok, NPS log tells that I have authenticated sucessfully). But at that point RDP is still down.
The other thing is that router have no idea that I'm restarting the interface (when in normal case it tells that link is up/down). Also the problem had appeared once before teaming was used, but didn't persisted for long, so I had no idea what happened then, now its back. There's also no logs in event viewer about interface is down or something, only services like NTP start spamming that they are unable to resolve their addresses.
What I've tried so far:
- Updating network drivers to latest available at Supermicro site
- Setting "allow to go sleep" to disabled
- Setting Energy Efficient Ethernet to disabled on both NICs
- Server reboot
What else can I do to resolve this?
Edit: setting the GPO for session expiration time to never seems to be a temporary problem solve. Since I had an active sessions, the server didn't fall to its mysterious sleep and was accessible normally. But anyway this isn't a full answer to the problem, just changes the subject to "why WS stops responding on rdp/smb/pings/probably something else when all user sessions are out"
