Using Terminal Services without a public IP address on the server
This is a discussion about Using Terminal Services without a public IP address on the server in the Windows Networking category; I have a customer that requires remote support quite frequently. The problem is that this customer's site is located in an area on which there is only one ISP, and it only provides internet connection though a cable-modem without the possibility of having a public IP address.
I have a customer that requires remote support quite frequently. The problem is that this customer's site is located in an area on which there is only one ISP, and it only provides internet connection though a cable-modem without the possibility of having a public IP address.
I would like to use Terminal Services on Windows 2003 server, but I can't make this work without a public IP address on the server side. So far all I've found are applications that give me remote control functionality, like Windows Messenger and LogMeIn, which don't give me all the functionality of Terminal Services.
So the question is, does anyone know how I can make Terminal Services work without a public IP address on the server side? Or is there a 3rd party software that can emulate terminals thought the internet without a public IP address on the server side?
I would like to use Terminal Services on Windows 2003 server, but I can't make this work without a public IP address on the server side. So far all I've found are applications that give me remote control functionality, like Windows Messenger and LogMeIn, which don't give me all the functionality of Terminal Services.
So the question is, does anyone know how I can make Terminal Services work without a public IP address on the server side? Or is there a 3rd party software that can emulate terminals thought the internet without a public IP address on the server side?
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
