Torrents; NAT on DHCP problem

[naith_kk]

Forgive me if a solution to this was around the forum... I tried searching but to no avail. I'm not that knowledgeable in router configurations and networking so please bear with me on my questions.

I have a TP-Link TD-W8951ND ADSL router. I have a desktop computer connected to the router by cable and the rest of my devices that access the internet are through wireless and through DHCP. I've set NAT and UPnP enabled on the router settings.

My Desktop IP is static because I host a local web server for work purposes. My wireless devices are handled by DHCP.

My problem is, my wireless devices that have their IP's managed by DHCP are not working well with torrent clients. Particularly they seem to have NAT issues and I get warned that my IP needs to be static and my ports need to be forwarded. None of these devices (including my desktop) have been port forwarded on my router. The reason why I did not have my wireless devices use static IP and have ports forwarded is because I sometimes use these devices in a variety of locations other than my home wireless... its a hassle for me to manually configure each and every device I have to accomodate the different wireless routers that I'm accessing. The other locations where I access the internet seem to enable NAT on my devices and I am able to use my torrent applications - but sadly, I'm not able to do so on this TP-Link router...

The only device that has torrents working with no problems is my desktop (I'm guessing the obvious reason is because it has a static IP set up). I was hoping UPnP would assist me in automatically assigning and opening ports required by these applications for my wireless devices which are managed by DHCP but that isn't the case.

So my question is, with this router, how do I go about setting it up to solve the NAT issues that I'm facing with my DHCP managed devices?

[naith_kk]

I figured it out - Reverted back from multi IP NAT configuration to single IP NAT configuration... but the downside is losing my web server connectivity for some wierd reason.