Very Computer

I am currently have the following problem where my calls
to the SQL Server 2000 is super slow if I have "Novell
Client for Netware" installed on my client PC.  My setup
is as follows:

Running a W2K Server with SQL Server 2000 installed on
it.  On my client machine I am running W2K Professional
with "Novell Client For Netware" installed on it.  I can't
remove "Novell Client For Netware" as I need access to my
Novell Network.

The problem is that when my application tries to connect
to SQL Server, it is very very very slow.   If I remove
the "Novell Client For Netware" from the client machine
then it speeds up and it can communicate with the SQL
Server with no problems.  With the "Novell Client For
Netware" installed, it can still communicate but it slows
down about 10 times or more.

My application uses ADO and OLE/DB to communicate with SQL
Server and I am using MDAC Version 2.6.

The client and server machines both have TCP/IP and
IPX/SPX network protocols installed for SQL Server.  
Initially, when SQL Server was installed on the Client and
Server they had Named Pipes and TCP/IP protocols installed
by default, but my application could not communicate until
I added the IPX/SPX protocol on the client machine's SQL
Server.

The following document from MS describes a slow connection
problem when using MDAC 2.6 and IP address instead of the
machine name (which we need to do because of our Novell
Network Setup), however, it doesn't seem to be exactly
this problem, since it suggests that this problem should
be occuring regardless of whether the novell drivers are
installed or not, which is not true in my case:
        http://support.microsoft.com/default.aspx?
scid=kb;EN-US;q300420

I would really appreciate any help or insight that anyone
can provide.

Regards
Iraj

Quote:> Hi All,

> I am currently have the following problem where my calls
> to the SQL Server 2000 is super slow if I have "Novell
> Client for Netware" installed on my client PC.  My setup
> is as follows:

> Running a W2K Server with SQL Server 2000 installed on
> it.  On my client machine I am running W2K Professional
> with "Novell Client For Netware" installed on it.  I can't
> remove "Novell Client For Netware" as I need access to my
> Novell Network.

> The problem is that when my application tries to connect
> to SQL Server, it is very very very slow.   If I remove
> the "Novell Client For Netware" from the client machine
> then it speeds up and it can communicate with the SQL
> Server with no problems.  With the "Novell Client For
> Netware" installed, it can still communicate but it slows
> down about 10 times or more.

> My application uses ADO and OLE/DB to communicate with SQL
> Server and I am using MDAC Version 2.6.

> The client and server machines both have TCP/IP and
> IPX/SPX network protocols installed for SQL Server.  
> Initially, when SQL Server was installed on the Client and
> Server they had Named Pipes and TCP/IP protocols installed
> by default, but my application could not communicate until
> I added the IPX/SPX protocol on the client machine's SQL
> Server.
...
> I would really appreciate any help or insight that anyone
> can provide.

The network protocols, as installed, imply a
preferred order for trying to find other
systems on the network.

When a connection is being established, the
attempt is first made thru the protocol
that is most preferred, then the next most,
and so on.  This can involve timeouts.

You can switch the protocol ordering and
get relief on this performance problem,
although this may make connection to stuff
using the Novell protocol slower.

--
-Larry Brasfield
(address munged, s/sn/h/ to reply)

I had the very same problem two days ago. I have Win 98 clients accessing
SQL 2000 on a Win 2000 Server that is connected with Novell 5.

The clients have to communicate with either of the server.

The problem was IP adress resolution. When a Win 98 tried to open an ADO
connection it was painfully slow. Even a ping with the server name was
long...

The network technician had to add the IP adresse in the DNS...

Hope it will helkp you,

David Quirion