|
Question : Netware Client32 and Windows 95 Timeout ODBC Connection problem
|
|
I have installed a client-server (Access-SQL Server)database solution in a customer's NT LAN environment where some PC's are using NT Workstation and some are using Win95 as their OS. All are using Netware Client32 for login and network connection. They connect to the SQL-Server Backend as an ODBC source using Named Pipes.
The odd thing is that the database application runs fine on the NT machines, but on the Win 95 machines, the ODBC connection to SQL Server times out and the connection is broken at or about 25 seconds. We have replicated this in a lab situation, but still don't know why it is occuring.
Does the combination of Client32 and Win 95 run more slowly? Is there any setting in Client32 that would affect the time limit before dumping an ODBC connection?
More details- This is not a recordlocking situation, but appears to be related to a timeout.
I am the database guy, not a Novell guy, and the Novell guy just quit for a better job, so there is no local expert to ask (but then, why do I need a local expert when I have all of you???)!
Thanks in advance,
Tim
|
Answer : Netware Client32 and Windows 95 Timeout ODBC Connection problem
|
|
Try to read this TID.
Client32 for Win95; Named Pipes not Supported (Last modified: 5NOV1998) TID2926061 This document (2926061) is provided subject to the disclaimer at the end of this document. Symptom Customer uses Named Pipes to access an SQL server. Vlm workstations run DosNP and DBMNPipe. They launch ODBC, which lists the available SQL servers, and allows the user to choose one. VLM workstations running Windows3.x have no problem with this. With vlm's and Windows95, it works too -- using the 16 bit version of ODBC. But with Client32 and Windows95, no SQL servers show in ODBC.. Solution Named pipes as implemented is not supported with Client32 for Windows95 version 2.12. Try using named pipes with the Microsoft client for Microsoft networks.
From the Help files for Windows95/ Client32:
Client32 supports Windows** 95** implementations (i.e. Microsoft's versions) of TCP/IP, Server Messenger Blocks (SMB), Windows Sockets (Winsock), Named Pipes, and NetBIOS.
And also:
The following were supported as NetWare* configuration options in previous NetWare clients but are not supported in this release of NetWare Client* 32* for Windows** 95**:
Named Pipes
NetBIOS
NetWare DOS TSA
Protocol RPL
Protocol TCPIP
Transport Provider
See also the Windows95 Resource Kit page 1015.
Document Title: Client32 for Win95; Named Pipes not Supported Document ID: 2926061 Document Revision: 2 Creation Date: 29MAY1997 Modified Date: 5NOV1998 Novell Product Class: NetWare Novell BorderManager Services
Novell Product and Version: BorderManager 2.1 (also called 1.0) NetWare 3.12 NetWare 3.2 NetWare 4.1 NetWare 5 NetWare for Small Business 4.11 NetWare for Small Business 4.2 Novell Clients
|
|
|
|