Archived from groups: microsoft.public.windowsnt.terminalserver.applications (More info?)
We have a Windows 2003 Terminal Services application running on a new Dell
server with 4GB of RAM and twin Zeon processors. Users access this over a
WAN, the slowest connection of which is 256K. The application itself is a
Delphi EXE at about 7MB, opening around 120 database files with around 130
indexes. There is a 100 user Advantage database from Extended Systems, NT
service running which appears to operate well. The SQL Native utility in
the database operates at spectacular speed when we
need to access the database for alterations etc.
Unfortunately we have many incidences of clients hanging and having to be
reset. The application never hangs when running on a standalone machine or
a LAN. All clients are using Windows 2000 Professional, and access the
server via a greater hospital network cluster.
Any advice would be most welcome, as we are a loss to understand the nature
of the problem.
Peter
We have a Windows 2003 Terminal Services application running on a new Dell
server with 4GB of RAM and twin Zeon processors. Users access this over a
WAN, the slowest connection of which is 256K. The application itself is a
Delphi EXE at about 7MB, opening around 120 database files with around 130
indexes. There is a 100 user Advantage database from Extended Systems, NT
service running which appears to operate well. The SQL Native utility in
the database operates at spectacular speed when we
need to access the database for alterations etc.
Unfortunately we have many incidences of clients hanging and having to be
reset. The application never hangs when running on a standalone machine or
a LAN. All clients are using Windows 2000 Professional, and access the
server via a greater hospital network cluster.
Any advice would be most welcome, as we are a loss to understand the nature
of the problem.
Peter