Thank you for the information, musicllum. I really appreciate it.
I loaded up Wireshark to look at what happens between my system and the VST connect server when I make a connect request. I created packet captures for both a successful connect and one that gets the “Server Not Responding” error. Summary:
1 - If it’s the first connect attempt after a reboot, a name server lookup is made for vstconnect.steinberg.net.
2 - My computer makes a request to the IP address of the vstconnect server (port 51111) with the value entered for “Name” in the payload (a 234-byte UDP packet).
3 - The vstconnect server responds with the assigned project number in the payload (another 234-byte UDP packet).
Given that what looks to be a valid project number is returned whether or not the error comes up, I can only conclude that this problem is with the VST Connect code. The vstconnect server appears to work as it should in all cases.
One other note, I can SOMETIMES successfully get a project number with this project. There is no pattern to it that I have figured out yet. If I close it, close Nuendo and reopen, it typically gets the error again.
I am happy to pass along the packet traces if that helps, but I believe our problem lies in the VST Connect and related code. Please let me know.
Thanks, again, for the help.