Hello,

The only specific data that I can provide at this moment is the piece of
code that is used to perform discovery from the server-side:

DiscoveryManagement dlm = new LookupDiscovery(LookupDiscovery.ALL_GROUPS);

ServiceItem item = new ServiceItem(//...doesn't matter);

        try {
            Thread.sleep(2000);    //To give time to the Lookup Server to
respond
        } catch (InterruptedException e) { e.printStackTrace(); }

        ServiceRegistrar[] srList = dlm.getRegistrars();

//perform the registration with the found Lookups


I relied in this code from the first day, and I constructed my software
making for sure that it worked. Problems only appear when I move the Lookup
execution to a different machine than the one that is executing the server.

More details: we are in a production environment (a company's LAN), so maybe
we are missing some special security configurations that we are not used to
(some multicast packet filtering maybe?). Also, if I increase the waiting
time you can see in the code from 2 seconds to 10, 20, 30... it still
doesn't work.

I have a list of tests to perform tomorrow, if I can meet with 2 mates to
use the 3-machine configuration (server-lookup-client). I'll post here our
conclusions, if we reach some, but in the meanwhile if you have any idea of
the source of the problem, it may help us in tomorrow's test.

Regards,

-- 
*Sergio Aguilera*

Reply via email to