|
Frequently Asked Questions
Q. How to run LanHelper on Windows Vista?
A. If User Account Control (UAC) is enabled on Windows Vista, you will probably get this error "You MUST have administrative privileges to run this program" while running LanHelper, even if you are an administrator. There are two methods for this issue.
- Right click on LanHelper shortcut, then select "Run as Administrator".
- Right click on LanHelper shortcut, select "Properties", under the Compatibility tab, check "Run as Administrator", then click Ok button.
Q. The target computer was running, but I got this error "The network path was not found".
A. There are four possible reasons. On the target computer, (1) Microsoft Files And Printers Sharing is not installed and enabled. (2) The Server service is stopped. (3) The SMB (TCP 445) and NetBIOS (TCP 139) protocols are blocked. (4) At most time you will get this error if the target computer has a firewall running.
Q. I often got this error "Access is denied".
A. You should provide correct security credentials ("Network>Security Credentials") so can have enough permissions. For detailed information please refer to Security Credentials section of the help document.
Q. While using Remote Execute function, I got this error message "you have not enough permissions or the ADMIN$ has been disabled on xx.xx.xx.xx."
A. There are three possible reasons.
- A firewall program is running on remote computer. If so, you will failed to schedule task or perform other network operations on it. To evaluate LanHelper, please temporarily disable the firewall, or configure the firewall to allow incoming traffic on TCP port 445.
- You have not enough permissions. In Remote Execute, click "Remote Logon - Settings" button, select "specify credentials" in Security Credentials drop-down list and enter an administrator account into corresponding fields. To a Windows XP computer, you may need to configure the Windows XP system so you can remotely log on to it successfully. On Windows XP system, click "Control panel>Administrative Tools>Computer Management>Local Security Policy>Local Policy>Security Options", in the right pane double-click the item titled "Network access: Sharing and security model for local accounts." The default option for this is "Guest only - local users authenticate as Guest." Switch this option to "Classic - local users authenticate as themselves." If the account that you are using to logon remotely has a blank password, it's recommended to disable this security option "Accounts: Limit local account use of blank passwords to console logon only". A restart may be required for the changes to take effect. Sometimes some policies will cause your network operation failed. On remote computer's system, click "Control panel>Administrative Tools>Computer Management>Local Security Policy>Local Policy>User Rights Assignments". In the right panel, check those items "Access this computer from the network", "Deny access to this computer from the network", whether the account you used in LanHelper have been added to them.
- The remote computers should have these two shares: ADMIN$, IPC$. If they have been disabled, you ought to enable them just as how they were disable. You may check them in LanHelper's scan results.
Q. Cannot schedule task on remote computers or local one by using Remote Execute from my Windows XP computer. The error information is "The binding handle is invalid", the error code is 1702. But I can schedule task on this computer from other computers.
A. This will happen if the MS04-011(835732) security update has been installed in the target Windows XP system. You can use any one of the following methods to solve this problem.
- In version 1.41 or higher, turn on the Remote Execute option "Switch IP address to DNS or NetBIOS name for selected machine(S)" in Options dialog. In early version, specify DNS name or NetBIOS name instead of IP address in "Computers" field in Remote Execute.
- Uninstall the KB835732 hotfix. After a reboot, you should install the Windows XP Service Pack 2 or higher version as soon as possible to better protect your computer.
You can learn more about the problem from Microsoft Knowledge.
- Sometimes stopping the Terminal Services will also probably cause this error. So please start the Terminal Services on target computer and try again.
Q. After finishing scanning, I found that the number of the returned items in the main window was often less than the one of the scanned machines displayed at status bar. Is this normal?
A. This will happen if the scan option "scan online computer only" is turned on. They will be equal if you turn off this option.
Q. Cannot get anything after scanning network. Or the MAC addresses are all returned as "00-00-00-00-00-00". Why is this so?
A. Try one of the following methods.
- Restart your computer and try scanning again.
- Select "Tools>Options" from the menu bar, click Scan tab, uncheck the option "Scan online computer only", click OK button. Then try scanning again.
- If the problem persists, you may need to check whether your computer uses NetBEUI protocol. In Windows 2000/XP, click "Start > Settings > Control Panel > Network and Internet Connection". Open Properties of Local Area Connection. If NetBEUI protocol is in the component list, you may need to uninstall it so LanHelper will scan normally (DO NOT uninstall NetBEUI if any program in your computer only uses this protocol). If TCP/IP protocol is not in it, you must install it.
Q. Why did LanHelper only return the information of my own computer after scanning network?
A. Steps:
- You were using Scan LAN or Scan Workgroup. Please inspect whether your computer is connected to network normally. Also inspect the network configuration to check whether IP address, subnet mask and so on are configured correctly.
- You were using Scan IP. Scan IP function sends ICMP echo request to destination to verify whether an IP is in use or active. So if the router blocked ICMP traffic, only your own computer or a portion of the computers in your network would be returned. Many personal firewall programs installed on PCs would also block ICMP, which make LanHelper unable to scan those machines too. In version 1.20 or higher, it would be helpful for Scan IP to find out more secret targets if you turn on the scan option "Skip ping while scanning IP".
Q. Cannot obtain currently logged-on user name while scanning network.
A. The general reason is that the Messenger service on remote system was not running. The computer name is probably returned if the user name was not unique on local network.
Q. Why the Scan IP function cannot scan machines that located outside my LAN?
A. Scan IP function sends ICMP echo request to destination to verify whether an IP is in use or active. However, many attacks and worm viruses also used ICMP widely. So hardly all the routers on LAN and WAN had to filter ICMP traffic. This is why Scan IP function frequently failed to scan other subnet. Now you can turn on the scan option "Skip ping while scanning IP" and it helps you retrieve more targets from other subnet, but this would slow down the speed.
Q. How to get MAC address of the computer that has been turned off?
A. From version 1.46 on, you can get MAC addresses of turned-off computers or running ones, as long as the network devices within your network, such as router, switch or xDSL modem, support SNMP MIB-2 and have an IP address. Click Wake-On-LAN button in toolbar, click "Get MAC from router, switch or modem" label. Enter IP address of the network device or the gateway into IP Address field and click Get button. If anything go right, you would get some MAC and IP addresses. In a DHCP network some duplicate MAC addresses may be returned. Click Add Item button to add those data to the main window. Click Ok button to add MAC addresses to the list in Wake-On-LAN dialog and return.
Q. The remote computer doesn't power down as I shut down it remotely. Is this normal?
A. LanHelper (or other similar programs) can not make a Windows NT/2000 system power down by using Remote Shutdown function. The computer being shut down remotely will flush all caches to disk, clear the screen, and then display a message indicating that it is safe to power down. Only the Windows XP/2003 computer can be powered down remotely. Please refer to Remote Execute and LanHelper Integrated Command, new features in v1.10, for how to power off Windows 2000/XP/2003 computer on LAN or WAN.
»
|
