Posting here in the desperate hope someone has seen anything like this before.
Have a domain user who's recently been issues with a new Windows 7 laptop. Following his first password change the other day, all manner of weird authentication problems have started.
Firstly, he can log on to the domain without any problems at all and can access the majority of network resources such as file shares, printers and so forth.
What he can't access is the SQL and Exchange servers (both separate servers within the domain). The SQL server produces the classic "Cannot create SSPI context" error whilst the Exchange server (Outlook 2007 client to 2010 server) prompts for his domain password. He can enter the password and it then works but he shouldn't be prompted for it in the first place.
Now it gets really weird. The problem is restricted to W7 clients. I can log on as him on my W7 machine and see the same problem but logging on as him on two different XP machines works flawlessly. Even more nuts - I can change his password and it fixes the issue until the next reboot of the client, then it's back. I've even tried removing and re-adding his account to the relevant security groups on the domain and again, this cures the problem but only until the next reboot.
Has anyone ever seen anything this nuts? Any help appreciated as I'm out of ideas
Have a domain user who's recently been issues with a new Windows 7 laptop. Following his first password change the other day, all manner of weird authentication problems have started.
Firstly, he can log on to the domain without any problems at all and can access the majority of network resources such as file shares, printers and so forth.
What he can't access is the SQL and Exchange servers (both separate servers within the domain). The SQL server produces the classic "Cannot create SSPI context" error whilst the Exchange server (Outlook 2007 client to 2010 server) prompts for his domain password. He can enter the password and it then works but he shouldn't be prompted for it in the first place.
Now it gets really weird. The problem is restricted to W7 clients. I can log on as him on my W7 machine and see the same problem but logging on as him on two different XP machines works flawlessly. Even more nuts - I can change his password and it fixes the issue until the next reboot of the client, then it's back. I've even tried removing and re-adding his account to the relevant security groups on the domain and again, this cures the problem but only until the next reboot.
Has anyone ever seen anything this nuts? Any help appreciated as I'm out of ideas
