Need Assistance in Resoving "NT AUTHORITYANONYMOUS LOGON" issue

  • 26 October 2007
  • 2 replies
  • 0 views

Badge +1

Hello Guys!


I just want to ask for assistance, I was trying to resolve an "NT AUTHORITYANONYMOUS LOGON" issue and luckily found something that might help here: http://kb.k2workflow.com/Articles/KB000123.aspx. But I'm kinda stuck on the part where I need to configure the Workspace web server Address/Host header in the local intranet.


 I have pasted the instruction below:


Include the workspace web server address/host header address to the "Local intranet" zone for the Client Browsers. This setting will log a user in using the current username and password. If not configured this way, "NT AUTHORITYANONYMOUS LOGON" will be displayed as the user name, even though Kerberos is configured correctly To insert the Address / Host Header, do the following from the Internet Browser :



  1. Click "Tools>Internet options"
  2. Click on the Security Tab and then locate the "Local intranet" icon
  3. Click on the button labeled "Sites"
  4. Click on the button labeled "Advanced"
  5. Enter the Workspace web server Addres/Host header in the format e.g. " http://hostheader.domain.com" or "http://workspaceserver.domain.com"
  6. Click "Add"
  7. Click "Ok" to save changes and to exit until you return to the Browser

Does anyone out there familiar of what is the exact "Workspace web server Addres/Host header" that I need to add in the local Intranet?


BTW, I'm using K2.net 2003 SP4. 


Your help will be greatfully appreciated!


Thanks in advance!


-ginoskie


2 replies

Badge +9
The address is completely dependent upon your IIS environment.  Do you know for sure if you are using host headers for workspace?
Badge +6

Given that Kerberos configurations are dependent on systems architectures and settings unique to each environment, I would recommend openinng a support ticket to get assistance with this (the 'post/reply' method of the Underground is not condusive to efficiently addressing most Kerberos configurations).


K2 Support does Kerberos setup/support regularly and can probably get this resolved more efficiently that thru the Underground.


Since you can access the K2 Knowledgebase (your reference to KB123), you should be able to log support tickets as well. 


 

Reply