I dont know if this is the right forum to ask this question but I dont know any other where I can get the solution from. Any help will be appreciated. I have setup remote desktop on the laptop and have configured the router to forward connections on port 3389 and got my IP from ISP. Now when I try to search for my IP I always get the error that my IP can not be found. Please help.

Most ISPs assign a DHCP IP address to users with residential accounts. So if that is the case its possible your public IP, as assigned by your ISP, has changed either because the lease expired and was renewed with a new IP or your modem rebooted or other reasons.One solution to that is to use a free service like No-IP.com or DynDNS to get a fully qualified domain name [FQDN]. Then you call using the FQDN. The way it works is you download and install a small program that communicates with the No-IP.com or DynDNS servers on a time scheduled basis. The servers then know what your current IP is and map to your FQDN. That information is propagated over the public internet. You call using the FQDN. Note that some consumer grade routers have that functionality built in, ie. ability to communicate with the No-IP.com or DynDNS servers. Check your users manual for help.Also note that calling the Remote Desktop [RDC] host computer from another computer on your LAN using the public IP of the router or the FQDN may fail. Many consumer grade routers do not support this loopback addressing.http://theillustratednetwork.mvps.org/RemoteDesktop/TroubleshootingDiagrams/Basic.html Additionally if your trying to use a older RDC client, ie. on a XP computer for example, to connect to a Windows 7 machine then you may still have the browse for terminal servers, I think that was what it was called, still available. Note that without doing a registry hack you will not be able to browse in a workgroup environment. That only works in a domain environment. Most home users are in a workgroup environment.http://support.microsoft.com/default.aspx?scid=kb;en-us;281307If your on a XP RDC client I also suggest upgrading to the new RDC 7 client.http://support.microsoft.com/default.aspx/kb/969084 MS-MVP Windows Desktop Experience, "When all else fails, read the instructions"

I tried to gain remote access immediately after configuring my router. So there is no question of IP address changing as I didnt reset the router. I even checked the IP address after the attempt and found it to be the same. I am using a Win Vista machine to connect to a Win 7 machine. And both are not on the same network.

Hi Ayush,Can you use command prompt to ping the "address" from Vista ?

I tried to gain remote access immediately after configuring my router. So there is no question of IP address changing as I didnt reset the router. I even checked the IP address after the attempt and found it to be the same.I am using a Win Vista machine to connect to a Win 7 machine. And both are not on the same network. If you go to the http://www.canyouseeme.org site on the Windows 7 RDC host does the test pass for TCP Port 3389? If not either port forwarding on the router is not configure right or your ISP is blocking TCP Port 3389 (generally unlikely).Can you successfully login to the Windows 7 RDC host from another computer on the same LAN using the local LAN IP of the RDC host?This all presumes the network location type on the Windows 7 RDC host computer is set to Home and NOT Public. You can also go to Start > Run on the RDC host and type cmd /k netstat -a and see if the computer is listening on TCP Port 3389. MS-MVP Windows Desktop Experience, "When all else fails, read the instructions"