Re: Credentials not being passed with remote access
- From: "Dan Guzman" <guzmanda@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 9 Aug 2007 07:34:47 -0500
That being the case, do you still think it could be a firewall issue and if
so, what would I look for in the firewall configuration?
If other users can successfully login with Windows authentication from the same machines that fail with "john", then it's probably not a firewall issue. Furthermore, since "johnx" can successfully login locally, it appears "johnx" is setup correctly in SQL Server.
The main difference between local and remote access is the communication protocol. Local access usually uses LCP but remote access is usually done via TCP/IP or Named Pipes (as specified by the cliconfg.exe utility). Named pipes requires the Windows account to have the "access this computer from the network" right so make sure "johnx" has the right (via group membership) if you are using Named Pipes.
After a successful connection of your working account, you can verify the connection protocol with:
SELECT net_library
FROM master..sysprocesses
WHERE spid = @@spid
If you still can't sort this out, try to connect using SSMS and post the full error message text here.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"jp" <jp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:FC3706EE-CE61-47EE-85A4-DEDDA3A633F6@xxxxxxxxxxxxxxxx
Dan, thank you for your response. I have seen you post helpful information
for many people before.
We looked at the time sync yesterday and it is close.
The odd thing is that it is specific to one login. Login "johnx" does not
pass credentials from any machine. My other login "johnz" works from any
machine. Also, no other users are reporting this problem with their login.
That being the case, do you still think it could be a firewall issue and if
so, what would I look for in the firewall configuration?
And again, to make it more frustrating, "johnx" can use Windows
Authentication on another SQL Server on the same domain with no problem.
--
John Shahan
"Dan Guzman" wrote:
> What could be specific to the login or the server that would cause the
> credentials not to be passed.
This could be caused by a firewall issue with domain controller
communication. I've also seen this problem due to a time sync issue between
the client and servers.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"jp" <jp@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4B43E6E3-D0F0-4084-AED0-6D4139DA79CB@xxxxxxxxxxxxxxxx
>I cannot remotely access SQL Server 2005 with Windows Authentication >with a
> specific login (I get the error 18452 "this user is not associated with > a
> trusted login.."). I ran a trace with the profiler and it shows that > no
> values are being passed for the login/credentials.
>
> I can login to the server locally just fine with the login.
>
> Windows Authentication works with the same login work against another > SQL
> Server machine.
>
> What could be specific to the login or the server that would cause the
> credentials not to be passed.
> -- > John Shahan
.
- Follow-Ups:
- References:
- Re: Credentials not being passed with remote access
- From: Dan Guzman
- Re: Credentials not being passed with remote access
- Prev by Date: Re: job access
- Next by Date: User can't be deleted because it has granted/denied permissions on objects
- Previous by thread: Re: Credentials not being passed with remote access
- Next by thread: Re: Credentials not being passed with remote access
- Index(es):
Relevant Pages
|
|
