The RPC server is unavailable, is half the truth...

[Lars_Vopicka]

Hi All,

after playing around a while i have found the following:

I get an RPC error if the fqdn, listed in AD is not the one from DNS.
Our Network does not allow dynamic updates to the DNS. Nevertheless the fqdn is generated by Domain membership. Of course I could change all entries by editing each and every Server in our domain.

I did edit the host file on the lansweeper Service pointing to the right adresses. I get no more RPC errors.
But,... this is very dirty.

What i would prefer is that lansweeper asks it's DNS-Server for the IP Adress and does not use the AD information.
How can this be accomplished?

Any suggestions Welcome!


@Geert, you might want to update your KB article. Im my case this is not a firewall issue, but missing name resolution

[Hemoco]

We are currently working on a test build that scans on
fqdn
computername
ipaddress
(in this order)

[dseidl]

we still have the same problem - fqdn in active directory is for example computer.domain.com, but dns name of computer is computer.subdomain.domain.com

[Lars_Vopicka]

I just sent you a pm.

Thanks for your patience.
Lars

[Hemoco]

Lars,

Could you give an example on how it looks in AD and in DNS please.