Re: [twsocket] UDP and TCP on same socket - problem on WS2008 and W7

2012-07-24 Thread Stephen Dickason
>> On starting on either a Windows Server 2008 R2 Standard or Windows >> 7 machine, it comes up with an error message: Address not available >> (#10049 in setsockopt(IP_ADD_MEMBERSHIP)). > >MSDN says: > >IP_ADD_MEMBERSHIP - WSAEADDRNOTAVAIL - Do not call IP_ADD_MEMBERSHIP with >the same group more

Re: [twsocket] UDP and TCP on same socket - problem on WS2008 and W7

2012-07-23 Thread Stephen Dickason
>> On starting on either a Windows Server 2008 R2 Standard or Windows >> 7 machine, it comes up with an error message: Address not available >> (#10049 in setsockopt(IP_ADD_MEMBERSHIP)). > >MSDN says: > >IP_ADD_MEMBERSHIP - WSAEADDRNOTAVAIL - Do not call IP_ADD_MEMBERSHIP with >the same group more

Re: [twsocket] UDP and TCP on same socket - problem on WS2008 and W7

2012-07-20 Thread Angus Robertson - Magenta Systems Ltd
> On starting on either a Windows Server 2008 R2 Standard or Windows > 7 machine, it comes up with an error message: Address not available > (#10049 in setsockopt(IP_ADD_MEMBERSHIP)). MSDN says: IP_ADD_MEMBERSHIP - WSAEADDRNOTAVAIL - Do not call IP_ADD_MEMBERSHIP with the same group more than

[twsocket] UDP and TCP on same socket - problem on WS2008 and W7

2012-07-20 Thread Stephen Dickason
Hi. I'm trying to set up a program that will discover and communicate with peer instances on a local network. Ideally listening on a single port number. Setup: ICSv6 - modified ICSTCPSrv sample program in Turbo Delphi. The code seems to work fine on my XP machine - it picks up its own UDP broa