Is there another solution out there?

Just do the port forwarding on the router. Forward port 12341 to internal
IP address 1.2.3.4 on port 80. Then setup another rule forwarding port
12342 to internal IP 1.2.3.5 on port 80. The router will do it. The
internal PCs will see the traffic as only coming into port 80. No need to
set up or change anything on the PCs.

It's very common for ISPs to block *incoming* traffic on certain ports.
Typically 80, 25 and some others. Usually with the purpose of blocking use
of residential connections for hosting servers. Most ISPs require using a
'business' account for that sort of thing. It's usually an option available
at a residential location, but at a greatly inflated price. Blocking the
incoming traffic will have no effect whatsoever on *outgoing* traffic on the
same ports. TCP connections don't use the same inbound port as the outbound
request.

-Bill Kearney

I the camera send the info via port 80 it is blocked by the ISP and does
not reach to you, so there is nothing that you can do on side to get in
something that is Not existing.

What?

If what you're trying to say is if the ISP blocks a port there's nothing you
can do to use it, yes that's correct.

Most DNS services provides port redirect (no-ip.com is an example).

Not usually as part of their free services, however. You pay extra for it.

I.e any signal that comes to their server from the outside ion port 80 can
be redirected redirect to port 1234 (as an example) before it reaches the
WAN side of the Router

Don't know how well redirection like this works for streaming connections
from things like webcams.

All you have to do is portfoward in the Router port 1234 toward the IP of
the computer that follows up the camera.

If he can live with knowing to use the port himself there's no need to use a
redirection service.

This should not effect your regular surfing since regular port 80 action
does not go to your DNS service.

It's a bit misleading to equate web port redirection with DNS services.
They're not the same thing. Port redirection does depend upon a DNS lookup
having taken place, this is true. But port redirection itself is not a
function of DNS.

-Bill

I the camera send the info via port 80 it is blocked by the ISP and does
not reach to you, so there is nothing that you can do on side to get in
something that is Not existing.

What?

If what you're trying to say is if the ISP blocks a port there's nothing you
can do to use it, yes that's correct.

Most DNS services provides port redirect (no-ip.com is an example).

Not usually as part of their free services, however. You pay extra for it.

I.e any signal that comes to their server from the outside ion port 80 can
be redirected redirect to port 1234 (as an example) before it reaches the
WAN side of the Router

Don't know how well redirection like this works for streaming connections
from things like webcams.

All you have to do is portfoward in the Router port 1234 toward the IP of
the computer that follows up the camera.

If he can live with knowing to use the port himself there's no need to use a
redirection service.

This should not effect your regular surfing since regular port 80 action
does not go to your DNS service.

It's a bit misleading to equate web port redirection with DNS services.
They're not the same thing. Port redirection does depend upon a DNS lookup
having taken place, this is true. But port redirection itself is not a
function of DNS.

-Bill