Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: How to diagnose setup issue of unable to contact master server?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
I have run into this many times on a number of clients and its always really annoying. Sometimes I can get past it just with retrying, other times I can't. Is there any log generated by the setup that will show me what errors or problems are happening when Setup is trying to contact the master server?

The latest one is with my 3500. I can ping the machine (cqcsrv) just fine with either just the name or the fqdn for it. But CQC will not pass the test of talking to the server. How can I get this working reliably? I like a whole lot of what CQC allows me to do, but adding in new client machines just seems to be way too painful.
Are you sure you are typing it correctly? The only time I have seen problems was..
1. Network not typed in the same
2. Firewall

if these are correct then maybe someone will know the answer.. It shouldn't be a problem.
nope, definitely typed correctly Smile

I set it up from another machine as well, same steps, same server name. That one worked fine. But one machine just isn't working. Any special gotchas with a Win2k machine vs XP for the client?

Is there any logging of what setup is trying to do? And of what fails?
Sendero Wrote:nope, definitely typed correctly Smile

I set it up from another machine as well, same steps, same server name. That one worked fine. But one machine just isn't working. Any special gotchas with a Win2k machine vs XP for the client?

Is there any logging of what setup is trying to do? And of what fails?
try opening up a cqc coomand prompt window, then running cqcnettest. its a program designed to help debug.
btw, you've started the cqc service on these boxes (assuming you didn't install in standalone viewer mode), right?
If the installer cannot connect, there aren't a lot of possibilities. The most common one is that you have incorrectly set up the DNS, so that the local machine is showing up with a domain suffix, despite the fact that it is in a workgroup, i.e. the name is really Bubba, but it's showing up as Bubba.whatever.com. If you do 'ipconfig /all', do any of the network connections show up with a domain suffix?
IVB Wrote:try opening up a cqc coomand prompt window, then running cqcnettest. its a program designed to help debug.
btw, you've started the cqc service on these boxes (assuming you didn't install in standalone viewer mode), right?

How can I do this if CQC is not installed?
Dean Roddey Wrote:If the installer cannot connect, there aren't a lot of possibilities. The most common one is that you have incorrectly set up the DNS, so that the local machine is showing up with a domain suffix, despite the fact that it is in a workgroup, i.e. the name is really Bubba, but it's showing up as Bubba.whatever.com. If you do 'ipconfig /all', do any of the network connections show up with a domain suffix?

All machines are in a domain. DNS works fine from all machines. There is no domain suffix appended on the ipconfig settings. From a command prompt pings to both cqcsrv and cqcsrv.mydomain.com resolve correctly and can ping the server.
If you are in a domain, then there actually should be a domain suffix on the network connections.

Are you absolutely sure you don't have two machines on the same IP address?

Also, look in the temp directory (wherever the TEMP environment variable is pointing) and there should be a CQCInstall log file there.
Interestingly, repeating the setup on the machine that can talk to the server now runs into the error during setup.

1 - Using the currently installed CQC IV, things work fine.
2 - Start CQC setup, when prompted, enter in same master server name

Result - Get an error that the server cannot be contacted.

3 - Cancel setup, restart CQC App shell service
4 - Launch IV

Result - works fine

How can the IV work fine but setup doesn't? I'm happy to help dig into the problem here because it sure looks like a bug or at least an area to improve the product. Let me know what diagnostics I can do because this is incredibly annoying Smile
Given that no one else is having this problem (that I know of), I'm not so sure it's an error in the installer. Check the install log and see what it's saying.

Do yo have multiple network cards in these machines?
Pages: 1 2