Re: Trouble registering a server

I have poked around a bit and would like to rephrase my previous response...

My problem is (1) when I log in to the remote physical machine using Remote
Desktop Connection, I do not have Admin rights on that machine and (2) I
cannot get a server registered within a SQL Server Group.

This is what I think you are telling me:
1. Someone with Admin rights on that machine could get into Enterprise
manager and register a server within a Server Group.
2. Then, the person with Admin rights could go into that server and create a
login for my windows username so that, while connected via Remote Desktop
Connection, I could manipulate that single database.
3. At the same time,the person with Admin rights could also create a login
for me to use from my remote machine (or I could use the same login as
already set up). This would now allow me to use Enterprise Manager on that
server from my remote machine and would also allow me to log into that server
from my Access front end on my local machine.

Is all of this correct?

"Jasper Smith" wrote:

> Right, so that suggests that your windows domain account is not setup as a
> login on the server. You need to get someone who is a local administrator on
> the server to add your login account to SQL Server using Enterprise Manager
> (Security>Logins>New Login). The good news is that you are actually
> connecting to the server okay (since the login failed error is returned by
> SQL directly)
>
> --
> HTH
>
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Bill Sturdevant" <BillSturdevant@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:7560D58A-E140-4085-96FD-9C900AB052F0@xxxxxxxxxxxxxxxx
> > Now I get the following message:
> >
> > ServerName - Login failed for user 'XXXXXX\myWindowsUserName' where XXXXXX
> > is maybe some sort of domain name...
> >
> > "Jasper Smith" wrote:
> >
> >> You do not need to supply your username and password if connecting using
> >> a
> >> windows account (which it sounds like you are doing). It also sounds like
> >> the server is set for Windows Authentication only. Simply don't supply
> >> the
> >> username and password when registering the server (if using the wizard
> >> select the top option on the "Select an Authentication Mode" page - the
> >> option is labeled Windows Authentication
> >>
> >> --
> >> HTH
> >>
> >> Jasper Smith (SQL Server MVP)
> >> http://www.sqldbatips.com
> >> I support PASS - the definitive, global
> >> community for SQL Server professionals -
> >> http://www.sqlpass.org
> >>
> >> "Bill Sturdevant" <BillSturdevant@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> >> message news:B134A1B1-CFAE-4F20-B196-A73748D18C3F@xxxxxxxxxxxxxxxx
> >> >I have SQL Server 2000 installed on a Windows 2K machine. The machine
> >> > happens to be located in another city. I do not have administrator
> >> > rights
> >> > on
> >> > this machine, but am able to collect to it using Remote Desktop
> >> > Connection.
> >> > Someone at that location installed DQL Server for me, but neither of us
> >> > really understood what we were doing at the time.
> >> >
> >> > I could not start/stop SQL Server, but discovered I could go into
> >> > MSSQLWERVER Properties (Control Panels\Administrative
> >> > Tools\Services\MSSQLSERVER) and set up a SQL Server account which
> >> > allows
> >> > me
> >> > to start and stop SQL Server.
> >> >
> >> > Now, working remotely but on that same machine, I am in Entrerprise
> >> > Manager
> >> > trying to Register a server. I right click on the ServerGroup and
> >> > select
> >> > New
> >> > Server Registration. I select the server (there happens to be others
> >> > available in this installation so they show up), then enter the
> >> > Username
> >> > and
> >> > password I set up for myself in MSSWLSERVER, but it fails telling me my
> >> > Username is "Not associated with a trusted SQL Server connection"
> >> >
> >> > What am I doing wrong, not doing?
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Terminal Services Setup/Flaw
    ... This still allows everyone to hit the TS Server but denies the login to ... Terminal Server with this user and then .rdp into another server on the ... I found the Remote ...
    (microsoft.public.windows.terminal_services)
  • SecurityFocus Microsoft Newsletter #152
    ... MICROSOFT VULNERABILITY SUMMARY ... Real Networks Helix Universal Server Remote Buffer Overflow ... ... NEW PRODUCTS FOR MICROSOFT PLATFORMS ...
    (Focus-Microsoft)
  • Re: SQL2005: Cannot connect error 11001
    ... The famous Windows Firewall (turned on my Server from which I'm trying to ... Exception Details: System.Data.SqlClient.SqlException: Login failed for user ... Try starting the SQL Server ... if you changed the port ...
    (microsoft.public.sqlserver.connect)
  • SecurityFocus Microsoft Newsletter #140
    ... Cafelog b2 Remote File Include Vulnerability ... Webfroot Shoutbox Remote Command Execution Vulnerability ... Pablo Software Solutions Baby POP3 Server Multiple Connection... ... Microsoft Windows XP Nested Directory Denial of Service... ...
    (Focus-Microsoft)
  • Re: error logging on SQL 2008
    ... I was, though, hoping for some more recognizable Reason for that error (state 11, " Token-based server access validation failed with an infrastructure error. ... Suggests that state 11 means "Valid login but server access failure", which doesn't really seem to rhyme with your description. ... How can you login to your SQL Server and use that tool if you can't log into your SQL Server? ... at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) ...
    (microsoft.public.sqlserver.server)