We have SQL Server 2000 installed on Windows Server 2003 SP 1. The server is
a member of a domain.

We have developers on workstations not part of the domain who need to use a
Trusted Connection to access a database on the server. I've read some other
posts that suggest this is possible. The developers created a local account
on their workstation with the username/password credentials that match those
of a domain user. When logged in under that account on their local
workstation, I believe they should be able to establish a trusted connection
to SQL Server using Enterprise Manager. But the authentication fails with the
message "Logon failed for user '(null)'."

Any suggestions would be appreciated.