Networks

Ask something
Question Locked

Microsoft Terminal Services Solution

0 helpful
3 replies

by stergios_nik

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello.

I have a Microsoft Access database (109MB) in building "A" and the remote user in building "B" opens the database extrememly slowly over the WAN (Wide Area Network) connection. It takes 1 hour to open the database.

I thought that I could use Microsoft Terminal Services technology in order to resolve this problem.

The need we have is that only one user for the time being from building "B" wants to open the Microsoft Access 2003 database that is stored on the server in building "A".

I would like to ask for the hardware and software requirements in order to install the terminal service solution on the server in building "A" so that I can allow the remote user in building "B" to access the database.

The existing server in building "A" where the database is stored has the following specifications
Server: HP ML350, Intel Xeon CPU (2 x 1.60Ghz), Ram (2GB)
Software: Windows Server 2003 (acting as Domain Controller and file server for the Access database .mdb file)

Could you tell me if the above server is adequate for handling the load of the Terminal Services Solution?

Also, having in mind the implementation procedure could you tell me if the terminal services will cause any problems to the Domain Controller's operation?

Thank you in advance.

Stergios

3 replies

by bfilmfan

You are going to be resource constrained with only 2 GB on a global catalog that is also offering Terminal Server Services, serving up an app and acting as a file and print point.

You didn't mention the number of users involved, so if it is less than 25 users TOTAL, then you should increase the RAM to a minimum of 4 GB.

If it is MORE than 25 users, you may need to split off the file, print and Terminal services onto another system to prevent issues.

by cg it

buying new hardware thinking it's a server hardware problem. The HP ML350 is a decent server even with 2GB of memory.

One user accessing a db for the WAN isn't going to cause the server to take 1 hour to open the db even if you have 10 or 15 other people accessing the db on the network.

It's possible that the front end application your using might be causing the problem in which case Terminal Services isn't going to solve that kind of problem either.

What application are you using as the front end? Access itself?

This discussion is closed to new replies.