Hi all,
I have a remote support application that uses Indy client/server components.
One of the features we have is a "Find" utility that uses the UDP client to
"discover" instances of the primary application running on the LAN.
On 95% of the machines the find feature works PERFECT as we have implemented
and it returns a nice list of available instances.
But on a few machines trying to open the UDP port results in a 10013 error
which is access denied. The exact same port can be opened in the TCP client
if you know the remote IP address no problem.
So I'm trying to track down how to fix this 10013 error for these few
systems that seem to have it. It seem to be a permissions thing but I
haven't figured how using Indy to force the permissions to be correct.
The offending systems are all on Windows XP pro.
Any help would be much appreciated.
Mark
