Login failed for user ''NT AUTHORITY\ANONYMOUS LOGON

Hello Guys,

I have two machines that i want to use for merge replication :

Laptop ( Publisher + Distributor )

VPS90 ( Subscriber )

Both connected via the internet

NO DOMAIN

Need to implement merge replication ,after initializing the snapshot I get the following error on both machines :

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 192.168.1.1]

I created a new user "Repuser" (admin)with the same password on both machines and configured the Agent proccess to run under that account ,now i get this error :

Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.1]

Please note that :

· Mixed mode authentication IS ENABLED ON BOTH MACHINES

· BOTH MACHINES CAN PING AND ACCESS EACH OTHER ,BOTH COMPLEETELY VISIBLE.

· CONFIGURED ALIASES ON BOTH MACHINES.

· Both configured to use Sa account .

* I have NO DOMAIN

what does this mean?

It simply means that the SQL Server Agent process account is the one that’s being authenticated to connect to the other machine and NOT the Sa account ,WHY?

do i have to use Web Synch in my case?

hi,

replication uses the sql server agent services

your sql services should be running on an account that has

access to replication resources such as the snapshot folder or the replication folder.

the sql server services should be able to access both machine

regards,

joey

|||how can i make the SQL Server Agent account access the other machine ? supposing that i have no domain? please clarify|||Hello?!! Any 1 there?!|||

how are the machine connected in the internet anyway?

are the IPs exposed over the web? Are you using VPN's?

192.168.1.1 seems to be a local IP

anyway...

I think it is not possible to do replication without domain

maybe some other solution would be better in the scenario

like

the SQL SERVER integration services (SSIS)

|||

thanks for the reply joeydj

both machines are exposed to the internet openely ,no VPNs ,first 1 with a static IP (in USA) and the other is via a DSL modem via NAT (thats y u saw 192.168.1.1) ,they can both connect to each other via SQL server Management Studio with out any problems ,i think microsoft made it nearly impossible to do anything with out Domain ,which is really stupid ,as for merge replication (which is my case) ,they are suggesting Web Synchronization if no domain was present ,which is even much harder to configure.

|||

Good Morning (its morning here)!
FINALLY I DID IT!...ITS WORKING NOW..>WOWWWWWWWWW..
well after cleaning up the whole mess and starting over from scratch ,i figured out the following mistake:
i made TWO Aliases on the publisher one for the publisher itself and the other for the subscriber ,the publisher Alias was causing the connection to fail when initializing the snapshot ,thats why i got the error message ,although i could connect to my own machine using that alias ,which make things strange ,but it was causing connection problems with the agent.

|||

Hi

Can you describe your setup a bit more in details, I'm having the exact same problem.

I get no errors other than the Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON error.

The two servers seem to connect just fine, and I can connect to them from sql server managemen studio just fine. But the Snapshot is not created.

On the subscriber machine the only indication that its not working is a message that the replication could not finish because no snapshot exists.

|||

ali_khankan wrote:

Good Morning (its morning here)!
FINALLY I DID IT!...ITS WORKING NOW..>WOWWWWWWWWW..
well after cleaning up the whole mess and starting over from scratch ,i figured out the following mistake:
i made TWO Aliases on the publisher one for the publisher itself and the other for the subscriber ,the publisher Alias was causing the connection to fail when initializing the snapshot ,thats why i got the error message ,although i could connect to my own machine using that alias ,which make things strange ,but it was causing connection problems with the agent.

that's a good news.

to sparrez just make sure that the sql server agent service is running on an account that have access to the replication folder.

usually it is a network share.

you can check it in the publication properties-snapshot location

|||

Why does it need to be a network share ? The publishing machine is isolated and not part of a "network", with shares, so to speak. Why won't the default folder be ok?

Also the two servers are in completely different locations so the replication must occur over the internet. With the subscribing machine actually beeing a Domain Controller, but the publishing not beeing a member of a domain a all.

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON

Hello Guys,

I have two machines that i want to use for merge replication :

Laptop ( Publisher + Distributor )

VPS90 ( Subscriber )

Both connected via the internet

NO DOMAIN

Need to implement merge replication ,after initializing the snapshot I get the following error on both machines :

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 192.168.1.1]

I created a new user "Repuser" (admin)with the same password on both machines and configured the Agent proccess to run under that account ,now i get this error :

Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.1]

Please note that :

· Mixed mode authentication IS ENABLED ON BOTH MACHINES

· BOTH MACHINES CAN PING AND ACCESS EACH OTHER ,BOTH COMPLEETELY VISIBLE.

· CONFIGURED ALIASES ON BOTH MACHINES.

· Both configured to use Sa account .

* I have NO DOMAIN

what does this mean?

It simply means that the SQL Server Agent process account is the one that’s being authenticated to connect to the other machine and NOT the Sa account ,WHY?

do i have to use Web Synch in my case?

hi,

replication uses the sql server agent services

your sql services should be running on an account that has

access to replication resources such as the snapshot folder or the replication folder.

the sql server services should be able to access both machine

regards,

joey

|||how can i make the SQL Server Agent account access the other machine ? supposing that i have no domain? please clarify|||Hello?!! Any 1 there?!|||

how are the machine connected in the internet anyway?

are the IPs exposed over the web? Are you using VPN's?

192.168.1.1 seems to be a local IP

anyway...

I think it is not possible to do replication without domain

maybe some other solution would be better in the scenario

like

the SQL SERVER integration services (SSIS)

|||

thanks for the reply joeydj

both machines are exposed to the internet openely ,no VPNs ,first 1 with a static IP (in USA) and the other is via a DSL modem via NAT (thats y u saw 192.168.1.1) ,they can both connect to each other via SQL server Management Studio with out any problems ,i think microsoft made it nearly impossible to do anything with out Domain ,which is really stupid ,as for merge replication (which is my case) ,they are suggesting Web Synchronization if no domain was present ,which is even much harder to configure.

|||

Good Morning (its morning here)!
FINALLY I DID IT!...ITS WORKING NOW..>WOWWWWWWWWW..
well after cleaning up the whole mess and starting over from scratch ,i figured out the following mistake:
i made TWO Aliases on the publisher one for the publisher itself and the other for the subscriber ,the publisher Alias was causing the connection to fail when initializing the snapshot ,thats why i got the error message ,although i could connect to my own machine using that alias ,which make things strange ,but it was causing connection problems with the agent.

|||

Hi

Can you describe your setup a bit more in details, I'm having the exact same problem.

I get no errors other than the Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON error.

The two servers seem to connect just fine, and I can connect to them from sql server managemen studio just fine. But the Snapshot is not created.

On the subscriber machine the only indication that its not working is a message that the replication could not finish because no snapshot exists.

|||

ali_khankan wrote:

Good Morning (its morning here)!
FINALLY I DID IT!...ITS WORKING NOW..>WOWWWWWWWWW..
well after cleaning up the whole mess and starting over from scratch ,i figured out the following mistake:
i made TWO Aliases on the publisher one for the publisher itself and the other for the subscriber ,the publisher Alias was causing the connection to fail when initializing the snapshot ,thats why i got the error message ,although i could connect to my own machine using that alias ,which make things strange ,but it was causing connection problems with the agent.

that's a good news.

to sparrez just make sure that the sql server agent service is running on an account that have access to the replication folder.

usually it is a network share.

you can check it in the publication properties-snapshot location

|||

Why does it need to be a network share ? The publishing machine is isolated and not part of a "network", with shares, so to speak. Why won't the default folder be ok?

Also the two servers are in completely different locations so the replication must occur over the internet. With the subscribing machine actually beeing a Domain Controller, but the publishing not beeing a member of a domain a all.

Login failed for user 'NT Authority\Anonymous

I have a Merge Replication configuration in which one Publisher replicates
with 20 subscribers.
Currently, we use Windows Integrated security.
I get the following error when attempting to access tables in a remote
server from the publisher.
In Query Analyzer window, logged into publisher, I type
SELECT * FROM <subscriber1>.<databasename>..<tablename>
And get the following error message:
Login failed for user 'NTAUTHORITY\ANONYMOUS LOGON'
1) From everything I’ve read, including article 827422, it is necessary to
go to Mixed Security in order to overcome this security issue. Is this true?
2) Will changing the security mode on the Publisher and all 20 subscribers
cause any problems with replication?1) That's a major over-generalization to say that changing it to SQL
Authentication (Mixed Mode) will allow you to over come this. It's working
around the issue entirely. You will still have issues with Windows
authentication, and should deal with those.
When you set up the merge subscribers, are they anonymous? Did you specify
for the merge agent to connect to the subscriber (if push) or publisher (if
pull) under the credentials of the SQL Agent account? What is that account?
Can you log onto each server (pub and sub) as their respective SQL Agent
accounts, then try to open Query Analyzer and point to the other server usin
g
windows authentication? Do you get the same "Anonymous error"? Are they th
e
same account? If not, are they in the same domain? Make sure they both have
the correct rights to each other's machine. If not in the same domain, you
need to look at trust issues. If there is no trust, then you will either
have to set one up, or use mixed mode and SQL accounts.
2) No, unless you consider the time to restart SQL an issue.
Donna Lambert
"elpepe" wrote:

> I have a Merge Replication configuration in which one Publisher replicates
> with 20 subscribers.
> Currently, we use Windows Integrated security.
> I get the following error when attempting to access tables in a remote
> server from the publisher.
> In Query Analyzer window, logged into publisher, I type
> SELECT * FROM <subscriber1>.<databasename>..<tablename>
> And get the following error message:
> Login failed for user 'NTAUTHORITY\ANONYMOUS LOGON'
> 1) From everything I’ve read, including article 827422, it is necessary
to
> go to Mixed Security in order to overcome this security issue. Is this tru
e?
> 2) Will changing the security mode on the Publisher and all 20 subscribers
> cause any problems with replication?
>
>

Login failed

I have a network based on Win 2000 advanced server, and my database is SQL Server 6.5 using replication from a publisher to subscribers. Recently I have changed all "sa" passwords, which were the same on all servers, and after this only change the Replication of data is not working anymore.
I have this error:
28000[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed
How do I fix that?
I need some help about.

Regards,Is the error for the log reader, the distribution agent, or both?

-PatP|||Hi,
The log reader is working properly. The error is from distribution task

ie SERVER1..BD1 -- Replication --> SERVER2..BD2

taskname: SERVER1_BD1_SERVER2_BD2|||See sp_changesubscriber (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_repl_4kaa.asp) for details.

-PatP|||See this KBA http://support.microsoft.com/default.aspx?scid=kb;EN-US;216848 is any help.

Login failed

I keep getting this error in the Queue Reader
How can I set the way the Publisher logs into the subsriber (push
subsription)?
Thank you,
Samuel
Samuel, I suggest you open a support incident with Microsoft on this one.
Its difficult to determine exactly what your problem is.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:esrZY1a4GHA.3964@.TK2MSFTNGP04.phx.gbl...
>I keep getting this error in the Queue Reader
> How can I set the way the Publisher logs into the subsriber (push
> subsription)?
> Thank you,
> Samuel
>