I'm confused what you are trying to achieve - the WAN port should be connected to your WAN connection i.e. something that connects to the internet.
Everything else should be on your LAN ports, or on switches connected to these.
If you are just testing something out, then you could give your server a static address on a subnet different to your internal one, then set a static ip address on your router in the same subnet as the server, e.g.:
Lets say your router's internal address is 192.168.0.1, subnet mask 255.255.255.0, this means your local subnet is 192.168.0.1-192.168.0.254 (as well as the reserved addresses 192.168.0.0 and 192.168.0.255).
You could then set your server with static ip 192.168.1.1 subnet mask 255.255.255.0 and your router's WAN interface to have static ip 192.168.1.2 subnet mask 255.255.255.0, then from your internal network you should be able to access 192.168.1.1 to get to your server.
The only real reason I can think to do so is if you have multiple WAN ip's and you wish to have your server on one of these so it can be accessed externally, but I would strongly advise you to have your server internal and set up relevant port forwarding instead.