There a likely multiple DNS lookups made during the whole handshaking process to get things rolling. I suppose if any of those requests couldn't connect for whatever reason, the process hangs. This setup happens dynamically as the request is made. Assume the specific endpoints are located in different parts of the world as determined by the provider that Bandlab is using, and that are assigned as geographically closest to you. the Bandlab client attempts connections with multiple endpoints involving the content delivery network that serves your download content. it phones home base and signs you in (so we know that part works). Using a network monitor, I noticed that Bandlab Assistant makes multiple connections to when it is working on a download. Like getting a wrong phone number, or a number out of service. If the DNS server either isn't up to date, or is blocking something, I think the process could possibly stall without an obvious error message as to the cause. Each DNS lookup has to go out to your ISP DNS server and obtain the actual IP addresses for the server to connect to. But for connected installs, there are often many DNS (Domain name Server) lookups made by an installer client to completely establish a session with a content provider cloud. If it was the firewall blocking, the assistant would not connect to anything and you couldn't sign in to it. I gotcha, but I was thinking further out, beyond the firewall. I don't know, but I added BandLab Assistant as an allowed program in the Windows firewall. Anderton abacab I wonder if it is a networking or DNS server lookup issue with the assistant? The joys of online installers.
0 kommentar(er)
