Data is stored on the terminal server and local workstations also access this same data via a lan. any idea why the remote clients would be fast but the data access for the local workstation would be slow? Switch is 100mbs and so are all nics... 8 local workstations and 8 remote clients accessing via TS
In article <#eVca46cGHA.3908@TK2MSFTNGP04.phx.gbl>, anonymous@discussions.microsoft.com says... > Data is stored on the terminal server and local workstations also access > this same data via a lan. any idea why the remote clients would be fast but > the data access for the local workstation would be slow? Switch is 100mbs > and so are all nics... 8 local workstations and 8 remote clients accessing > via TS Bad DNS settings? -- spam999free@rrohio.com remove 999 in order to email me
Leythos wrote on 10 maj 2006 in microsoft.public.windowsnt.terminalserver.connectivity: > In article <#eVca46cGHA.3908@TK2MSFTNGP04.phx.gbl>, > anonymous@discussions.microsoft.com says... >> Data is stored on the terminal server and local workstations >> also access this same data via a lan. any idea why the remote >> clients would be fast but the data access for the local >> workstation would be slow? Switch is 100mbs and so are all >> nics... 8 local workstations and 8 remote clients accessing >> via TS > > Bad DNS settings? That's a possibility, but Jeff Pitsch has already answered a duplicate of this post in another TS newsgroup: the remote clients are using the TS as a TS, for which it is optimized. The local LAN users use the same server as a file server, for which it is *not* optimized. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___
