On the first screen shot:
The camera name does not need to be the IP address, it can be anything you want it to be. So for example, it could be something meaningful like BirdCamera but certain characters (usually symbols and spaces) may not be permitted.
From a browser, the URL only needs to be the dynamic IPaddress:Port number, the rest is unnecessary and may be what's causing the problem.
The URL you are using could be the extra bits that have to be entered into a media player when viewing the camera stream locally in order to identify the stream you want to watch. For example some HD cameras use two or more streams, the question then is how do you tell the media player which stream you want to view? a common method is to type http://{local ip address:port number/videoMain or videoSub) note the deliberate use of uppercase M and S, it is case sensitive.
With reference to the second screenshot:
It's not critical but I would use a static IP address (below 192.168.1.64) rather than a reserved DHCP pool address.
The Third Screenshot.
Not much wrong there but I would suggest you change the protocol to TCP/UDP.
The final thing to check is that your hub is set to use DDNS, that your account login and password are stored and that the public IP address visible in your DDNS account is the same as your current public IP (in other words make sure the hub is updating your DDNS service)
