asked on Windows 2008 R2 slows down over time
We have an IBM server running Windows 2008 R2 Enterprise
It is a Hyper-V server for two virtual machines.
The virtual machines use ports on an Intel network card. We have not noticed any performance issues on the virtual machines.
The host machine has become very slow twice in the last three months. The response time has become slow and Backup Exec is unable to perform any remote agent backups until the system is rebooted.
The host server is using the on-board Broadcom network ports.
It is a Hyper-V server for two virtual machines.
The virtual machines use ports on an Intel network card. We have not noticed any performance issues on the virtual machines.
The host machine has become very slow twice in the last three months. The response time has become slow and Backup Exec is unable to perform any remote agent backups until the system is rebooted.
The host server is using the on-board Broadcom network ports.
Windows Server 2008Windows NetworkingServer Hardware
Last Comment
richn
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
I made the changes specified, but still could not get connectivity to establish without a reboot. Last time I got 35 days after the reboot before the problems appeared. I'll let you know how this goes.
Another problem I had was due to only 1 connected NIC on the 2 available with the other one taking precedence in the Network connections / Advanced / Advanced parameters.
Disabling the unused NIC and/or reorder them solved the problem.
Disabling the unused NIC and/or reorder them solved the problem.
ASKER
Hopefully this will keep my question from being classified as abandoned.
As stated in my previous post, this condition has previously taken at least a month to manifest, so I won't know for another three or four weeks if the solution worked.
As stated in my previous post, this condition has previously taken at least a month to manifest, so I won't know for another three or four weeks if the solution worked.
ASKER
The problem has not returned,so I guess this fixed it.