.NET portal, Active Directory on a sub domain, Windows Authenticat



I run a .NET based portal product. I am using windows authentication. This
mode of authentication and the string specifying the connection to AD is
specified in the application's web.config file. This portal has always worked
fine, though recently, our infrastructure team changed our internal domain
name. Now I can no longer authenticate any users no matter how I change the
connect string in the web.config file.

For the purposes of this discussion my former domain name is 'abc.com' and
my new domain name is '123.abcdefghijklm.com'. The name of the server
housing AD is now 'DC1.123.abcdefghijklm.com'. The netbios name had to be
truncated to 15 characters to accommodate a couple NT4 servers and its new
designation is '123.abcdefghijk'.

The previous connect string in web.config which worked with the old domain
<code><add key="ADdns" value="LDAP://DC1.abc.com/DC=abc, DC=com;

I tried the following to accommodate the name change (domain and netBios):
<code><add key="ADdns"
value="LDAP://DC1.123.abcdefghijklm.com/DC=123.abcdefghijklm, DC=com;

It didn't work. The application generates an error specifying the domain
cannot be contacted.

Can anyone help me with this one?


I figured it out. In this case, the trick is to use only the netbios name
for the ADdns key:

<code><add key="ADdns" value="WinNT://123.abcdefghijk"/></code>

Rock on!!!!!

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question