Page 1 of 1

xx.subsonic.org is registered, but could not connect to it.

PostPosted: Sun Dec 30, 2012 10:12 pm
by chrisvor
Hello,
I just donated to the Subsonic team and also purchased the full version if iSub for the iPad/iPhone.
I installed Subsonic and when I registered my xxx.subsonic.org address, it returned "...subsonic.org is registered, but could not connect to it. (ConnectTimeoutException) "

I know this has been asked many times, and equally many times the answer was "there is something wrong with the port forwarding"

I am a computer technician and my router is properly configured to forward the correct port to the correct PC on the LAN. I can verify this also, because I have a firewall on the PC and when I delete any previous firewall rules, as soon as I hit the "save" on the page, an INCOMING request comes in from the subsonic server (IP starts with 66.49), so the port is being correctly forwarded from the router to my PC.

However, the subsonic service does NOT respond back. I checked also with http://canyouseeme.org/, which also fails to get back a response.

Can anybody help me out on this one? I am a computer professional and I can handle any technical guidance you can give me.

Many thanks for your support.
Best regards,
Chris

Re: xx.subsonic.org is registered, but could not connect to

PostPosted: Sun Dec 30, 2012 10:15 pm
by chrisvor
The only thing my mind goes to, is because the PC IP address is 192.168.1.2, and my public address is something different of course, maybe the service binds itself to the local address, and since in the incoming packet request the IP specified is the public one, it thinks it's not meant for it and does not respond?
Is there such a probability?

Best regards,
Chris

Re: xx.subsonic.org is registered, but could not connect to

PostPosted: Sun Dec 30, 2012 10:34 pm
by chrisvor
JUST SOLVED IT myself ! *VERY HAPPY SMILEY FACE*

The problem was in the WINDOWS FIREWALL !!!

Even though I have another firewall (ESET), the *WINDOWS* firewall was not allowing the incoming connection.

I manually created two new rules, one for TCP and one for UDP for the *PORT* that I am using (not the application/service name), and it now works !!

I am posting this in case somebody else has the same issue.

Best regards,
Chris