- Kerberos SharePoint CRM List Web Part problem
- Posted by Ross Gardner on September 7th, 2006
It took a lot of time, but after following the instructions in the CRM List
Web Part readme, I was able to get the web part working. Well, almost...
The SharePoint server is on a separate server than the CRM server. There
are two ways to get to our SharePoint site. One way is to use http://servername.
The web part works correctly using this URL, presumably because it is using
Kerberos. However, the most common way we use to access SharePoint is by
using a DNS entry http://portal that goes to the same IP address and virtual
server. But the web part is not working when we access SharePoint this way.
I used a packet sniffer and found that it was using NTLM.
Why would http://servername work with Kerberos and a DNS entry pointing to
the same IP address not work
- Posted by dtu11 on September 7th, 2006
More than likely your Kerberos ticket is referencing http://portal and there
isn't a SPN setup to allow that server to pass the credentials. By default I
think there is already a SPN for the HOST/SERVERNAME and the HTTP protocol
will default to that.
I would start by downloading KerbTray to show you which Kerberos ticket it
is requesting and then create the additional setup needed for the server to
pass the credentials when you have a DNS name.
You can reference this document to help you out. I know it's specific for
Reporting Services but it gives you details on what needs to be created and
where you can start.
http://www.microsoft.com/downloads/d...displaylang=en.
"Ross Gardner" wrote:
- Installer problem with CRM Web Part List (Windows CRM) by Ulf
- CRM Sharepoint Web Part (Windows CRM) by kmyers@sdasolutions.com
- Sharepoint CRM Web Part (Windows CRM) by kmyers@sdasolutions.com
- CRM List Web Part, CRM Reporting and Sharepoint deployment questio (Windows CRM) by Steve Ware
- List web part not working for Sharepoint "Invalid CRM Server" mess (Windows CRM) by RickNavarro

