There is currently a static route on the WAN port pointing at the 159 part of the network. I can ping that side from the router
On the VLAN ports 1-3 i can ping the computer and from the computer i can ping the vlan and wan ports
I just cannot ping the 159 address from the computer
It's an interesting diagram. You have differing subnets connected together using a static to direct traffic via a physical interface. Why can't you have an IP address on the router in the same subnet as the server? What is the gateway address the server is using? To get to your PC, the server would need to have a gateway that knows how to get to your 172 network.
Might I be so bold as to suggest you change the WAn interface IP to 18.104.22.168 with a mask of 255.255.255.0 and get rid of the 192.168.20.4 (this all assumes that there is nothing else on the network that may be impacted by this change). You would no loger require the static route in your config then. Then configure your server to have the 22.214.171.124 address as its default gateway.
If this isn't possible due to other devices etc, then pick any other IP address in the 159 range thats free and put that on the WAN interface of your router and use that as the default gateway.
If a default gateway is in use on the 159 network already, then you will need to configure a static route on that gateway device to point at your routers WAN IP address for your 172 network.
Hope this isn't to confusing.