Networking Forums

Networking Forums > Computer Networking > Windows Networking > SNMP & Get-Request (unicast vs multicast)

Reply
Thread Tools Display Modes

SNMP & Get-Request (unicast vs multicast)

 
 
agent
Guest
Posts: n/a

 
      06-17-2008, 01:06 PM
Hi all,

i have installed an SNMP agent on a Windows 2003 Server Standard.

Under XP, this agent answers perfectly to SNMP get-request, with both
unicast or multicast destination address.

Under Windows Server 2003, this same agent answer to SNMP get-request only
when the destination address is the ip address of the server (unicast).

Why this difference of behaviour of the SNMP agent between unicast &
multicast address under Windows Server 2003.

Is there any security settings against broadcast/SNMP or something like that?

Here it is the broadcast mask used:

* 255.255.255.255 or
* 10.1.1.255

Unicast address :

* 10.1.1.221 (works fine)

In conclusion i could not discover 2003 server agent with SNMP get-request
with a multicast destination address. The only way to communicate with those
server is to use unicast address...

If i use wireshark on the windows 2003 server i can see both unicast and
multicast SNMP request (get-request). In case of unicast i can see the SNMP
response but not with multicast address.

How to go further in investigation on 2003 ? The server seems to not
propagate the request to my custom agent when the destination address is
multicast....

Best regards,

 
Reply With Quote
 
 
 
 
agent
Guest
Posts: n/a

 
      06-18-2008, 10:49 AM
Any ideas why windows server 2003 does not propaget get-request with
multicast destination address to my extension agent throw the
SnmpExtensionQuery interface. Were as the request is propagted with unicast
address.

IpSec & Firewall Disabled !

The Intel extension agent of my lan driver have the same behaviour ...

It seems to be an OS UDP filtering feature or what else ?!

Help

"agent" wrote:

> Hi all,
>
> i have installed an SNMP agent on a Windows 2003 Server Standard.
>
> Under XP, this agent answers perfectly to SNMP get-request, with both
> unicast or multicast destination address.
>
> Under Windows Server 2003, this same agent answer to SNMP get-request only
> when the destination address is the ip address of the server (unicast).
>
> Why this difference of behaviour of the SNMP agent between unicast &
> multicast address under Windows Server 2003.
>
> Is there any security settings against broadcast/SNMP or something like that?
>
> Here it is the broadcast mask used:
>
> * 255.255.255.255 or
> * 10.1.1.255
>
> Unicast address :
>
> * 10.1.1.221 (works fine)
>
> In conclusion i could not discover 2003 server agent with SNMP get-request
> with a multicast destination address. The only way to communicate with those
> server is to use unicast address...
>
> If i use wireshark on the windows 2003 server i can see both unicast and
> multicast SNMP request (get-request). In case of unicast i can see the SNMP
> response but not with multicast address.
>
> How to go further in investigation on 2003 ? The server seems to not
> propagate the request to my custom agent when the destination address is
> multicast....
>
> Best regards,
>

 
Reply With Quote
 
agent
Guest
Posts: n/a

 
      06-19-2008, 07:40 AM
Hi,

is this the right MS group for this kind of question ?

br

"agent" wrote:

> Any ideas why windows server 2003 does not propaget get-request with
> multicast destination address to my extension agent throw the
> SnmpExtensionQuery interface. Were as the request is propagted with unicast
> address.
>
> IpSec & Firewall Disabled !
>
> The Intel extension agent of my lan driver have the same behaviour ...
>
> It seems to be an OS UDP filtering feature or what else ?!
>
> Help
>
> "agent" wrote:
>
> > Hi all,
> >
> > i have installed an SNMP agent on a Windows 2003 Server Standard.
> >
> > Under XP, this agent answers perfectly to SNMP get-request, with both
> > unicast or multicast destination address.
> >
> > Under Windows Server 2003, this same agent answer to SNMP get-request only
> > when the destination address is the ip address of the server (unicast).
> >
> > Why this difference of behaviour of the SNMP agent between unicast &
> > multicast address under Windows Server 2003.
> >
> > Is there any security settings against broadcast/SNMP or something like that?
> >
> > Here it is the broadcast mask used:
> >
> > * 255.255.255.255 or
> > * 10.1.1.255
> >
> > Unicast address :
> >
> > * 10.1.1.221 (works fine)
> >
> > In conclusion i could not discover 2003 server agent with SNMP get-request
> > with a multicast destination address. The only way to communicate with those
> > server is to use unicast address...
> >
> > If i use wireshark on the windows 2003 server i can see both unicast and
> > multicast SNMP request (get-request). In case of unicast i can see the SNMP
> > response but not with multicast address.
> >
> > How to go further in investigation on 2003 ? The server seems to not
> > propagate the request to my custom agent when the destination address is
> > multicast....
> >
> > Best regards,
> >

 
Reply With Quote
 
Anthony [MVP]
Guest
Posts: n/a

 
      06-20-2008, 08:11 AM
You should probably try the "platformsdk.networking" group,
Good luck,
Anthony
http://www.airdesk.co.uk


"agent" <(E-Mail Removed)> wrote in message
news:2EBA6D1C-7BEB-444C-820B-(E-Mail Removed)...
> Hi,
>
> is this the right MS group for this kind of question ?
>
> br
>
> "agent" wrote:
>
>> Any ideas why windows server 2003 does not propaget get-request with
>> multicast destination address to my extension agent throw the
>> SnmpExtensionQuery interface. Were as the request is propagted with
>> unicast
>> address.
>>
>> IpSec & Firewall Disabled !
>>
>> The Intel extension agent of my lan driver have the same behaviour ...
>>
>> It seems to be an OS UDP filtering feature or what else ?!
>>
>> Help
>>
>> "agent" wrote:
>>
>> > Hi all,
>> >
>> > i have installed an SNMP agent on a Windows 2003 Server Standard.
>> >
>> > Under XP, this agent answers perfectly to SNMP get-request, with both
>> > unicast or multicast destination address.
>> >
>> > Under Windows Server 2003, this same agent answer to SNMP get-request
>> > only
>> > when the destination address is the ip address of the server (unicast).
>> >
>> > Why this difference of behaviour of the SNMP agent between unicast &
>> > multicast address under Windows Server 2003.
>> >
>> > Is there any security settings against broadcast/SNMP or something like
>> > that?
>> >
>> > Here it is the broadcast mask used:
>> >
>> > * 255.255.255.255 or
>> > * 10.1.1.255
>> >
>> > Unicast address :
>> >
>> > * 10.1.1.221 (works fine)
>> >
>> > In conclusion i could not discover 2003 server agent with SNMP
>> > get-request
>> > with a multicast destination address. The only way to communicate with
>> > those
>> > server is to use unicast address...
>> >
>> > If i use wireshark on the windows 2003 server i can see both unicast
>> > and
>> > multicast SNMP request (get-request). In case of unicast i can see the
>> > SNMP
>> > response but not with multicast address.
>> >
>> > How to go further in investigation on 2003 ? The server seems to not
>> > propagate the request to my custom agent when the destination address
>> > is
>> > multicast....
>> >
>> > Best regards,
>> >



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DHCP and Multicast/Unicast Oliver Emslers Linux Networking 0 04-27-2008 11:55 AM
Unicast 2 Multicast etgarnet Linux Networking 1 12-13-2006 09:36 AM
Can Microsoft's RRAS be configured for multicast? Such as in cases where you want to make it a multicast rendevous point? Spin Windows Networking 0 10-26-2006 01:06 PM
SNMP service is running OK, but get no SNMP relevant data from ser Marlon Brown Windows Networking 0 01-18-2006 06:14 PM
Help in dropping inbound multicast and unicast UDP traffic. William Hargrove Linux Networking 0 04-22-2005 01:02 PM



1 2 3 4 5 6 7 8 9 10 11