Another thought.

It could be you client configuration. I haven't got SQL Server on my machine here right now, I can mail you exact details when I get home.

If I remember rightly, there is a client configuartion utility that appears on the SQL Server menu options (from the win95/nt start button).

In here you can set the communications driver to be used between the client and the server. You may be using the general driver, which may try a number of different protocols.

Using the utility, try selecting the IP or TCP/IP specific drivers.


>Mark,
>
>The test I am doing is on a dedicated LAN (NT Server linked directly to Win95) with just the two PCs on BNC about two feet away from each other. The tables on SQL Server are presently empty. The structure is about 100 bytes, the clustered (Primary) index is the Identity column incremented by one. I have only got to about 300 rows so far before I aborted. Bulk inserting into a temporary table wouldn't work in this case because the tables I am working on at the moment are empty anyway.
>