Re: Remote NT Login not working

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

When using Integrated Security, your machine must be part of an
authenticated domain on the Win2003 server and this account must be added to
the list of accounts accepted by SQL-Server. The fact that your copy of
the adp on the server works means nothing in this regard.

Please consult your network specialist in order to configure your machine to
be part of an authenticated domain recognised by the Win2003 Server. After
that, you will be able to add this account or its domain to the list of
accounts and domains recognised by SQL-Server.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


<sfarkas@xxxxxxxxx> wrote in message
news:1177208799.851853.317000@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have created a new adp with a SQL Server backend. I have the adp
file on my laptop and the SQL Server resides on a remote server that I
access via a VPN. When I open up the adp on my laptop and select File-
Connection and type in the server name of the SQL Server and select
Use a Specific User Name and Password I get a perfectly fine
connection to the database and everything works.

However I want to use Windows NT Integrated Security. When I try to
select this I get an error:

Login failed for user ". The user is not associated with a trusted
SQL Server connection.

The error seems to indicate the username I am passing to SQL Server is
null. I have set up logins and users on SQL Server that work. I know
this because I also have a copy of the adp on the server itself and
when I use NT Security from that adp everything works fine.

So the basic question is:

How can I get my remote laptop to pass a valid username (and I presume
password) to the SQL Server so that I can use Windows NT Integrated
Security?

Thanks.



.

Relevant Pages

  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... Client computer must use STRICTLY the INTERNAL DNS server which can ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Re: Same question, still no answer!!!
    ... Sounds then like we are all paying for a feature set only large companies ... The "proxy server" pc is actually an older box stuffed ... Expectation #1) keep the ethernet more or less as is. ... The kids account would be ...
    (microsoft.public.windowsxp.basics)
  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... This would be on the DNS server 172.20.100.2 ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
  • Sending email to mydomain.com
    ... server will appear as undeliverable. ... This happens because you are using the POP3 connector... ... an NDR when an account doesn't exist). ... >different from the user account names for the exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Basic Authentication + IIS 5 + Windows 2000 + Frontpage 2002 = failure?
    ... Everytime I attempt to login under Basic Authentication, ... IUSR_blah account. ... the anonymous user impersonated by the IIS Server is the ... > Event Viewer Security log. ...
    (microsoft.public.inetserver.iis.security)