Slow client connect 
Author Message
 Slow client connect

Why would two computers configured in exactly the same (at least, as far
as I can see!) have such disparate connect times when using ISQL/w or
ODBC?

Both machines are Win95, pentiums, 64 meg RAM.  I have both Microsoft
and Netware clients installed under the Network applet in Control Panel
with all properties for all the protocols (TCP/IP, NetBEUI, IPX/SPX) set
exactly the same.  Yet one machine is almost instantly connected to the
server using the ISQL/w app while the other takes nearly five minutes.
Using Access and ODBC, I can link to tables on the server in less than
ten seconds on one machine while on the other machine, I get a timeout
error!  

Are there any setting anywhere else I might have missed or can check?
This is driving me nuts (and so is my boss!).

TIA, Del G.

P.S.  IS there an ODBC setting that determines the wait time before a
timeout?  I'm not exactly sure, but I think the ODBC driver version is
2.5.



Fri, 12 May 2000 03:00:00 GMT
 Slow client connect

Del,

You may want to upgrade your ODBC SQL drivers to 2.65.0240 (I think this is
the latest)

Your Speed problem may be due to a networking feature called direct
Hosting.  Here is an excert taken from the WindowsNT Mag.  It was written
by a SQL MVP called Brian Moran and it explains the problem/solution well.

The problem is a result of a networking enhancement called direct hosting.
Microsoft implemented the enhancement in network client software to
increase communications speeds. Direct hosting lets the client bypass the
NetBIOS layer when communicating with the server over IPX. Unfortunately,
the Win95 direct-hosting technology seriously slows processing when you use
it over Named Pipes. Named Pipes is the default and most commonly used SQL
Server NetLib. (A NetLib is the software that lets a client talk to SQL
Server over the network.) I've seen queries that return just a few rows
take 2 seconds from an NT client and more than 20 seconds from Win95
clients. Ouch!

Getting around the problem is simple. Because SQL Server clients are slow
when they use direct hosting with IPX over Named Pipes, my advice is:
"Don't do that." I know two easy alternatives. Both alternatives let you
use IPX but avoid the deadly direct-hosting-over-Named-Pipes problem.

One technique is to disable direct hosting. This technique works fine, but
it requires hacking the Registry and can slow the performance of other
applications on your client that don't use Named Pipes. If you have your
heart set on this method, Microsoft Knowledge Base article Q156430
(http://www.microsoft.com/kb/articles/q156/4/30.htm) lists the necessary
Win95 Registry changes to disable the direct hosting feature for client
computers running Win95. To the Registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VxD\VN, add a string
value named DirectHost, and set the string value to 0. Also ensure that
NetBIOS support is enabled for NWLink if NWLink is the only transport
protocol loaded on the client computer.

I recommend keeping your life simple by using the other alternative: Pick a
different SQL Server interprocess communication (IPC) mechanism, such as
IPX sockets or the Multi-Protocol NetLib. Changing the default IPC for a
SQL Server client is a breeze. The SQL Client Configuration Utility
provides a GUI for setting up all client site networking information.
Configuring the Client Software in Books Online (BOL) explains the process
well.

--
I hope this was of use.

Steve Robinson



Mon, 15 May 2000 03:00:00 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. Some clients connect fast, some slow

2. Very slow to connect the client over the network

3. Vb clients slow when more than 1 client log in

4. Vb clients slow when more than 1 client log in

5. SQL Server super slow when Novell Client For Netware is installed on client PC

6. SQL Server super slow when Novell Client For Netware is installed on client PC

7. SQL Server super slow when Novell Client For Netware is installed on client PC

8. SQL 2000 client toosl slows down Windows 98 client machine

9. SQL2000 slower in Win2K-Clients ->98 +Dos Clients almost double Speed

10. SQL Server super slow when Novell Client For Netware is installed on client PC

11. slow opening connection using w2k client vs nt client

12. Net8: connect from remote client but not local client


 
Powered by phpBB® Forum Software