cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
stobias
Engaged Sweeper
But, it works fine when opened independently. The IP address is correct on the webpage(which is a miracle) and when launching LSREMOTE is comes back with RPC server unavailable.

Then I launch the LSREMOTE tools from the lansweeper$ share and use the exact same IP address it connects fine.

Anyone have any ideas?

Current action is {actionpath}lsremote {smartname}

Changing the action to {actionpath}lsremote {ipaddress} works

All other {smartname} commands work.
1 ACCEPTED SOLUTION
Hemoco
Lansweeper Alumni
This is likely a DNS problem and not a Lansweeper problem. "Smartname" is the computer's FQDN or, if an FQDN is not available, NetBIOS name. If connecting with the smartname parameter doesn't work, but connecting with the IP address does, your computer's FQDN/NetBIOS is likely not resolving correctly. (You indicate that other smartname commands work, but do they work for that specific problem computer?)

We recommend checking your DNS settings to ensure that all computer names resolve to the correct IP addresses and vice versa.

View solution in original post

1 REPLY 1
Hemoco
Lansweeper Alumni
This is likely a DNS problem and not a Lansweeper problem. "Smartname" is the computer's FQDN or, if an FQDN is not available, NetBIOS name. If connecting with the smartname parameter doesn't work, but connecting with the IP address does, your computer's FQDN/NetBIOS is likely not resolving correctly. (You indicate that other smartname commands work, but do they work for that specific problem computer?)

We recommend checking your DNS settings to ensure that all computer names resolve to the correct IP addresses and vice versa.