I've had a network setup at my home now that has worked (for the most part) for the last two years. Basically, I have a desktop machine, which is where all my files are stored, and I can access it remotely from any computer connected over the network, either wired or wirelessly. The desktop is connected to my RTA1025W by ethernet cable, all other machines connect to it via wireless.

I've had port forwarding setup, allowing me to connect to the desktop remotely via TightVNC, thereby allowing me to control it from elsewhere. To do this, I assigned each machine on the network an internal IP address, and the port forwarding has worked fine. Only issue is when the laptops are taken elsewhere, they have issues connecting wirelessly, as they are always trying to get the LAN specified in the network settings in Windows.

I mentioned this issue to a colleague last week, who suggested instead of modifying the network settings on each machine, I set it up so that the MAC address is assigned the internal IP instead. I did this and bingo, it all works really well.

Only issue is tonight, when I try to connect to my desktop using TightVNC as I have done previously (and has been fine for over two years) now it refuses to connect. Apart from entering in the IP address/MAC address for each machine on my network, I didn't change any port forwarding rules. I deleted them and left the space empty, but that didn't work either. I'm sure it has to do with specifying the internal IP in the router instead of on the machine, but is there some way I can set up the router to allow a connection remotely using TightVNC?

Sorry for the novel, it's a pretty complex situation and I thought I should explain it all. If I've missed anything out or something doesn't make sense please say so.

Any assistance gratefully accepted.