|
|
|
|
Group: Forum Members
Last Login: Thursday, May 10, 2012
Posts: 1,
Visits: 8
|
As the subject says, due to our unique in-house multi-subnet, distributed DNS system we have in place (which I do not fully understand or have control over), it doesn't really work when resolving HOSTNAME.DOMAINNAME as the Linked Active Directories feature would imply.
The only way we can use the software is either via Entire Network (not good enough really) or by adding all the computers to the Registered Computers section, and ensuring we check "Use computer host name as registered computer IP".
Any ideas?
Thanks, Tom
Tags:
|
|
|
|
|
Group: Administrators
Last Login: Yesterday @ 8:06 AM
Posts: 1,686,
Visits: 3,175
|
Hi Tom,when we fetch AD computers from a Linked AD we set a computer's hostname to the value of dNSHostName property. If this property is empty, then we use name property instead. With regards of your unique problem, I think there is a solution. On your computer you need to open properties window for the LAN connection, then select Internet Protocol Version 4 (TCP/IPv4) and click on the Properties button. Than click on the Advanced button, switch to the DNS tab. DNS sufix for this connection: enter your domain name.  Yesterday, I actually had to use this trick and it helped me to fix the same problem as yours (computer hostname works, hostaname.domain doesn't resolve).
Kindest Regards,
SmartCode Solutions Support
|