Issue:
The customer has an MS AD Parent / Child setup and webNetwork is having many problems creating objects in webAdmin. When a wizard is used to create a webApp and the end the Host, Link and User cannot be modified.
Resolution:
This was verified by going to webNetwork server 8090 management console and turning on the following debugs:
com.stoneware.service.directorymanager
com.stoneware.service.public.admin.createlink
com.stoneware.service.public.admin.createobject
com.stoneware.service.public.admin.modifyattribute
When things are working fine when the debug is viewed when the wizard was used, the following debug will be shown:
DEBUG (09/11) 14:35:45 [com.stoneware.service.public.Admin.createObject]: cn=test4-webapp,ou=stoneware,dc=example-cloud,dc=com was created on: dc1.example-cloud.com
DEBUG (09/11) 14:35:45 [com.stoneware.service.public.Admin.createObject]: cn=test4-host,ou=stoneware,dc=example-cloud,dc=com was created on: dc1.example-cloud.com
DEBUG (09/11) 14:35:45 [com.stoneware.service.public.Admin.createLink]: cn=test4-link,ou=applications,ou=stoneware,dc=example-cloud,dc=com was created on: dc1.example-cloud.com
DEBUG (09/11) 14:35:45 [com.stoneware.service.DirectoryManager]: cn=test4-webapp,OU=Stoneware,dc=example-cloud,dc=com> was created on server: dc1.example-cloud.com
When things are not working, the wrong DNS name will be shown for "was created on: xxx.example-cloud.com".
To fix this:
- Make sure that Multi Domain Support is enabled in the 8090 management console.
- Make sure the Search Scope and the Domain Tree Root match exactly.
- Make sure the DNS name / IP address is set to an IP address or DNS name of the DC in the top level of your tree.
- Make sure that a Global Catalog in the same part of the tree is used. Usually set the GC to the same as DNS Name / IP address.
- Make sure that SSL is checked in the 8090 console. Microsoft requires that SSL be used for Multi Domains.
- Make sure that the DNS name / IP address resolves to the real machine name.
ping -a 1.1.1.1 should equal the machine name of the DC. - Make sure that the domain name (same as search scope) resolves to the IP number in Step 6.
ping example-cloud.com should equal 1.1.1.1 from Step 6.