client Can't use domain name to worksapce but use ip can

Was this installed using the "Server Farm" option or the "Stand Alone" option?

 The "Server Farm" option requires the use of Kerberos internally.

You might also want to run the K2 Host Server in console mode and check what authentication method you are connecting as.

Hi jonhny,

   The console show : Authenticating  domainuserid for session .... using k2 - NTLM 

     use "Small Scale Install"

     BPSp1 + Workspace + reporting service in one pc

     MSSQL 20035  in one pc

   tks 

That would seem strange.  Are you saying the from the Console it shows the correct user (connected via NTLM) if you use the IP address?

 What happens if you use the server name?

when use ip,form the console can see

The console show : Authenticating  domainuserid for session .... using k2 - NTLM

but use domain name will alert the user/password window to key in,but can't login correct

Thanks

Have you added the site url to trusted zones and also configured the zone settings to "Automatic Logon with current user name and password"?

The only other thing I can think of is to force your workspace site to use NTLM.

From c:inetpubadminscripts, run the following command.

cscript adsutil.vbs set w3sv3/<site id>/NTAuthenticationProviders "NTLM"

I would also suggest logging a support ticket if you can to get a K2 support person to assists you.

johnny,

tks 

I had do Cscript adsutil.vbs set w3svc/xxxx/NTAuthenticationProviders “Negotiate,NTLM”

after do this , ip can see but domain still can't

after to reinstall version blackpearl 803 

run cscript adsutil.vbs set w3svc/xxx/NTAuthenticationProviders "NTLM"

Client browser can use domain name to see workspace

is it different from “Negotiate,NTLM”

johnny, tks much

Glad to hear that it works.

The "NTLM" value forces IIS to use NTLM protocol for the IIS authentication.

If you set it to "Negotiate,NTLM" it uses Kerberos first and then tries NTLM if Kerberos is not supported.