If you were Registered and logged in, you could reply and use other advanced thread options
|
Posted by McDavid on May 26, 2009, 1:28 pm
Environment:
- Terminal Server
- Windows 2008 x64 Server Standard
- Kerberos Token Size set to maximum
- Profile and Folder Redirection hosts
- Windows 2003 x64 Server Standard
- Kerberos Token Size set to maximum
Issue:
When our users logon to our Terminal Servers using kerberos, they receive a
temporary profile and none of the Folder Redirection policies are applied.
The event log reports both processing failing with "Logon failure: unknown
user name or bad password.". However the user is successfully logged onto
the server using kerberos. The server hosting the profiles also reports
"unknown user name or bad password" in the security log and the
authentication package as NTLM. The users can navigate to the network
locations of their roaming profiles and redirected folders just fine without
any errors.
If the users logon to our Terminal Servers using NTLM, their roaming profile
is loaded and folder redirection policies applied successfully.
Kerberos is the required authentication method for logging into our Terminal
Servers. We are using Citrix Web Interface and single signon leverages
kerberos.
Initial Troubleshooting:
I turned on Kerberos logging on the Terminal Server. When the user logs into
the Terminal Server using kerberos, the logon process attempts to load their
profile and redirect their profiles using kerberos. This is failing because
we don't have SPNs registered for these resources. I'm guessing the logon
process then attempts NTLM and that is failing because they didn't login with
NTLM.
Is there any way to get the fallback to NTLM to function? If not, how does
one go about registering SPNs for file-shares that are cluster resources
(virtual IPs and computer names that aren't regisered in Active Directory).
In addition, how does one go about registering SPNs for DFS roots?
Any/all help is appreciated.
Thanks.
|
|
Posted by McDavid on May 27, 2009, 11:46 am
Found that we don't have kerberos enabled on our clustered file shares.
Would still like to know if there is a way to have the logon process revert
to NTLM if kerberos authentication fails (because the user logged onto the
Terminal Server with kerberos and the file share doesn't currently support
kerberos).
"McDavid" wrote:
> Environment:
> - Terminal Server
> - Windows 2008 x64 Server Standard
> - Kerberos Token Size set to maximum
> - Profile and Folder Redirection hosts
> - Windows 2003 x64 Server Standard
> - Kerberos Token Size set to maximum
>
> Issue:
> When our users logon to our Terminal Servers using kerberos, they receive a
> temporary profile and none of the Folder Redirection policies are applied.
> The event log reports both processing failing with "Logon failure: unknown
> user name or bad password.". However the user is successfully logged onto
> the server using kerberos. The server hosting the profiles also reports
> "unknown user name or bad password" in the security log and the
> authentication package as NTLM. The users can navigate to the network
> locations of their roaming profiles and redirected folders just fine without
> any errors.
>
> If the users logon to our Terminal Servers using NTLM, their roaming profile
> is loaded and folder redirection policies applied successfully.
>
> Kerberos is the required authentication method for logging into our Terminal
> Servers. We are using Citrix Web Interface and single signon leverages
> kerberos.
>
> Initial Troubleshooting:
> I turned on Kerberos logging on the Terminal Server. When the user logs into
> the Terminal Server using kerberos, the logon process attempts to load their
> profile and redirect their profiles using kerberos. This is failing because
> we don't have SPNs registered for these resources. I'm guessing the logon
> process then attempts NTLM and that is failing because they didn't login with
> NTLM.
>
> Is there any way to get the fallback to NTLM to function? If not, how does
> one go about registering SPNs for file-shares that are cluster resources
> (virtual IPs and computer names that aren't regisered in Active Directory).
> In addition, how does one go about registering SPNs for DFS roots?
>
> Any/all help is appreciated.
>
> Thanks.
>
|
|
Posted by Anthony [MVP] on May 27, 2009, 1:46 pm
McDavid,
I am not an expert in Kerberos, so you may get a more expert answer from
someone else, but:
- we run Citrix with Web Interface and single sign-on, and you don't need to
do anything special to do it.
- when you sign on to the WI server, it authenticates you to other servers
in the farm: I don't think this is AD Kerberos, although it is
Kerberos-like. You get a ticket from a Citrix Secure Ticket Authority (STA)
and present this to other servers in the farm
- I suspect the problem lies with the cluster resources and delegated
authentication. What cluster is this?
- You can use the SetSPN utility to create additional SPN's:
http://technet.microsoft.com/en-us/library/cc773257.aspx
Hope that helps,
Anthony
http://www.airdesk.com
> Environment:
> - Terminal Server
> - Windows 2008 x64 Server Standard
> - Kerberos Token Size set to maximum
> - Profile and Folder Redirection hosts
> - Windows 2003 x64 Server Standard
> - Kerberos Token Size set to maximum
> Issue:
> When our users logon to our Terminal Servers using kerberos, they receive
> a
> temporary profile and none of the Folder Redirection policies are applied.
> The event log reports both processing failing with "Logon failure:
> unknown
> user name or bad password.". However the user is successfully logged onto
> the server using kerberos. The server hosting the profiles also reports
> "unknown user name or bad password" in the security log and the
> authentication package as NTLM. The users can navigate to the network
> locations of their roaming profiles and redirected folders just fine
> without
> any errors.
> If the users logon to our Terminal Servers using NTLM, their roaming
> profile
> is loaded and folder redirection policies applied successfully.
> Kerberos is the required authentication method for logging into our
> Terminal
> Servers. We are using Citrix Web Interface and single signon leverages
> kerberos.
> Initial Troubleshooting:
> I turned on Kerberos logging on the Terminal Server. When the user logs
> into
> the Terminal Server using kerberos, the logon process attempts to load
> their
> profile and redirect their profiles using kerberos. This is failing
> because
> we don't have SPNs registered for these resources. I'm guessing the logon
> process then attempts NTLM and that is failing because they didn't login
> with
> NTLM.
> Is there any way to get the fallback to NTLM to function? If not, how
> does
> one go about registering SPNs for file-shares that are cluster resources
> (virtual IPs and computer names that aren't regisered in Active
> Directory).
> In addition, how does one go about registering SPNs for DFS roots?
> Any/all help is appreciated.
> Thanks.
>
|
|
Posted by McDavid on May 27, 2009, 2:53 pm
Kerberos (and possibly ADFS) is the only supported single sign-on protocol
when authenticating to a Web Interface (or PN Agent site) from a XenApp
Server. I believe the XenApp Client readme states this limitation. When
running the XenApp client from a XenApp server, the ssonsvr.exe process is
not available to perform the sign-on.
Kerberos authentication is working fine for us to the Web Interface server.
And the Web Interface is passing kerberos just fine, logging the users into
the Terminal Servers. The logon process is attempting to use kerberos to
load the roaming profile and perform folder redirection. That is failing
because we have kerberos disabled on the cluster resources. I'm going to
enable kerberos on the cluster resources during our next maintenance window.
However, I would still like to figure out an interim solution. Is there a
way to force the logon process to use NTLM even though the user logged on
with kerberos?
Our file shares are hosted on a Windows 2003 x64 cluster.
"Anthony [MVP]" wrote:
|
|
Posted by Anthony [MVP] on May 29, 2009, 3:33 am
I have been puzzling over this.
As you say, you can enable Kerberos authentication on the cluster:
http://support.microsoft.com/kb/302389
But I am curious what it is about the logon process that makes the profile
load fail.
As you are already aware, there are numerous authentication processes in
Citrix. Can you tell us how people authenticate initially from their client
to the Web Interface? Are you using Pass-through authentication with
Kerberos enabled?
Anthony
http://www.airdesk.com
|
If you were Registered and logged in, you could reply and use other advanced thread options
Related Posts
Latest Posts
|
XML Sitemap
> - Terminal Server
> - Windows 2008 x64 Server Standard
> - Kerberos Token Size set to maximum
> - Profile and Folder Redirection hosts
> - Windows 2003 x64 Server Standard
> - Kerberos Token Size set to maximum
>
> Issue:
> When our users logon to our Terminal Servers using kerberos, they receive a
> temporary profile and none of the Folder Redirection policies are applied.
> The event log reports both processing failing with "Logon failure: unknown
> user name or bad password.". However the user is successfully logged onto
> the server using kerberos. The server hosting the profiles also reports
> "unknown user name or bad password" in the security log and the
> authentication package as NTLM. The users can navigate to the network
> locations of their roaming profiles and redirected folders just fine without
> any errors.
>
> If the users logon to our Terminal Servers using NTLM, their roaming profile
> is loaded and folder redirection policies applied successfully.
>
> Kerberos is the required authentication method for logging into our Terminal
> Servers. We are using Citrix Web Interface and single signon leverages
> kerberos.
>
> Initial Troubleshooting:
> I turned on Kerberos logging on the Terminal Server. When the user logs into
> the Terminal Server using kerberos, the logon process attempts to load their
> profile and redirect their profiles using kerberos. This is failing because
> we don't have SPNs registered for these resources. I'm guessing the logon
> process then attempts NTLM and that is failing because they didn't login with
> NTLM.
>
> Is there any way to get the fallback to NTLM to function? If not, how does
> one go about registering SPNs for file-shares that are cluster resources
> (virtual IPs and computer names that aren't regisered in Active Directory).
> In addition, how does one go about registering SPNs for DFS roots?
>
> Any/all help is appreciated.
>
> Thanks.
>