Windows 2003 server standard edition: no trap received

[Leonardo_14]

Hi folks!

I have installed Windows 2003 server SE on a HP ProLiant DL360.
On this server I have a network management server.
I would like use this server to display traps incoming from other management server.

As a test, I'm sending snmp trap to this server from another server on port 162, but theese traps are not displayed on the TrapReceiver tool.

I captured the traps trought a wireshark, but the TrapReceiver doesn't trace the trap.

Infact the Network management SW doeesn't trace the trap.

The windows firewall is down.
The SNMP Service is UP.

Who stops theese traps?
Seems that was stopped over the datalink layer.

Any helps would be appreciate!
Thanks
Leonardo

[Daniel Leblanc · Accepted solution]

Did you try scan 161 port?

I know that snmp is 161/162

Daniel

[Leonardo_14]

Hi Daniel,

the snmp traps are sending on the 162 port number.

[Daniel Leblanc]

Typically, SNMP uses UDP ports 161 for the agent and 162 for the manager. The Manager may send Requests from any available ports (source port) to port 161 in the agent (destination port). The agent response will be given back to the source port. The Manager will receive traps on port 162. The agent may generate traps from any available port.

Many distributions change this, however, and this is not necessarily always true

Dan

[Leonardo_14]

Yes Ok..

The problem is that.
Seems that some windows service on the management server, stops the trap.

I tryed to sent trap to my computer with a TrapReciver tool (linsten on any port) and the trap are correctly received.

Thus I think there is a service or agent that stop the trap above the datalink layer.

Do you have any idea about that?
Leonardo

[Daniel Leblanc]

A shoot in the dark,local policy could be blocking/Filtering the port?

Dan

[Leonardo_14]

ok it runs!
Thanks :)
Leonardo

[Leonardo_14]

d