Re: Best way to diagnose issues?
From: Greg Lirette [MSFT] (gregoryl_at_online.microsoft.com)
Date: 06/29/04
- Next message: Jorge: "Disable shut down"
- Previous message: Javier Gomez [SBS MVP]: "Printing woes"
- In reply to: Douglas McIver: "Best way to diagnose issues?"
- Next in thread: Douglas McIver: "Re: Best way to diagnose issues?"
- Reply: Douglas McIver: "Re: Best way to diagnose issues?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 28 Jun 2004 22:37:26 -0500
Can you reproduce it on the LAN also? What operating system is this?
Windows 2000 or Windows 2003?
This posting is provided "AS IS" with no warranties, and confers no rights.
"Douglas McIver" <douglas@nospam.com> wrote in message
news:O6RPJWUXEHA.3988@tk2msftngp13.phx.gbl...
> Our terminal server is locking up quite a bit for the end users, sometimes
> it take fifteen seconds for the start menu to open up when logging on,
> sometimes it takes a couple of minutes for Word to open.
>
> We are running a Dual 3 GHz, 2GB Interleaved RAM, 2x 15K SCSI disks with
> Hardware Raid, Trend Server-Protect, MS Office 2003, Adobe Acrobat 6.
>
> Clients are Wyse thin clients, no port redirection, set on 28.8K settings.
> There are 15 client terminals in CA, TermServer is in Houston. There is a
> 1.5Mbps Frame Relay circuit between the two, and constant pinging shows a
> steady 40ms ping between them.
>
> Any ideas?
>
> Thanks,
> Douglas
>
>
- Next message: Jorge: "Disable shut down"
- Previous message: Javier Gomez [SBS MVP]: "Printing woes"
- In reply to: Douglas McIver: "Best way to diagnose issues?"
- Next in thread: Douglas McIver: "Re: Best way to diagnose issues?"
- Reply: Douglas McIver: "Re: Best way to diagnose issues?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
