SOLVED: DLNA connection and database problems

[bigfoot65]

I believe there has been a suggestion about that, but it's a distant project.

There are so many moving pieces and parts to a firewall. I will say it's not high on the priority list for Amahi at this point.

Most users don't have the issues you have experienced.

In my opinion, it's best to let the router handle firewall settings.

[AndyBel]

I had a Eureka moment earlier on the way home from work! I think I know what the problem is!!

Typing username.yourhda.com into an outside network browser didn't redirect me to the setup screen, it directed me to my CCTV system!!

I forgot I hard-IP'd it on it's own config page (due to the Belkin's inability to do that!) and it seemed to take control of the system! I suppose that's why the port forwarding worked - it was telling the radio how to get to the server, without that the radio may have been searching the CCTV and not finding anything!!

I've given it the same static IP on the server now, and changed it's config settings to use DHCP for it's IP address.

Now I need to figure out how to access it remotely via the yourhda.com DDNS system!

[bigfoot65]

We all often have those or the Duh ones LOL

The web UI for DLNA is on a different port than the DLNA server itself I believe. The internet says TCP for 8200 and UDP for 1900 to expose it to an external network.

That may help.

[AndyBel]

Mainly Duh moments for me!!

Sorry - just re-read my post and noticed I wasn't very clear! It's the CCTV box I'd like to be able to access externally either via it's apps or via a browser login. I've set it up with it's own DNS on Amahi so I can access it internally, pity I can't seem to figure out how to do it externally.

[bigfoot65]

Oh I see.

You should be able to port forward the IP address of the device providing it operates on a specific port.

Let's close this thread and start a new one if more is needed.

[AndyBel]

OK - we seem to have gone off on a tangent since the original query was solved!