Cannot access Windows Client with Windows authentication

[tboudrez]

When I run the following script and enter my windows username and password only the web client works. I can see in the web client that it opens with Windows user NAV2018WIN\TIMOTHY.

However the Windows client isn't able to connect. It tries to connect to NAV2018Win:7046/NAV and gives a connection error.

New-CSideDevContainer -containerName 'NAV2018Win'
-imageName microsoft/dynamics-nav:2018 -licenseFile 'C:\mylicense.flf'
-memoryLimit 4G -updateHosts
-accept_eula `
-Verbose

[freddydk]

When you ping nav2018win on the host, what happens?

[tboudrez]

I get replies when I ping nav2018win

[freddydk]

And it resolves to the IP number of the container?
Strange.
What kind of machine is this?
Azure VM?
Local?
Could you share Docker logs and docker inspect?

Thanks

[Koubek]

@tboudrez You can obtain required information using Get-NavContainerDebugInfo -containerName NAV2018Win -CopyToClipboard but you need to update navcontainerhelper (this function has been published right today).

[martonsagi]

Hi, I have the same issue here.
Actually, I have two NAV containers installed and none of them seem to have Port 7046 opened.
My locally installed other NAV instances are running on different ports but stopped all of them just to be sure.

Status:

• Web Client: OK
• Web Services: Port 7047, 7048 OK
• RTC: Cannot connect
• CSide: no luck with windows auth., but it works with sa / my windows password
• Command/PowerShell prompt: OK

Environment:

• Physical machine (Lenovo T420)
• Windows 10 Enterprise
• Docker: 17.09.1-ce-win42 (14687)
• Navcontainerhelper: 0.2.2.0 (just updated today)

Containers:

• microsoft/dynamics-nav:latest
• microsoft/dynamics-nav:2017-cu13

Commands used for creation:

New-NavContainer 
-accept_eula 
-containerName NAV2018-W1-RTM 
-imageName microsoft/dynamics-nav:latest 
-licenseFile "E:\NAV\Install\NAV 2018\NAV2018_dev.flf" 
-memoryLimit 3G 
-updateHosts 
-includeCSide 
-doNotExportObjectsToText 
-Verbose

New-NavContainer 
-accept_eula 
-containerName NAV2017-W1-CU13
-imageName microsoft/dynamics-nav:2017-cu13
-memoryLimit 3G 
-includeCSide 
-doNotExportObjectsToText 
-Verbose

Get-NavContainerDebugInfo:

• Docker info for NAV2018-W1-RTM
• Docker info for NAV2017-W1-CU13

This was my first try with Docker, so I'm open for any suggestions. Thanks!

[elweilando]

matches your password the default password complexity requirements?

[martonsagi]

Yes, it does meet the default requirements.

[Koubek]

@martonsagi Please, could you try to download this folder (or the whole project but then use the folder) and run NAV on Docker using this example.
https://github.com/Koubek/nav-docker-examples/tree/master/local_cside

[martonsagi]

@Koubek

Thanks, I gave it a try. Container was created but could not be started:

PS E:\VSCode\nav-docker-examples-master\local_cside> .\run.ps1
Input the user`s password: ---
Initializing...
AuthorizationManager check failed.

I could not let it go and I have found this related issue: #34. I also happen to have a Microsoft Online account tied to my PC, so I guess that's the main issue in my case as well.
A newly created container with NavUserPassword works almost fine, except for the C/Side Management Port.

Still, I find it extremely impressive! Thanks for your great work, guys.

[Koubek]

@martonsagi Hi, if you want, you can contact me via email (my e-mail address can be found on the profile). We can check it together using AnyDesk (or TeamViewer but I prefer AnyDesk).

[Koubek]

@freddydk Do you have any idea why in a standard example that works everywhere occurs the same error AuthorizationManager check failed like in #132? There is no DVD here in this case (I suppose :)).

[Koubek]

@martonsagi Please, could you check the following link?
http://tgnp.me/2011/09/powershell-authorizationmanager-check-failed-resolution/

I am not sure how it could be exactly related in this particular case to the example you were trying but the error message is the same (at least when you were trying one of my nav-docker-examples.

[freddydk]

No idea, sorry
I full day meetings yesterday and today - will look at this tonight/tomorrow

[Koubek]

Me the same, since yesterday I haven't stopped yet so I am just watching issues in between other tasks.

[martonsagi]

Thanks for the suggestions! I'm full for today as well but I'll try it out some time tomorrow.

[martonsagi]

@Koubek
Thanks, IE has indeed blocked some PS files, hence the AuthorizationManager error.
I was able to try your "local_cside" example and I got the very same result as in my first comment.

[srideout2525]

I was running into the same issue, unable to access windows client. I had local version installed. I uninstalled the local version and now I am able to access.

[freddydk]

Was this issue resolved?

[srideout2525]

It was only solved for me by uninstalling my local version of 2018.

[freddydk]

Ok, thanks.
That is probably just something we have to accept.