This is my case. Factor (2), it's inside the correct folder, because before port-switch, my work on WP is done within a LAN, it was accessible without problem via http://localhost/wordpress. Factor (3), I guess this is not happening... otherwise, I won't be able to access apanel, meanwhile wordpress is just a word '/wordpress' to add into URL.. ... I believe factor (1) is causing all the trouble! Last night I tested again the server with port 80 (in LAN environment), everything went ok! Even WP is accessible... ... ok, let's see... A redirect or blocking is in place... which could it be? I have examined 2 channels: Internet, domain by NO-IP http://mydomain.no-ip.info:81/wordpress [failed] LAN http://serverIP:81/wordpress [failed] Localhost http://localhost:81/wordpress [failed] Looks like the redirect or blocking is happening at the server itself, right? Correct me if I'm wrong, I'm googling for redirect/block in Windows Server 2003 R2 now... Thanks!