Andre_p
asked on
Web remote sesion
I have setted up a windows 2008 standard server with a TS web site for remote control over the internet.
I use DYNDNS for address resolution
If i log into the web site via my ocal web site everything works.
As soon as i go into the site via the internet i get into the server, log in to get to the point where you enter the IP and then get a error message telling me the remote server (one hosting the site) is not available for remote control.
I use 192.168.2.201 as the server IP
Can it be a router problem?
I use DYNDNS for address resolution
If i log into the web site via my ocal web site everything works.
As soon as i go into the site via the internet i get into the server, log in to get to the point where you enter the IP and then get a error message telling me the remote server (one hosting the site) is not available for remote control.
I use 192.168.2.201 as the server IP
Can it be a router problem?
ASKER
if i work on the internet i can log into my server , my router is setted up to forward the trafic, the problem comes in as soon as i am logged in to the server.
Under the remote tab you need to point it to a machine - i exspected the IP to be the problem but how do i fix it
Under the remote tab you need to point it to a machine - i exspected the IP to be the problem but how do i fix it
I'm not sure so you need to "Request Attention" to get some others that know more about it than I do.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you
If you are 'out on the internet' and not on your LAN, then '192.168.2.201' is a private non-routable IP address. You would have to set up your router to forward the appropriate packets from your public IP address.