Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD on remote serverAD on remote server
Previous
 
Next
New Post
10/31/2007 10:20 AM
 
I have the DNN installation on Server 1 and AD on Server 2.
I have the domain name’s ( mydomain.com) A record pointing to Server 1 and I have the same domain name used for my AD on Server 2.
Obviously, when I put mydomain.com as the domain in the AD module setup in DNN it does not work as the AD is on another server.
My question is – is there a way to make it working with such setup? When trying to connect to the AD, is the module using the DNS server address for the domain or is it using the A record?
Thank you in advance for your kind help :)
 
New Post
10/31/2007 2:36 PM
 

Are both servers part of the same domain? The way I read your post they are but I just want to be sure.

Did you enter mydomain.com in the root domain textbox or did you enter dc=mydomain, dc=com? It has to be in the second format.

The AD can be on another server (in every instance that I've used the provider the AD has been on a separate server). I don't know about Server 2003 as I've never tried it but Server 2000 would complain if you tried to run a webserver on a domain controller.

 

 
New Post
10/31/2007 5:38 PM
 

Thanks for your reply Mike,

you are bringing a good point - no - the servers are not part of the same domain.

I think that this is my problem - Server 2 has an AD for mydomain.com, mydomain.com does not have neither the DNS neither the A record pointing to that server, so obviously when i type dc=mydomain, dc=com (thanks for the clarification on the format) it does not know where to look for the AD.

Any suggestions on how to handle this? Should I change the DNS server to be the on the AD directory server? I can not point the A record, as it is pointing to the web server.

 
New Post
10/31/2007 5:56 PM
 

I really don't know which direction to point you as I haven't tried setting up the provider on a server that isn't part of the domain. It's one of my plans but time and resources haven't worked out in my favor yet.

 
New Post
11/1/2007 4:48 AM
 

Hi Mike, i've got the same problem. I've got two domains with trust relationships between them. The web server is located in one domain appdomain.com with AD and users that should log on to portal is on other domain sub.domain.local with AD.

When I get user information form sub.domain.local  with ADSI scripts with appropriate users permissions it works fine. The syntax looks like this:

usr = GetObject("LDAP://CN=VASYA, OU=WEB USERS, DC=SUB, DC=DOMAIN, DC=LOCAL") 

and I've got the username in usr.GivenName and displayname in usr.sn.

The AD provider did not do that. Provider did not return neither UserName nor DisplayName. When I log on to portal with Windows Auth turned on with user form sub.domain.local  the user is logged on, portal user is created but Display Name is empty, First Name filled in with domain NETBIOS name and Last Name filled in with SAM account name.

I have no time to wait and I wnat to try to modify the source of AD Provider but where can i get it. Can you share the source?

Victor

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD on remote serverAD on remote server


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out