First of all, I want to say that I have read all the threads in the forum regarding this issue.
Here, what I want to ask for is VSL help to figure out what ACTUALLY causes this problem (routing, DNS, IP management, passthrough technologies, etc.).
My previous scenario was: Host Computer and Slave Server both connected to a switch; the switch connected to the router to have internet access on both the computers; all the IP addresses statically set; both the computer could access the web; the 16 VE Pro plugins inside Nuendo connected to their instance in fractions of seconds (the instances with just Vienna Instruments ALL connected SIMULTANEOUSLY, so that I could not tell which one connected before the others!). The whole template in Nuendo loaded in not more than 20 seconds (16 instances with 200+ audio channels from VE Pro back to Nuendo's mixer).
In the new configuration the only thing that changed is the router (I moved to a new apartment and I had to apply for a new contract with TimeWarnerCable and they offered me a new model). The new scenario is the same as before, except that the switch is now connected to the new router.
And here comes the problem.
EACH plugin connects to its own instance in 3 to 10 seconds, bringing the total loading time of the whole template to 2-3 minutes.
For your information, most of the instances have the DECOUPLE ON, so it should take no time at all to connect, as they are not sending any data to the instances.
I feel there is a network routing issue, based on the model of the modem/router: it is like each plugin is "looking around" to find its own instance, which doesn't make any sense to me, especially considering that I have static IP on the whole network.
I wish VSL could dig into this problem and tell us how to solve it.
What I can tell is that I used to work connected to the web without any problem, having all the plugins connecting to their own instances almost simultaneously.
I know several people affected by the same issue.
Thanks.