G
Guest
I have posted this in Windows 2003 networking but no replies received. Maybe
this is a more suitable forum. Basicall, the issue is that in KB324261, the
procedure has you create IP filters that only match traffic that comes from
AND goes to ports 161 and 162 over TCP/UDP. This doesn't happen. When using
any SNMP management product (Dell Openmanage for example), traffic comes from
a random high port, to port 161, then from 161 back to the random high port.
So the filters defined in that article never match.
I had to create rules that say from 161 to any port, use IPSec. This rule
works (verified by Ethereal). Shouldn't this article be updated, or have I
misread it?
this is a more suitable forum. Basicall, the issue is that in KB324261, the
procedure has you create IP filters that only match traffic that comes from
AND goes to ports 161 and 162 over TCP/UDP. This doesn't happen. When using
any SNMP management product (Dell Openmanage for example), traffic comes from
a random high port, to port 161, then from 161 back to the random high port.
So the filters defined in that article never match.
I had to create rules that say from 161 to any port, use IPSec. This rule
works (verified by Ethereal). Shouldn't this article be updated, or have I
misread it?