Terminal Services.......WOW it works!!!

[PaulSM]

Ok, I got Terminal Services Client to work on my home network. But i was wondering if someone can provide me a step by step procedure on how to get it to work from outside my home network. Say at school and I want to access my home computer.

Any help will be appreciated. Please remember, I don't know too much about networking so please explain in laymen's terms. thanks.

You'll need these:
1. Static IP
2. VPN capable router (Ex. Netgear FVS318)
3. Faster upstream

[tallshorty]

You'll need these:
1. Static IP
2. VPN capable router (Ex. Netgear FVS318)
3. Faster upstream

Alrite where do we start?

1. How do I get a static IP? Will it interfere with my current internet connection?
2. I have a USR Wireless Router 8054
3. Upload speed is 512 Kbps. Is that adequate?

[PaulSM]

Alrite where do we start?

1. How do I get a static IP? Will it interfere with my current internet connection?
- You'll need to contact your ISP. Nope.
2. I have a USR Wireless Router 8054
- If you don't care about security, you can still use your USR just open the right port or use DMZ.
3. Upload speed is 512 Kbps. Is that adequate?
- It's plenty.

[Liderc]

Actually, you don't need a static IP from your ISP; though, it does help. If you use a broadband service, you computer has a Dynamic IP address. However, the lease on this address is decently long (a week for most ISP's) and the lease will renew again when it get close to expiring. So, your outside IP (outside your personal network) will stay static longer than you think. So, what you want to do is go to DynDNS.org and register for an account. What you can do here is register your ISP issued IP (which can be found if you go to whatismyip.com, I believe), and have dyndns.org issue a static domain address which maps to your ISP IP. And this account can be configured to automatically update. So if your ISP IP does change, DynDNS will update it's info as well so the same domain address is still pointing to your ISP issued IP. Hope this helps. :approve:

Thanks, this really helps.

[Koldun]

Thanks, this really helps.

Yeah thanks for this! Just tried it here at work, and it works perfectly! Muchos Respectos! :approve:

[wstam]

You can set up Dynamic DNS. It can set up a public name address (e.g. xyz.no-ip.org) and redirect the IP address to your home network. It involves two parts to work.

First, you need a Dynamic DNS service provider. There are many free DDNS server. DynDNS.org is very popular but I am using www.no-ip.com.

Second, you have to set up your router to update the DDNS server when your IP address change. Most the recent router support Dynamic DNS. Just search your router Advance Set up for the Dynamic DNS option. My D-Link router allows me to enter any DDNS service provider. I saw some Linksys router only have 2 to 3 pre-set DDNS service provider and you are forced to use them. You better to check your router before you choose the DDNS server.

If your router does not support DDNS, you will have to run the DDNS program, provided by the service provider, in your computer. The program will check your public IP very 5 to 15 minutes and update the DDNS server.

I am using ADSL that change the IP quite often and the DDNS work perfectly.

Good luck.

Actually, you don't need a static IP from your ISP; though, it does help. If you use a broadband service, you computer has a Dynamic IP address. However, the lease on this address is decently long (a week for most ISP's) and the lease will renew again when it get close to expiring. So, your outside IP (outside your personal network) will stay static longer than you think. So, what you want to do is go to DynDNS.org and register for an account. What you can do here is register your ISP issued IP (which can be found if you go to whatismyip.com, I believe), and have dyndns.org issue a static domain address which maps to your ISP IP. And this account can be configured to automatically update. So if your ISP IP does change, DynDNS will update it's info as well so the same domain address is still pointing to your ISP issued IP. Hope this helps. :approve:

[coach_ng]

is it possible to set this up on a win2k system?

Im really not sure if it'll work with Win2k. If 2000 doesn't have remote assistance then I don't think it's possible. Wait...wait.....check this out, it might give you some answers.>>>http://www.aximsite.com/boards/showt...minal+services :approve:

[Li0rE]

Yea, I actually just connect to one of my computers and do full screen firefox browsing. This gives you LAN speeds and a firefox tabbed browser.

[Li0rE]

and, by the way, it doesnt work with different ports. So if you use your router to redirect ports, lets say to 8000, and try blah.com:8000 it will say invalid. So you can only do Blah.com or IP which goes to default 3389.

[ToddAB]

There is an online service at www.logmein.com

It works pretty good and is free if you don't want to transfer files or print that it seemed very easy to set up.

Maybe an easier solution!

[elliso92]

I'm just starting out using terminal services myself. The problem I'm having is when I try to use it to log onto my home machine while on my home network, I get an error saying I can't log on because of "account restrictions". What is this referring to?

[BigBHaller]

You'll need these:
1. Static IP
2. VPN capable router (Ex. Netgear FVS318)
3. Faster upstream

As it was stated before, static IP is not necessary, but would be easier to remember if you did. A dynamic DNS solution is also good.

A VPN capable router is not necessary. A Virtual Private Network is an entirely different animal. You only need a router that allows port forwarding. Simply set port forwarding for 3389 to your internal computers IP.

While your experience will be much more enjoyable with broadband, it is entirely possible to use at GPRS speeds. The reason RDP is much faster and lighter than remote control software such as VNC, is because RDP draws the interface locally at the client, whereas VNC has to send the entire screen image of whatever is at the host to the client. RDP and remote control are different. To understand the difference, it is best to look at the server implementation of RDP.

In Terminal Services/RDP in 200x Servers, multiple people can connect to terminal sessions simultaneously and work in their own seperate windows environment. Each session is seperate, as if each were working on different computers. None of them can see what each are doing (it can be possible for admins to see, but we'll leave that out, as it can get confusing).

In a remote control environment, only one person can be signed on to a Windows session. Both remote and local user see the exact same thing and control the same mouse and keyboard inputs (it is also possible to lock out either remote or local session, but that's also more confusing so we'll leave that out).

RDP (remote desktop protocol) in Windows XP/2003 Server and Terminal Services in Windows 2000 Server use TCP port 3389. Only the Server version will have this capability in Windows 2000. All versions of XP and 2003 have RDP built in.

If you are denied access because of an account restriction, this generally means you have a blank password. Windows XP/2003, by default does not allow remote access to it if the user's password is blank. You can either change your password, or change the local security policy to allow user's with blank passwords.

So to summarize:

1) Enable remote desktop on your Windows XP/2003 Server computer or Terminal Services on your Windows 2000 Server.
2) Make sure you either have a password on your user account, or change the local security policy to allow blank passwords for remote access.
3) If your internal network (the one in your home) uses DHCP to assign IP addresses to your computers, it would be a good idea to set an address reservation for the MAC address of the computer. This way your computer won't change it's IP later (which will break the port forwarding below)
4) Set your router to forward TCP port 3389 to the internal IP of your host computer.
5) If you have DHCP assigned from your Internet Service Provider, it would also be a good idea to use a Dynamic DNS service to register a fully qualified domain name to your dynamic IP address.

[elliso92]

This is pretty neat, but what now? Can I transfer files with the remote system? Can I print something on the remote system?