by matt
25. March 2009 10:07
I'm still fairly new to EPiServer, so I'm going through the process of a great many rookie errors whilst taking over a site from someone with vastly more knowledge of the product than me.
One issue I had recently was when I was creating a new stage server for a client so that they could test things out. I went through a cobbled route of copying their live DB and live code and slapping them on to of a clean EPiServer install and hacking about in the web.config file to get it all working. The in itself was a piece of cake.
I started getting problems when the AD users could not connect tot he site. I checked and rechecked the LDAP settings in the web.config and they were all correct. After a quick look on EPiServer World, I found an FAQ explaining the problem, though I could not manage to get the workarounds to provide the goods.
The problem is not caused by EPiServer, it is how the .Net framework deals with AD when it is not connected to the domain. Now that I knew a little more about what the cause of the problem might be, I hit Google to try and find a resolution. Eventually a came across this forum entry which gave a possible solution. The long story short is that bay changing the Local Policy on the server and rebooting.
To make the change, follow the steps below:
- Go to 'Local Security Policy' on the server through the Administrative Tools.
- Expand 'Local Policies' and then click on 'Security Options' to see the list of security policies.
- Select the 'Interactive Logon: Number of previous logons to cache' policy.
- In the properties, set the cache value to 0.
This stops the OS for caching user details between logins, forcing the server to connect to the domain. After quick reboot, this fixes the problem.
Related Links
http://world.episerver.com/en/FAQ/Items/The-trust-relationship-between-the-primary-domain-and-the-trusted-domain-failed/
http://www.techsupportforum.com/microsoft-support/windows-nt-2000-2003-server-2008-server/169618-disconnecting-domain.html
Subscribe