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.