Local disk access horribly slow

  • Thread starter Thread starter Freaky
  • Start date Start date
F

Freaky

Guest
Hey there,

we have several customers that can work flawlessly on our terminal
server. The applications on the terminal work very fast.

The customers also connect their local drivers, and this is where the
problems lie. Access to the local disk is extremely slow. Every time
they click a folder they have to wait around a minute for the directory
listing. Browsing through 10 folders deep therefore is not doable. Also
copying large files (larger than 10MB) from the local disk to the
terminal often fails.

The terminal connection itself is very stable. Also uploading (very)
large files from the workstation/customer PC to for example a webserver
with FTP gives no issues whatsoever.

Any ideas?

TIA
 
Re: Local disk access horribly slow

Just got the error from the customer. It was in dutch so I had to
translate it, but this seems to be the correct message:

"The I/O operation has been aborted because of either a thread exit or
an application request"

TIA

Freaky wrote:
> Hey there,
>
> we have several customers that can work flawlessly on our terminal
> server. The applications on the terminal work very fast.
>
> The customers also connect their local drivers, and this is where the
> problems lie. Access to the local disk is extremely slow. Every time
> they click a folder they have to wait around a minute for the directory
> listing. Browsing through 10 folders deep therefore is not doable. Also
> copying large files (larger than 10MB) from the local disk to the
> terminal often fails.
>
> The terminal connection itself is very stable. Also uploading (very)
> large files from the workstation/customer PC to for example a webserver
> with FTP gives no issues whatsoever.
>
> Any ideas?
>
> TIA
 
Re: Local disk access horribly slow

Probably the local disk holds a lot of files and folders, this slows down
browsing the local disk. What version of RDP client is used? Which SP is
installed on the server?

"Freaky" wrote:

> Just got the error from the customer. It was in dutch so I had to
> translate it, but this seems to be the correct message:
>
> "The I/O operation has been aborted because of either a thread exit or
> an application request"
>
> TIA
>
> Freaky wrote:
> > Hey there,
> >
> > we have several customers that can work flawlessly on our terminal
> > server. The applications on the terminal work very fast.
> >
> > The customers also connect their local drivers, and this is where the
> > problems lie. Access to the local disk is extremely slow. Every time
> > they click a folder they have to wait around a minute for the directory
> > listing. Browsing through 10 folders deep therefore is not doable. Also
> > copying large files (larger than 10MB) from the local disk to the
> > terminal often fails.
> >
> > The terminal connection itself is very stable. Also uploading (very)
> > large files from the workstation/customer PC to for example a webserver
> > with FTP gives no issues whatsoever.
> >
> > Any ideas?
> >
> > TIA
>
 
Re: Local disk access horribly slow

Hoi Bart,

thanks for the re'. Almost all computers at a certain customers location
have this. They have one of those firewalls that scans for virusses (a
fortigate) in some protocols. Thinking this is causing the corruption,
also can't seem to copy a 500MB file through sftp through the firewall.

Strange this is that it shouldn't proxy (and thus interfear with the
traffic) on either RDP or SSH protocols (just HTTP, POP, IMAP, SMTP,
NNTP, IM).

Quite certain this must be it, seeing this error never pops up on the
internet in combination with terminal services. That and it happening on
multiple computers makes the firewall a prime suspect, which I'm gonna
expect next.

Anyways thanks again.

Groetels

Bart Van Vugt wrote:
> Probably the local disk holds a lot of files and folders, this slows down
> browsing the local disk. What version of RDP client is used? Which SP is
> installed on the server?
>
> "Freaky" wrote:
>
>> Just got the error from the customer. It was in dutch so I had to
>> translate it, but this seems to be the correct message:
>>
>> "The I/O operation has been aborted because of either a thread exit or
>> an application request"
>>
>> TIA
>>
>> Freaky wrote:
>>> Hey there,
>>>
>>> we have several customers that can work flawlessly on our terminal
>>> server. The applications on the terminal work very fast.
>>>
>>> The customers also connect their local drivers, and this is where the
>>> problems lie. Access to the local disk is extremely slow. Every time
>>> they click a folder they have to wait around a minute for the directory
>>> listing. Browsing through 10 folders deep therefore is not doable. Also
>>> copying large files (larger than 10MB) from the local disk to the
>>> terminal often fails.
>>>
>>> The terminal connection itself is very stable. Also uploading (very)
>>> large files from the workstation/customer PC to for example a webserver
>>> with FTP gives no issues whatsoever.
>>>
>>> Any ideas?
>>>
>>> TIA
 
Re: Local disk access horribly slow

Hi Freaky,

What is the bandwidth on the servers location?
And what on the sites where the clients are?
Can you do a test when you are use nobody else is on the TS?
Maybe the line is the bottleneck.

Let us know.
All the best, en de groetjes,
Yuri
 
Re: Local disk access horribly slow

Is there any firewall? How does it perform for opening a network shared
drive?

Thanks

Rong


--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Freaky" <wontsay@ondeja.com> wrote in message
news:%23BtHvYUTIHA.5288@TK2MSFTNGP04.phx.gbl...
> Just got the error from the customer. It was in dutch so I had to
> translate it, but this seems to be the correct message:
>
> "The I/O operation has been aborted because of either a thread exit or
> an application request"
>
> TIA
>
> Freaky wrote:
>> Hey there,
>>
>> we have several customers that can work flawlessly on our terminal
>> server. The applications on the terminal work very fast.
>>
>> The customers also connect their local drivers, and this is where the
>> problems lie. Access to the local disk is extremely slow. Every time
>> they click a folder they have to wait around a minute for the directory
>> listing. Browsing through 10 folders deep therefore is not doable. Also
>> copying large files (larger than 10MB) from the local disk to the
>> terminal often fails.
>>
>> The terminal connection itself is very stable. Also uploading (very)
>> large files from the workstation/customer PC to for example a webserver
>> with FTP gives no issues whatsoever.
>>
>> Any ideas?
>>
>> TIA
 
Back
Top