Terminal Service & Dial up Problem

[jandk4014]

First I would like to say that this is a great site. I've been looking all over the internet for a site like this!!!

I currently working on a Windows 2000 Advanced Server and experimenting with Terminal Services (TS). I configured TS properly because other computers that are on the same router can see the server and are responding just fine. But I only have dial-up (56k) at home and when I try to log on I receive an error message stating:

"Remote connections might not be enabled ...."

Where exactly do I set this parameter to enable remote off campus access? Is this a useless idea (TS) when it comes to dial-up? I don't even get to enter the username or password. I've also tried using remote desktop connection and I got the same problem.

 

[AndsA]

For this type of connection you do not use Terminal Services. You use the Remote Access service. Do a search on this service on the web and you will get the lowdown.

Ands

 

[redwhip]

You can dial directly to a terminal server running RAS and create a thin client session to it.
You can also use it across the internet using packet redirections or static NAT on your router.

If you have any firewall on your PC you will need to open it for terminal services.

Also check for licencing restrictions.
If you have the terminal server in remote admin mode then only one person can log in at a time.

 

[jandk4014]

Thanks for the reply. I'll do some research on RAS and thin client sessions. I've also be in talks with a collegue about this issue that he says that I'll have to open a port on the Linksys router to enable remote dial in. Is this true? Are there any good sites that discuss RAS and thin client applications?

Thanks again for the replys.