Archived from groups: microsoft.public.windowsnt.terminalserver.misc (More info?)
Hi all,
I Have a 2003 Terminal server that is part of a 2K domain. When ever a user
logs in and uses software that connects to SQL 2000 server in the domain the
performance is very bad. even over LAN.
When logging in from a normal LAN XP client, the network the performance of
the SQL based software is much faster. Because of this I dont think its a
problem with the SQL 2000 server but Mabye something that needs tweaking on
the TS2003 server.
In short does anyone know of some tweaks for 2003 Terminal server to get it
to work well with SQL 2000 server connections.
The server has a maximum of 4 people connected to it. it is running pretty
much desktop processor / motherboard (2.2 ghz / 333 FSB) with 1.5 GB RAM and
a S-ATA disk.
Regards,
Mike.
Hi all,
I Have a 2003 Terminal server that is part of a 2K domain. When ever a user
logs in and uses software that connects to SQL 2000 server in the domain the
performance is very bad. even over LAN.
When logging in from a normal LAN XP client, the network the performance of
the SQL based software is much faster. Because of this I dont think its a
problem with the SQL 2000 server but Mabye something that needs tweaking on
the TS2003 server.
In short does anyone know of some tweaks for 2003 Terminal server to get it
to work well with SQL 2000 server connections.
The server has a maximum of 4 people connected to it. it is running pretty
much desktop processor / motherboard (2.2 ghz / 333 FSB) with 1.5 GB RAM and
a S-ATA disk.
Regards,
Mike.