Authenticate Three Tiers without AD

David_Singleton

I am playing with a test environment, which is basically just three machines, one with SQL, one NST and the third with RTC. There is no domain or AD, its just three machines connected to a router.

Is there a simple way to get them to talk together without a domain?

DenSter

Have you tried identical local Windows users?

David_Singleton

DenSter wrote:

Have you tried identical local Windows users?

Thanks, yes I tried that, but it needs the full name \\<computername>\<username> and you can't use the same name on different machines.

Also I am trying to do this "out of the box" so to speak, just using what comes with the NAV 2013 installer, no going in the SQL back end or user aliasing etc. Just to basically set up a really simple procedure to set up a multi machine demo system.

I could just throw an Domain controller in there, but I want to see how to do it without that to get a better picture of exactly what is going on with Authentication.

David_Singleton

DenSter wrote:

Have you tried identical local Windows users?

Oh and that works fine for the Object Designer, just not for the Nav Server.

ara3n

I haven't tried it myself but remembered the following two blogs.

http://blogs.msdn.com/b/nav/archive/201 ... ctory.aspx



http://blogs.msdn.com/b/freddyk/archive ... t-a-d.aspx

David_Singleton

ara3n wrote:

I haven't tried it myself but remembered the following two blogs.

http://blogs.msdn.com/b/freddyk/archive ... t-a-d.aspx

Thanks for the links. Unfortunately as Freddy says:

FreddyDK wrote:

I did not try to install the database tier separate from the Service Tier, as I do not think it is relevant in a scenario like this.

But this is specifically what I need to do. Basically I just want one machine with ONLY SQL. I want to work out how all this authentication works with just one user logging from NST to SQL. AD just adds a another layer to clutter things up.

David_Singleton

I guess once I get it all sorted out it will make for an interesting blog.

DenSter

David Singleton wrote:

DenSter wrote:

Have you tried identical local Windows users?

Oh and that works fine for the Object Designer, just not for the Nav Server.

Maybe the <machine name> part in <machine name>\<user name> screws local users up when you want to implement in a multiple machine environment. Local Windows users does work when you have all components on the same box, including NAV Server.

David_Singleton

DenSter wrote:

Local Windows users does work when you have all components on the same box, including NAV Server.

Yes that works fine, the issue now is getting the NST and SQL on separate machines. Also I am trying to do this without SSMS, I want to see if it can all be done just using Navision and Win7.

Thanks for the input, please keep the ideas coming.

stomdahl

You could try to use credentials manager, [Control Panel\User Accounts\Credential Manager]
to configure how NST communiates with SQL machine.

And regarding user authentication, you should use "ClientServicesCredentialType" = "NavUserPassword", where all user are stored in the NAV database.

Thanks,
Stefan

David_Singleton

stomdahl wrote:

You could try to use credentials manager, [Control Panel\User Accounts\Credential Manager]
to configure how NST communiates with SQL machine.

Thanks,
Stefan

Thanks Stefan, this looks like the right starting point, as I can now connect with the Classic Client (Developer) to the SQL server using windows login. But still I can't get the NST to use this login, it is still trying to authenticate to SQL as 'NT AUTHORITY\ANONYMOUS LOGON' giving me the message (in event viewer)

Message: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

I tried in NAV Administration tool to set the login user as the alias but it wontlet me save that because the user does not exist.

But I think you have me on the right track.

David_Singleton

OK looks like I am close, I set the SQL login to be the user on the NST machine, and the alias is now working by mapping that login to the login on the SQL machine.

The message I am getting now is a standard

---

Microsoft Dynamics NAV

---

The license information on the Microsoft Dynamics NAV Database Server is invalid.

---

OK

---

Which makes sense since that SQL server has a Nav 2009 license, so I am certain that it is now hitting and authenticating correctly.

\:D/ \:D/ \:D/ \:D/ \:D/ \:D/

Thank You Stefan.