Windows 10: IIS: autologon from current domain user work on name but on IP

Then I try to access my intranet website hosted on IIS server via name : http://mywebsite I am automatically logged on with my current user Domain. That's what I want!If I try to access the website through IP :http://123.12.1.100 I receive a login request.If I save the login in my browser, the login is asked everytime and autofilled by the browser.After that, I have tried to add an entry in the Windows Identification Information using "mywebsite" not the IP. After that, there is no popup anymore.Why? How can I make it work through IP the same way as through name?Thanks in advance for your re

:)

 

Configure IIS under different Domain user than the current logged in User domain

Hi Sarah,

Thanks for the suggestion. The issue with ADFS is that we are a services company and domain which we want to use for IIS configuration is of one our client. We cant create a ADFS to include both our company users and client credentials.

 

Configure IIS under different Domain user than the current logged in User domain

The issue is that we cant change the application to accept new Domain and its user. Client will use its application how it is currently accepting its own Windows Authentication. That is why we are trying to figure out if we can do this configuration inside
IIS.

Also is it possible to run IIS using 'runas' command with different domain, like we can do that for SQL server.

 

AutoLogon not working in domain environment

I have a strange problem with AutoLogon in our domain environment:

we have several machines that are configured for autologon, where the registry entries DefaultUsername, DefaultPassword, DefaultDomainName are all verified as having the correct data, and AutoAdminLogon is set to a value of '1'....

...but the machine does not autologon to that account, but instead shows the LOCK SCREEN for the account, and it is asking for email address instead of username, like it is not in a domain environment.

This occurs whether we run the Autologon.exe application, or manually configure the registry.

My guess is there is something else amiss, like a security setting, because everything I am reading says autologon itself is configured properly.

Has anyone experienced this? Do you know where I should start looking?

----------------------------------------------
Windows 10 Enterprise, build 1709