first thing, make sure the SNMP TRAP service has total access to UDP port 162.
to verify this on your Windows server type in NETSTAT -ANO
you should see from that list if UDP 162 is available and also see which Process ID (hopefully snmptrap.exe) has it…you definately want SNMPTRAP.EXE to have it and nothing else.
Verify the PID in your Windows Task Manager. The number seen here, 5788, is my process ID and it is SNMPTRAP.EXE.
UDP 0.0.0.0:161 *:* 2360
UDP 0.0.0.0:162 *:* 5788
UDP 0.0.0.0:445 *:* 4
UDP 162 is not listed when I run a netstat -ano, so I guess it's not in use.
By the way, I fired up Syslog Daemon, and enabled that to listen for SNMP Traps, re-ran the natstat -ano, and I sw that the syslod_d service grabbed UDP 162 with a PID of 7744.
I've turned off Syslog Daemon now, and the netstat-ano now doesn't list UDP 162 again.
Any more suggestions?
check in your windows services gui for...SNMP SERVICE service is "Started" "Automatic" and SNMP TRAP SERVICE service is "Started" "Manual"?
SNMP Service (Started/Automatic)
SNMP Trap Service (Started/Automatic)