Admin user provisioning throws: The remote name could not be resolved

(0) Share

Report

Posted on by Community Member

Hi -

I have configured a VM for D365FO in my laptop using VMWare Player 12. Of late, the application is not working, unable to browse from IE, IIS. Even can't debug/run from VS. when i try to re-provision (Admin user provisioning), a error window prompts as:

"The remote name could not be resolved: "login.windows.net".

The event log records the same error as

"An error occurred while sending the request.

The remote name could not be resolved: 'login.windows.net'
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)

etc etc"

Basically, the URL redirection for authentication is not working when I browse the D365FO site .

I did try and the same with a fresh environment, no customization, still have the same issue.

Has anyone encountered the same issue and advice on the same.

Thank you.

Dip

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Martin Dráb 237,878 Most Valuable Professional on at

Like (0)

Report

Are you connected to internet? Does DNS resolution work correctly?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Martin - My VM is connected to internet sharing the guest network and able to browse sites normally. Ping to the remote name 'login.windows.net' results differently in guest OS and hosted VM -

Rgds,

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Further, https://login.windows.net - unable to browse from VM whereas it can be browse from host machine.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Well - absolutely no issues with the application but not sure why the guest system is not able to browse the url for identity authentication. Even I was unable to browse LifeCycle/Azure wherever this portal " https://login.windows.net" is used for authentication.

At end, i tried to login using my phone's 4G connection, it worked and able to browse all sites. Later, i stop/start the home router - looks fine so far.

I will still appreciate a root cause for such issues from others.

Was this reply helpful? Yes No