A connection could not be established between networks

While trying to connect SQL server from one network to another I'm suddenly
getting this error message:
A connection could not be established to ServerName.
Reason: Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection..
Please verify SQL Server is running and check your SQL Server registration
properties...
Windows authentication validates. Different logins are used for both
servers, but SQL Server is set to startup using the same login and password.
This login is given administrator rights on both servers.
?
"Steven" <Steven@.discussions.microsoft.com> wrote in message
news:DD3A83A2-71C0-4030-A92A-C7A02BF85AF4@.microsoft.com...
> While trying to connect SQL server from one network to another I'm
suddenly
> getting this error message:
> A connection could not be established to ServerName.
> Reason: Login failed for user '(null)'. Reason: Not associated with a
> trusted SQL Server connection..
That usually means that the user account could not be translated into an SQL
Server login account. Perhaps because the domain\user account does not have
access to the server running SQL Server.

> Please verify SQL Server is running and check your SQL Server registration
> properties...
> Windows authentication validates. Different logins are used for both
> servers, but SQL Server is set to startup using the same login and
password.
> This login is given administrator rights on both servers.
> ?
I'm confused by the last 2 sentences. Are these servers in a domain,
workgroup or simply standalone servers?
Steve
|||There are actually 3 servers: A, B, & C. Server A is in workgroup 1 and
cannot connect to servers B or C. Server B is in workgroup 2 and cannot
connect to server A, but can connect to server C. Server C is in a domain
and connects to server B, but not server A.
Important notes: Servers A runs under the NT login of Admin with a password
of AdminPW1. Servers B and C run under the NT login of Admin with a password
of AdminPW2. All three servers use the start up account of user SQLAdmin
with a password of SQLAdminPW and all three servers are set to use Windows
and SQL Server authentication.
Also, replication is working between servers A and B and between servers A
and C. It's the Ent Man that's not able to connect.
"Steve Thompson" wrote:

> "Steven" <Steven@.discussions.microsoft.com> wrote in message
> news:DD3A83A2-71C0-4030-A92A-C7A02BF85AF4@.microsoft.com...
> suddenly
> That usually means that the user account could not be translated into an SQL
> Server login account. Perhaps because the domain\user account does not have
> access to the server running SQL Server.
> password.
> I'm confused by the last 2 sentences. Are these servers in a domain,
> workgroup or simply standalone servers?
> Steve
>
>