login fails when connecting to named instance from different subnet

From: Kathy Sedro (ksedro@trane.com)
Date: 12/04/02 

From: "Kathy Sedro" <ksedro@trane.com>
Date: Wed, 4 Dec 2002 10:13:38 -0800

I have a default instance and a named instance of SQL
Server 2000 on the same PC running NT server.
I am connecting using OLE DB.
I am seeing the following:
* Users on the same subnet as the server are able to
connect to the named instance.
* Users on a different subnet can connect to the named
instance using SQL authentication.
* Users on a different subnet can connect to the named
instance using NT authentication only if they are also
allowed to connect to the default instance.

What I want is for users to be able to connect only to the
named instance, using NT authentication. Can anyone tell
me what I need to do to accomplish this?

When I set up a .udl file to connect to my named instance
from a different subnet, selecting OLEDB provider for SQL
Server, the "Test Connection" button is able to connect
succussfully if the user has access to the default
instance or if I use SQL authentication. Otherwise, I
get the following error:
    "Test connection failed because of an error in
initializing provider. Login failed for user '(null)'.
Reason: Not associated with a trusted SQL Server
connection."

I do not see these problems when the SQL Server is on a
PC running Windows 2000.

Thank you,
Kathy