Windows Authentication component broke???

[Anonymous]

Hi all,

About two months ago, We upgraded our vault manufacturing 2010 to Vault professional 2011/SP1 and SP2.

And windows Authenticaiton works just fine. Up until last week users can no longer logon to vault using vault server by name. it worked if we use the server's IP ADDRESS along windows Authentication option.

I dont think this is a DNS issue. Because we can use vault local account to logon to vault server regardless we are using vault server by name or by IP Address.

Please help.

Thank you in advance.

[herrerh]

What error do you get when trying to login via Windows Authentication and the computer name?

Can you post the vlog from the server?

[Anonymous]

Attached are the vlogs. Also attached an error message when we logged on to vault server using server name. Successful with IP address.

Best regards,

[Anonymous]

Did you find a solution for this?  I'm having the same issue.  Windows Authentication was working, but after Vault 2012 Pro Update 1 was applied, logins aren't working.

[Anonymous]

Still broken!  Extremely frustrating.  Our consultants and Autodesk say they've never seen this before.

[r.smith1 · Accepted solution]

HI Jeff,

As per our discussion today regarding your support case, we had you remove IIS, reinstall IIS and added in Roles:

Security

set basics authentication IIS Client Certificate mapping
Management Tools
IIS management scripts
IIS 6 management compatibility
IIS6 scripting tools

WinAuth settings in IIS, enabled Windows Authentication, disabled asp.net Impersonation.
Made sure default apppool regular time interval is set to suggested numbers per WinAuth White Paper (17400).

Stopped IIS. [using command iiisreset /stop]
Deleted the folder:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\autodeskdm_services

Started IIS. [using command iiisreset /start]

Once all was added, WinAuth started functioning again.

Feel free to reply and add the screen shots taken fro others to review.

Please tag this as a solution to resolve this issue.

[Anonymous]

Ron, thanks for all of your help today.  I've taken screenshots of almost all of our configurations for future reference.  Too many to post here, but if someone runs into this issue, perhaps I can help.  Enjoy your weekend!

[r.smith1]

Thanks Jeff, You as well. 

[Anonymous]

Hi Jeff,

I have exactly the same issue at the moment, can you please (!) explain me how you've resolved it ?

It occurs after installation of Upgrade 1 on Vault Pro 2012.

Thanks in advance !!! 

[Anonymous]

Hi,

Issue resolved... after reinstalling IIS, I used IP Adress instead of Server Name and it works !

Hope it helps, and hope that Autodesk is working on a solution !

[herrerh]

If it works via IP address and not the host name then your issue is most likely a network issue. 

If you do a "ping <hostname>" do you get the same IP address?  Check with your IT group for help with this.

[Anonymous]

Thanks for reply.

The "ping" works, with IP address or server name.

[Anonymous]

Hi!

is there a step by step guide for reinstalling the IIS?

I have the same problem after installing sp2 for Vault Pro 2012.

The IIS roles are configured corectly, so I must reinstall the iis.

Thanks.

Fotis

[jweiss1313]

I just upgraded from Vault Server Pro 2013 to 2014.  We applied SP1 after the upgrade and we are unable to login to the Vault Explorer using the server name at our subscriber site in Poland.  We can login using the server IP address.  Can you provide me with detailed instructions on how to fix this issue?  Thanks!

[Anonymous]

Having the same issue here.  Upgrading 2012 Vault AEC to 2014 Pro, SP1.  can login with IP, but not server name.  Can ping both IP and Name.  can you provide step by step instructions to resolve this?

[Anonymous]

One of my customers has a similar problem after updating Vault Pro 2013 RTM to SP1 Update 2.

Vault login works but not Windows authentication. Tried the steps in various cracking the vault articles, but still no success.

Any other help would be appreciated.

Cheers

Dan

[Ezekiel12]

Anyone solved this? Vault 2013 Collaboration - Win Auth worked well but then sudenlly stopped.