Windows 2012 RDWeb RDP port

That onky changes the port thatbthe client attempts to connect tom it does not change then port that the broker and session hosts listen on. They are likely still listening on 3389.

With thatbsaid, changing ports isn't a good idea. The most often cited reason people are trying to is security, but internally that isn't more secure, and externally, rdgateway should be handling the hardening duties. I've never seen a good justified reason to change ports. In the modern server era.

this is a simple one but i have to ask, are you also specifying to connect on port 82 from the client?

Are you sure port 82 was open and not in use?
Run and post output

netstat -anb > out.txt

Select allOpen in new window

We only have one public IP, port 3389 is already in use and being Nat'd for another purpose.  This has worked and worked well on our current 2008r2 RDS box.

Can it not be done on WIndows 2012?

On the current server port might not have been in use, please post output of command

It can,  but it sounds like you are confusing what that PowerShell command does.  It just edits what properties are included in to files published to a collection (thus "custom rdp property.")  It does NOT change what prots servers listen on.

And I stand by what I said earlier you wouldn't want 3388 open *at all* (not even in 2008 R2) or NATd. You want to set up Rdgateway (which was also available in 2008 R2) when accessing from the outside. NATing REP just isn't a good idea.

Issue was self corrected.