Windows 2000 professional terminal services

INF instead of just the client files. This would make it much easier for users. Since my service still will not start I cannot. I can conf the settings with tscc. In some instances netmeeting breaks video stuff in applications. For instance in premire when you hit play on a clip or what you are trying to edit, the picture doesnt move. You can see what it does to windows when you enable it sometimes. It even blacks out and reclicks the screen often. To me this aint the best sign.

XP Pro is not certified at my workplace yet. That's not what the subject of this thread is about. I can start the program, but it locks right up, can't do anything with it. It see the "server" and shows that I am logged on at the console. I tried the NT switch trick, still refuses connections though.

The service is definitely started though and there are no errors logged in the event viewer. I have 'em both networked to my host 2K server so it's very easy to pass files back and forth and using the disk "undo" feature of VPC I do not have to reinstall my guest OS'S. Service is still "Starting". Oh really? Just how is W2K 'more' of a workplace OS? Here's my current file copy list until I can figure out why tsoc.

SYS tdasync. It would require hours of my time to evidence my opinion. Time which I do not have. Suffice it to say that I "Think it. Therefore it is. But I ain't buyin' it and I don't think you should purport misinformation like as fact when it is simply your unsubstantiated opinion, which, if you couldn't tell, I strongly disagree with.

Me and you, buddy--empty thread. How so? Service is still started, however, when I try to connect to it it still complains that the server isn't responding. Also, just for the hell of it, I used NT switch on that server install and changed it to pro Also, all the admin tools work, like remote control and the like.

I will post more if I can get it to work. I have looked at everything you posted thus far and I really don't see a difference as to what I have done and what you have done I don't know. One thing I noticed on mine,the original Pro install that still isn't working, is that the rdpwd device under device manager is set to start on demand and doesn't start.

What "hacked up Windows Pro" are you referring to? TS most likely looks at the product type Posted: Sat Jan 04, pm. Posted: Sun Jan 05, am. It's easy to join and it's free. Register now while it's still free! Already a member? Close this window and log in. Join Us Close. Join Tek-Tips Forums! Join Us! By joining you are opting in to receive e-mail.

Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here. My Archive. Close Box. Log In Come Join Us! Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden. Setup a Client-Server network Domain as you do.

Introduction to Terminal Services: Terminal Services enables multi-user access to Windows , allowing several people to run sessions from a single computer simultaneously. Administrators can install Windows-based applications on a Terminal server and make these applications available to all clients who connect to the server.

Although users may have different hardware and operating systems, the Terminal session that opens on the client desktop looks and runs the same on each device. On your Terminal Services Server, there is an icon labeled "Terminal Services Client Creator" which creates disks that are used to install the Terminal Services Client program on the computer you plan to use to remote administer the server.

You must install this client program on each computer you plan on using to remote administer the server. Double click on the "Terminal Services Client Creator" icon. You will see the following screen. You must choose which version of windows bit or bit the client disks should support. As a gross simplification, windows 3. The 16 bit version of the Terminal Services Client requires 4 disks while the 32 bit version of TS Client requires only 2 disks.

Choose which version of the client you require and follow the directions. After you are done making the Terminal Services Client disks, you can now install the Terminal Services Client on any computer you will use to remotely administer your server.

If you are using a LAN computer to access Terminal Services on your server, then you do not need to do anything with your router. However, if you are planning on accessing Terminal Services from a computer across the Internet, you will need to forward port to your server. This is very important since Terminal Services listens on port Install Terminal Services Client. Let's install the Terminal Services Client on a computer that you will use to remote administer your server.

Insert the first Terminal Services Client floppy disk into your disk drive and click setup. After this you are ready to connect using Terminal Services Client. Once you connect to you server through Terminal Services, you have full control over the server. However, the desktop you see is not exactly the one that is open on the server itself.

The Terminal Services logs in separately, so technically, it is a different session. However, everything you do in the Terminal Services session will be executed on the server. Once you are done working with terminal services, how do you get out?

You'll see four options. Download Terminal Services Client. If you do not have a Windows Server machine, you can download the two disks from here. Overview Looking for a way to remote control your Windows Server without actually sitting in front of it?