Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: New Amazon Echo Support
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
are you sure that you're 8080?

run 'netstat -ano | find "8080"' in a command prompt. it will spit out what is running that port, including the PID on the far right.

then run 'tasklist | find "pid from above"' to see what EXE is holding that port.

for CQC, it will be CQCWebSrv.exe

to verify that the port is forwarded correctly, just try to telnet to it from outside your network - telnet ip.address port (telnet 8080)
I got it as far as giving me the pid, but I can't get it to recognize tasklist.
the command tasklist isn't on your system? it's on all of mine, Win7, Win8.1, Win10.

tasklist | find "PID"

regardless, if that isn't working, try to telnet to your public IP and the port (8080). i don't know if it will work inside your network without a U-turn configured, but it can't hurt to try.

telnet your-public-ip port
Got it. It's CQCWebSrv.exe
I could do it on my iPhone on Verizon which wouldn't be on my network.

I need to know exactly what to type in the address line. Remember, your grandmother knows more than I do about this.
Actually the -o on netstat causes it to show the process that owns the port, so there's no need to do the task list thing. Just search the output for 8080 and see what shows up as having opened that the port.

So do something like:

Netstat -aon > nstat.txt
notepad nstat.txt

then just search for 8080.
In terms of testing the port forward, you can just create a sample html file, say:


And then open a web browser and accessit as:


If you can open that file, then you are ok on the port forward.
not -o or -ano shows the service name. as far as i know, you have to grab the PID and match it, but i don't know all of the switches for netstat.
I assume there is a proper way to make an html file that I don't know about?
The CQC servers are just standard programs, running under a service that manages them, so it'll show their regular process names. Since there are no multiple instances of them, that's sufficient.