Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Clipper-Applications very slow in Windows2003-Network

2 posts in Networking Last posting was on 2005-06-21 09:49:34.0Z
Matthias Bendorf Posted on 2005-05-09 15:32:49.0Z
From: "Matthias Bendorf" <mbendorf@trigondata.de>
Newsgroups: Advantage.Networking
Subject: Clipper-Applications very slow in Windows2003-Network
Date: Mon, 9 May 2005 17:32:49 +0200
Lines: 36
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: 62.153.109.180
Message-ID: <427f8423@solutions.advantagedatabase.com>
X-Trace: 9 May 2005 09:39:15 -0700, 62.153.109.180
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!62.153.109.180
Xref: solutions.advantagedatabase.com Advantage.Networking:538
Article PK: 1131960

Hello,

we are running a 16-Bit-Clipper Application (Dr. Huggle CL Professional,
Clip4Win compatible) with
ADS 7.1 on Windows 2003 Server with Windows 2000 Prof. / XP Prof. Clients.
IP is the only protocol on server and clients.
The application needs about 5-10 seconds to connect to the ADS and even
browsing the database within the
application is very slow (1-2 seconds for browsing from one to the next
record, also when there are only a few records in the database).

In a Novell-Environment with IPX as the only protocol (and ADSIP16.DLL not
present at the system) the same application with the same database runs
blazing fast (less than 1 second to connect, browsing the database without
any
delay).

I cannot believe that IP is so much slower than IPX because we have on
Windows 2000 Server on which the same application runs as fast as under
Novell - independent of the Client-PC we use. Only difference in
Network-Settings is that NetBEUI protocol is installed on this server. We
tried NetBeui on a fresh installed Windows 2003 Server but it didnt change
the speed.

What we tried further:
- We checked the AUTOEXEC.NT for IPX-entries (often mentioned in the groups
when discussing performance issues)
- We tried to install IPX-Protocol on server and client

So what are we doing wrong with Windows 2003 environment?
Thanks for any hint that helps us to get rid of the brake.

Matthias Bendorf
Trigon Data GmbH


Matthias Bendorf Posted on 2005-06-21 09:49:34.0Z
From: "Matthias Bendorf" <mbendorf@trigondata.de>
Newsgroups: Advantage.Networking
References: <427f8423@solutions.advantagedatabase.com>
Subject: Re: SOLUTION - Clipper-Applications very slow in Windows2003-Network
Date: Tue, 21 Jun 2005 11:49:34 +0200
Lines: 57
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 62.153.109.180
Message-ID: <42b7e45a@solutions.advantagedatabase.com>
X-Trace: 21 Jun 2005 03:56:42 -0700, 62.153.109.180
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!62.153.109.180
Xref: solutions.advantagedatabase.com Advantage.Networking:542
Article PK: 1131965

Good News:
At least we found some lanmanserver parameters which release the brake.

Disable Oplocks and Open File Caching on the Server, after a Reboot the
Clipper-Applications run as fast as in the Novell-Environment. It works fine
with Win 2000, 2003 Server and 2003 SBS.

HKLM\System\CurrentControlSet\Services\lanmanserver\parameters
--> new DWORD EnableOplocks, 0
--> new DWORD CachedOpenLimit, 0

I hope this hint can help in other cases too...

Regards,

Matthias Bendorf

"Matthias Bendorf" <mbendorf@trigondata.de> schrieb im Newsbeitrag
news:427f8423@solutions.advantagedatabase.com...

> Hello,
>
> we are running a 16-Bit-Clipper Application (Dr. Huggle CL Professional,
> Clip4Win compatible) with
> ADS 7.1 on Windows 2003 Server with Windows 2000 Prof. / XP Prof. Clients.
> IP is the only protocol on server and clients.
> The application needs about 5-10 seconds to connect to the ADS and even
> browsing the database within the
> application is very slow (1-2 seconds for browsing from one to the next
> record, also when there are only a few records in the database).
>
> In a Novell-Environment with IPX as the only protocol (and ADSIP16.DLL not
> present at the system) the same application with the same database runs
> blazing fast (less than 1 second to connect, browsing the database without
> any
> delay).
>
> I cannot believe that IP is so much slower than IPX because we have on
> Windows 2000 Server on which the same application runs as fast as under
> Novell - independent of the Client-PC we use. Only difference in
> Network-Settings is that NetBEUI protocol is installed on this server. We
> tried NetBeui on a fresh installed Windows 2003 Server but it didnt change
> the speed.
>
> What we tried further:
> - We checked the AUTOEXEC.NT for IPX-entries (often mentioned in the
> groups when discussing performance issues)
> - We tried to install IPX-Protocol on server and client
>
> So what are we doing wrong with Windows 2003 environment?
> Thanks for any hint that helps us to get rid of the brake.
>
> Matthias Bendorf
> Trigon Data GmbH
>
>