Showing posts with label authority. Show all posts
Showing posts with label authority. Show all posts

Thursday, March 29, 2012

Error 18456

I am repeatedly receiving the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
This has been occuring since a network wide password
change ( for an employee leaving the company ) and I do
realize that there is some process trying to connect, but
I do not know how to find out what the process is, or
what it is trying to connect as. Is there a way to trace
this information?You may be able to catch this with SQL Profiler and/or a network trace.
The network trace will only work if the connection is coming from a remote
machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Have tried the profiler and don't get enough information
to track. Haven't tried a network trace, I will try, but
I don't think it is a remote connection. Thanks for your
help.
Rachel

>--Original Message--
>You may be able to catch this with SQL Profiler and/or a
network trace.
>The network trace will only work if the connection is
coming from a remote
>machine.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>

Wednesday, March 21, 2012

Error 1418, NT AUTHORITY\Anonymous login

Hello All!

Can you help me with that problem:

I want to mirror some database to another server (without witness server)

I have 2 machines, where Microsoft SqL '05 Developer Edition SP1 installed.

Two machines working in domain network, one of them is a server, secondmachine enters into domain with username and password.

I can ping each machine by the ip adress and by the networks name, like a.machine.com, b.machine.com

TCP/IP is enabled in Server Configuration.


What I DO:


1. Create full backup of my database on server A

2. Create full backup of transaction logs on server A

3. Restore my database and transaction logs from backup WITH NO RESTORE on server B

4. On machine A: I open tasks -> mirroring properties dialog (configuring mirroring) and go to configure security dialog.

5. I use standart properties (port, endpoint name, ecryption)

6. On page "Mirror Server Instanse" i click "Browse for more" and type there server B adrress (b.machine.com). Click connect.

7. Server configuring was sucsessful

8. Server network addresses were:

Principal : TCP://a.machine.com:5022

Mirror : TCP://b.machine.com:5022

9. I click Start Mirroring but system gives me error:
Error 1418, The Server network address can not be reached or does not exists.

I open logs on machine b (mirror server):
Message

Database Mirroring login attempt by user 'NT AUTHORITY\Anonymous login.' failed with error:
'Connection handshake failed. The login 'NT AUTHORITY\Anonymous login' does not have CONNECT permission on the endpoint.
State 84.'. [CLIENT: 172.168.0.130]

and this message before:
The database 'mybase' is marked RESTORING and is in a state that does not allow recovery to be run.


When I configured database mirroring, i choose "Windows Authentication", Why 'NT AUTHORITY\Anonymous login.' ...?

This SQL Server message indicates that the server network address cannot be reached or does not exist, and it suggests that you check the network address name and reissue the command. http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=14871 fyi.|||

Hi

From the errors it looks like your SQL Server is not using domain account to run SQL Server service.

Please use a domain account and ensure that account has permissions on the Database mirroring endpoints.

Jag

|||

I did it!

My error was:

I don't add domain user in security -logins at both servers.

Whet i added my user1 to server A and server B - it workes!

Jag Sandhu - thank you for your reply, I used domain accounts, but i forgot to allow access for current user in database.