Connection problem

I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?
"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve
|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:

> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:

> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:

> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:

> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
sqlsql