David,
I will try "route print" when I get back to work on Monday. What should I look for? What is the purpose of doing route print?

Yeah I think I read somewhere that routers will not transfer brodcast messages also. I will have to investigate if that will be a problem in my application but I assume that the device can and will sometimes be "behind" a router.

Thanks,
Einar

>No, I mean from the DOS command line. Its a built in command of the operating system.
>
>If I remember right, the reason we used a multicast group instead of broadcast is because a broadcast will not go through a router (but don't quote me on that - I'm not a network guru). A multicast message will go through a router. My guess is that your problem has something to do with the broadcast message not being routed. If you extended your logic then broadcasting to 255.255.255.255 would broadcast to every computer on the internet! Clearly this is not so.
>
>
>>David,
>>When you say command line do you mean the message that I am broadcasting? Currently I only brodcast 4 bytes, should I convert the phrase "route print" to ascii bytes representation and try to send that?
>>
>>Thank you for the link I will look closer at it when I get back to work on Monday.
>>
>>Einar
>>
>>>If you type "route print" on the command line what does your routing table look like?
>>>
>>>Instead of broadcasting we use a multicast group. Example is here:http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconusingudpservices.asp
>>>
>>>
>>>>
>>>>I get a response from the device that indicates that the device's IP address is 192.168.50.50, which is correct, but if I broadcast to 192.168.255.255 instead of 192.168.50.255 I do not get a response.
>>>>
>>>>If anyone can give me more information regarding this please let me know. Any article or book refences would be welcome as well.
>>>>
>>>>Thanks,
>>>>Einar