Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows 2000 / Terminal Services / May 2005

Tip: Looking for answers? Try searching our database.

Installing Windows 2000 Terminal Services

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kesavan - 26 May 2005 06:39 GMT
Hi all,

I'm from a financial background so my queries might sound trivial but i need
some clarifications. The case is I have a machine in Singapore which i need
to access. Presently the system in Singapore runs on P4 1.7 ghz and 512 MB
RAM, Win2k client. I need to remotely access the system from Chennai. This is
done thro 1 mbps line and it is not dedicated line. Presently we are
accessing it through VNC. Also we run all oracle based applications.  

1. I guess we need to install Windows 2000 Server  to access the system.
2. We are presently facing a problem of VNC being very slow. If we use
Terminal services will it be faster. ok if u need how slow it is , enterning
a invoice in financials takes not less than 30 mins. so will it improve.
3. wht are all the changes we need to make if we need to install Terminal
Services to the system, network and other infrastructure

Thanks
Vera Noest [MVP] - 26 May 2005 21:44 GMT
You don't write if you have a need to access the machine in
Singapore with more than one user at a time.

If you have that need, then you will need a server Operating system
(Windows 2000 or 2003) and install Terminal Services. You will then
also need to install a Terminal Service Licensing Server (can run
on the same machine if it is a standalone server in a workgroup),
and you need to install Terminal Services Client Access Licenses on
the Licensing Server (depending on the OS on the server and the
clients).

If one connection at a time is enough for you, then you could
instead install Windows XP Pro on the machine, and access it with
the Remote Desktop Client software.

In both cases, you need to make sure that port 3389 is accessible,
probably by forwarding port 3389 on the firewall to the Terminal
Server / XP Pro machine.

If you decide to install a server OS, you will need more memory.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"=?Utf-8?B?S2VzYXZhbg==?=" <Kesavan@discussions.microsoft.com>
wrote on 26 maj 2005 in microsoft.public.win2000.termserv.clients:

> Hi all,
>
[quoted text clipped - 16 lines]
>
> Thanks
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.