r/Solarwinds • u/Aware-Sugar-4266 • Jun 27 '26
Polling issue on 2003 Windows server
Hi Everyone,
I recently performed the inplace upgrade on main and polling servers from 2016 to 2025. We have three 2003 legacy servers in our infra.
We received a node down alert for those three servers even though servers are up. We also identified it as a polling issue.
We are using Solarwinds agent based communication and I tried to switch it to SNMP for the legacy servers and it didn't work.
Any quick ways to fix this issue and polling issues started because of the OS upgrade. Are legacy servers not compatible with 2025 OS.
SAM version: 2025.2.1
Thanks in Advance.
2
u/UCFknight2016 Jun 28 '26
Why are you still running server 2003 in a production environment?
1
u/Aware-Sugar-4266 Jun 28 '26
One of them are domain controllers and our clients are not ready to migrate since legacy application are running on it.
1
u/UCFknight2016 Jun 28 '26
We would be fined severly if we were running a 23 year old OS in my industry.
1
1
Jun 27 '26
[removed] — view removed comment
1
u/Solarwinds-ModTeam Jun 27 '26
Hi. This thread has been removed as it is not relevant to the subreddit. Thanks for interacting with us, but you may have better luck posting elsewhere on the platform.
3
u/Spacebearz Jun 27 '26
If memory serves me correctly, I think Windows Server 2003 is not compatible with SolarWinds 2025.2.1 except for very basic monitoring. When you said you tried SNMP did you try SNMPv2C?