Problem with Auto Authentication
Created: 09 May 2012 | 11 comments
Hello!
I am having problems with the auto autenthication in external systems, the auto authentication with AD in the servicedesk SERVER works, but in anothers PC's in the domain doesn't work.
i am following this How To ----> http://www.symantec.com/business/support/index?pag...
Discussion Filed Under:
Comments 11 Comments • Jump to latest comment
On the server works means with different user IDs signing on to the server?
yes, with diferent user IDs, in the Servicedesk SERVER the Automatic authentication with AD credentials works perfectly.
But if i want to sign in the servicedesk with another computer, the automatic authentication doesn't work.
Hi
Verific when you open the adress of Service Desk if in the right corner on Internet Explorer see "Local Intranet" , if you see "Internet Zone" you need add page to Intranet Zone
Jorge Fernandez
yes, I see "local intranet" in the right corner, the configuration in the IE options its ok, the page in intranet sites and local intranet authentication.
Have you tried to bounce that site in to trusted. I know I had problems on computers where cookies were disabled. Might want to check in the internet settings, on the advanced tab, to make sure "Enable Integrated Windows Authentcation" is checked and in the Security Settings for the zone (trusted/local) that under User Authentication - Automatic login with current user name and password is selected..
Hi!
I've tried that configuration Jamie, and doesn't work, can you give me another advice? :(
Just throwing things out there (and I cannot remember if you are using SP2 or not)... Sounds like someone has an outstanding case on it.
One thing I had was my user table was getting poop in it because of a check box. The AD field was screwed up (at one time) and then it moved from that field to the first name field (where it prefixed our domain name)
I think it was Convert Native Users to Active Directory User was checked off and some of my fields were done akwardly with the update. I think they fixed this in a roll up.
I have SDK 7.1 SP1 no SP2... in SP2 works well ?.
I need a solution with SDK 7.1 SP1 :(
Sorry I could not help out more.
A recent client has a support case to address this - still unresolved...
could you find a solution ?
i'm in trouble now :(
Would you like to reply?
Login or Register to post your comment.