cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
jeslimei
Engaged Sweeper
Lansweeper wrote:
Download from here : http://www.lansweeper.com/testconnection.zip

Use this tool from the same machine where the service is installed.
Make sure it runs using the same account as the service.

Test the machines that are giving problems in three different ways:
- On hostname (netbios name)
- On FQDN (long name : computer.domain.local)
- On IPaddress
=============================================

I tested these 3 ways at the Lansweeper installed server.

On hostname - test OK
On IPaddress - test OK
On FQDN - test Failed meaning when i put servername.domain.local (failed)

Why is that?

For the scan, it seems that everything is being scanned.
However Compsystem is in RED

Autorun 5 08/10/2009 1.99
Baseboard 32 08/10/2009 0.03
Battery 27 08/10/2009 0.03
Bios 30 08/10/2009 0.03
Bootconfig 29 08/10/2009 0.02
Bus 30 08/10/2009 0.06
Cdrom 60 08/10/2009 16.94
Codec 50 08/10/2009 0.59
Comapplication 26 08/10/2009 0.58
Componentcat 40 08/10/2009 0.11
Compsysprod 24 08/10/2009 0.02
Compsystem 1 ---> in red (not scanned)
Dcomapp 23 08/10/2009 0.61
Desktop 22 08/10/2009 2.17
.
.
.

Why?
1 REPLY 1
Hemoco
Lansweeper Alumni
jeslimei wrote:

On FQDN - test Failed meaning when i put servername.domain.local (failed)

Why is that?

Check your dns server, most likely servername.domain.local resolves to a wrong ip address (or does not resolve at all)

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now