Currently on my site we have 100s of Windows 95 SQL server clients. The
windows 95 machines logon to a Netware 4.11 network using Novells
intranetware client and connect to SQL Servers (version 6.5) using ODBC and
the TCP/IP Sockets net library and therefore use standard SQL Server
The windows 95 machines are running both IPX/SPX and TCP/IP
SOME of the users will shortly be also be given a logon to an NT Domain and
want to use integrated security to connect to SQL Server. For simplicity I
want to be able to use the same net library (either Named Pipes or
Multi-protocol) for all clients whether they are going to use integrated
security or not.
I can get the Multi-protocol connection working for either integrated or
standard security but only if the client machine is logged on to the NT
domain. Obviously if youre going to use a trusted connection you need to
be logged on to an NT domain for it to work, but I cant see why the same
should apply for standard security. The error message I get when not logged
on to the domain says that the specified server is unavailable or does not
I get the same message when using Named Pipes but it happens whether the
client machine is logged on to the network or not.
Anybody got any ideas.