
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2014 06:05 PM
We re-installed LS on a new server and moved our old database over to the new server. I followed the directions for that step by step and everything confirmed that it was good. We did that on the 10th. Since then every time it scans it says there is an error, and shows the last tried time in red. If I click the errors tab it states that RPC was unavailable, BUT (while still looking at the same asset) if I click the rescan action button on the left it scans with no error and updates the page.
Any ideas on what I could do to fix this?
Any ideas on what I could do to fix this?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2014 06:52 PM
As explained previously, you need to test the connection to the FQDN and the NetBIOS name of the machine. The scanning error was generated while connecting to the FQDN, which is listed in the error; the Rescan buttons connect to the NetBIOS name, not the FQDN.
Preferably, you should also troubleshoot the *same* machine shown in your initial screenshots, not a different machine.
Preferably, you should also troubleshoot the *same* machine shown in your initial screenshots, not a different machine.
6 REPLIES 6

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-26-2014 10:48 PM
We can now ping all of our machines by FQDN. Thank you!

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2014 06:57 PM
I'm sorry I got in a hurry and didn't read that correctly. You are correct, they are failing when trying to use FQDN, we will look into that, thanks!!

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2014 06:52 PM
As explained previously, you need to test the connection to the FQDN and the NetBIOS name of the machine. The scanning error was generated while connecting to the FQDN, which is listed in the error; the Rescan buttons connect to the NetBIOS name, not the FQDN.
Preferably, you should also troubleshoot the *same* machine shown in your initial screenshots, not a different machine.
Preferably, you should also troubleshoot the *same* machine shown in your initial screenshots, not a different machine.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2014 06:50 PM
Just ran the exe you sent, everything passes. It was ran from the scanning server, both by name and IP.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2014 06:37 PM
The problem is probably that there is something wrong with the fqdn resolving of this asset.
When you scan an asset with active scanning we use the fqdn. When you re scan the asset we are going to use the netbios.
You can check if there is a difference with fqdn and netbios when you run the connetion tester to the fqdn of the asset and once to the netbios of the asset.
You can download the connection tester from: http://download.lansweeper.com/tools50/TestConnection.exe.
When you scan an asset with active scanning we use the fqdn. When you re scan the asset we are going to use the netbios.
You can check if there is a difference with fqdn and netbios when you run the connetion tester to the fqdn of the asset and once to the netbios of the asset.
You can download the connection tester from: http://download.lansweeper.com/tools50/TestConnection.exe.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-19-2014 06:10 PM
