Windows Server 2008 RDS / TS gets stuck

We are running Windows Server 2008 R2, Remote Desktop Services.

The server is a Dell R410, Intel Zeon E5520, 2.26GHz 8M cache, 8GB 1066MHz Dual Ranked RDIMMs, Advanced ECC mirror.

Out of the factory the memory was set to Mirror, so only 4GB was available. I thought, that's what was crashing the system. So I changed it to Optimized mode, and now all 8GB are available, but it still got stuck this morning.

All remote users froze, and could not reconnect. Luckily I was logged in via the console at the time. It showed that 4GB of memory was still available, and the CPU was not too heavily utilized.
InfoTechEEAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Darius GhassemCommented:
Disable TCP Chimney.

http://support.microsoft.com/kb/951037

Remove any AV for testing.
0
InfoTechEEAuthor Commented:
Quick question. After reading that article it seems taht TCP Chimney is a good thing. It allows to take the TCP load off of the processor and offload it to the network card. Sounds like the network card is helping out the CPU. Isn't this a good thing. Why would we want to turn it off.

I'll give it a try, thanks.
0
Darius GhassemCommented:
TCP Chimney doesn't work all the time and causes multiple issues. Search EE for TCP Chimney.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

InfoTechEEAuthor Commented:
This did not help. The server froze today again. While frozen, I tried pinging it, and it worked. However, our network monitoring software which uses WMI was unable to contact the server. RDP didn't work either.
0
Darius GhassemCommented:
What AV are you running?
0
InfoTechEEAuthor Commented:
ESET
0
Darius GhassemCommented:
Remove ESET for testing since there are known issues with AVs and Windows 2008 server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
InfoTechEEAuthor Commented:
Removed. Will monitor the situation to see if the server crashes again.
0
Darius GhassemCommented:
Try disable TCP Chimney on client machine.
http://www.alacritech.com/Support/FAQs/DisableOffload.aspx
0
InfoTechEEAuthor Commented:
On all the clients? This seems to be a server issue, not so much the client. After client disconnects from the Frozen Server, he is able to browse the web, log on to the VPN, and use other methods to connect to our backup systems.
0
Darius GhassemCommented:
The frozen first then the client.
0
Darius GhassemCommented:
0
InfoTechEEAuthor Commented:
Removed ESET and the server hasn't crashed since.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.