The RPC Server is unavailable

[pdumbleton]

I think I understand why this is occuring.

My server, lets call it server1, has a FQDN of server1.mydomain.com, all servers in my AD Domain have the same primary DNS suffix. LANSweeper has no problem collecting information from the servers.

My clients have a FQDN of client1.client.mydomain.com and all clients are getting the RPC Server unavailable error in LANSweeper.

If I understand the Active Scanning service correctly, it uses the FQDN of the LANSweeper server to attempt connection to any clients or servers in AD that it has enumerated.

The server is able to ping the host using the netbios name, Client1 , the FQDN of Client1.client.mydomain.com and the IP address. It fails using FQDN of Client1.mydomain.com. This happening using both ping in the command window and the testconnection.exe software.

Is there a workaround for this, other than adding the lsclient to the login script?

Thanks.

BTW this is a really good piece of software.

Update: I did notice that the correct FQDN is in the dbo.tblADComputers.DNSHostname field. Is this being used to connect to the clients?

[Hemoco]

This bug is fixed in version 3.5

[Hemoco]

I can confirm that this a a bug and will be fixed in the next release. (the service scans on the wrong fqdn name)

[pdumbleton]

That is correct.

The reason for this is that we have two DNS servers. A Cisco DNS server that manages the zone mydomain.com and a Microsoft DNS that is integrated into our AD for DHCP purposes which is zone client.mydomain.com.

[Hemoco]

If I understand correctly the domain to which your clients belong is : mydomain.com but the FQDN name for the clients is client1.client.mydomain.com.
Is this correct?