 |
|||||||
 |
|
| :: Navigation |
| Home |
| Download |
| Buy Now |
| What's New |
| FAQ |
| Screen Shots |
| Mailing List |
| Contact |
| :: Information |
| Current version: 1.75 Release date: 4/29/2008 File size: 1.15MB |
|
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. (1) Right click on LanHelper shortcut, then select "Run as Administrator". (2) 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 program 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. (1) 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. (2). 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. (3). 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 your Windows XP system. You can use any one of the following methods to solve this problem. (1) 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. (2) 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. 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. (1) Restart your computer and try scanning again. (2) Select "Tools>Options" from the menu bar, click Scan tab, uncheck the option "Scan online computer only", click OK button. Then try scanning again. (3) 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. (1) 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. (2) 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. Q. Why cannot I shut down a Windows XP computer by using Remote Shutdown? A. Windows XP computer failed to be shut down remotely due to the default system configuration. There are two methods to solve this problem via configuring Windows system of the target computer using the Local Security interface. (1) Click "Start>Settings>Control Panel>Administrative Tools>Local Security Policy>Local Policy". Highlight the Security Options item in the left pane. In the right pane, locate the item titled "Network access: Sharing and security model for local accounts." The default option for this is the "Guest only - local users authenticate as Guest." Switch this option to the "Classic - local users authenticate as themselves." Thus you can log on remotely as a member of administrators group to shut down this computer by using Remote Shutdown. If the account 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". (2) Click "Start>Settings>Control Panel>Administrative Tools>Local Security Policy>Local Policy". Highlight the User Rights Assignment item in the left pane. In the right pane, double-click the item titled "Force shutdown from a remote system". Click "Add User or Group" button, in "Enter the object names to select (examples)", type "guest" and click OK. And then click OK again. Following this, click "Start>Settings>Control Panel>Administrative Tools>Computer Management>Local Users and Groups>User", in the right pane, double-click the Guest account. In the general tab of Guest Properties window, click the check box "Account Disabled" to make it unchecked, and then click OK. Thus anyone can shut down this computer by using Remote Shutdown without logging on. A restart may be required for the changes to take effect. Q. The feature that detects writable shared folders is quite dangerous. The files and folders in writable shared folders detected by LanHelper may be destroyed by anyone. What should I do to prevent it happening? A. At the beginning, I developed this feature to help myself clean the NIMDA virus on my network. But it might bring danger to the network users if someone misuses this feature. Anyone can use it to find the writable shared folders on the network and then modify or erase important data in those folders. To prevent this happening, use LanHelper to scan your network in time. Before this, make sure the scan options "shared folders" and "Detect the access to shared folders" have been turned on. After finishing scanning, select "View>Filter>Writable Share" from the menu bar, and then only the writable shared folders would be displayed in the Share column of the list. To the writable shared folders on Windows 95/98/ME system, you should configure them to be read-only ones or set password to protect them. To the writable ones on Windows NT/2000/XP, you should use Access Control List and Permissions Properties to protect them. For detailed information please refer to Windows help document. Q. Why the Windows 98 computers cannot receive messages sent from my machine? A. Under Windows 95/98/ME system, the program Winpopup.exe should be running to receive messages sent from other machines. To run Winpopup.exe, select Run from the Start menu to open the Run dialog box. Type "winpopup.exe" in the Open field and click OK button. Q. I used Scan IP under Windows XP but found that all the scan results were badly wrong. Why? A. This is caused by a bug in Windows XP system. You should install Windows XP Service Pack 1 or higher version to fix it. If your Windows XP system doesn't have Service Pack 1 or higher version installed, please set the value of the scan option "Maximum threads for IP scanning" to 1. Q. What should I note if I want to wakeup a machine located on another subnet? A. (1) Make sure Wake-On-LAN commands can reach the targets. Boot the target computer and run a packet sniffer on it and start capturing packet. Then from your computer send Wake-On-LAN commands to the destination by using Wake-On-LAN function. Check the sniffer whether it has captured the Wake-On-LAN data. If it has you would be able to send Wake-On-LAN command to this machine across subnet. (2) If the target computers cannot be reached, send Wake-On-LAN commands to router that the target subnet is directly attached to. You need configure the router yourself. Please read router's user manual for how to broadcast the Wake-On-LAN data into target subnet so all computers are able to receive Wake-On-LAN data. (3) The source port LanHelper uses in Wake-On-LAN command is port 9810 and the destination one is port 2304. So if you are using a firewall you need to open the ports for UDP traffic. (4) You should use unicast address or directed broadcast address. Directed broadcast address is an Internet Protocol address that specifies all nodes on a specified network. For example, send Wake-On-LAN commands to 192.168.10.255 so they can reach all nodes in the 192.168.10.x subnet. For all nodes on the specified network to receive the directed broadcast, each router attached to the network must have enabled directed broadcast. (5) If the target computers are very difficult to receive Wake-On-LAN data, another choice is use HUB in your network. For example, computer A and B all connect to one same HUB. A is powered down while B is running. When using unicast to send Wake-On-LAN commands to B, computer A and B will all receive the data at the same time. An old, second-hand HUB will help. (6) How to calculate the subnet-directed broadcast address. 1. Convert machine address to binary, e.g. 10.208.20.1 = 00001010.11010000.00010100.00000001. 2. Convert the Subnet Mask to Binary, e.g. 255.255.240.0 = 11111111.11111111.11110000.00000000. 3. Invert the Binary Subnet Mask, e.g. 11111111.11111111.11110000.00000000 becomes 00000000.00000000.00001111.11111111. 4. OR the machine address and the inverted subnet mask, e.g. 00001010.11010000.00010100.00000001 OR 00000000.00000000.00001111.11111111 = 00001010.11010000.00011111.11111111 = 10.208.31.255. From version 1.46 on, the program calculates the address for you. In Wake-On-LAN dialog, click IP Broadcast Address label, then select Internet option, enter IP and subnet mask, click Ok button to calculate. Q. I used Wake-On-LAN function to power on my PCs. Sometimes it worked fine but sometimes it failed. Why? A. A computer may not be powered on by using Wake-On-LAN, if it was shut down improperly, or the Windows 2000/XP/2003 system hibernated. For some network cards require a flag to be set, which only happens when the operating system power down the machine normally. A machine probably failed to be waked up after a power loss when AC power was restored. If you wish the machine to power on automatically on AC power back, you should configure the BIOS setup. Just enter BIOS Setup, then enter Power Management Setup, set the value of "AC Back Function" to "Full-On", then save and exit BIOS Setup. Q. After shutting down a Windows 2000 computer by using Remote Shutdown, I used Wake-On-LAN and expected to boot it but failed. Why? A. While a Windows NT/2000 computer is shut down by using Remote Shutdown, it simply shuts down the system and doesn't power down the machine, so you cannot power it on again by using Wake-On-LAN. Q. I already have a list of computer names and their MAC addresses. How can I use this list in Wake-On-LAN? A. (1) In version 1.40 or higher, use Import function to import your data into the program. (2) In early version, run the Notepad.exe application or any other plain text editor, input the existing MAC address, IP broadcast address and machine name just as the following format: FF-07-E9-0F-20-12; 255.255.255.255; PC1 FF-05-5D-FB-90-DB; 192.168.1.255; PC2 FF-50-BA-10-7C-8C; 255.255.255.255 FF-02-B3-50-E6-6B Use semicolon as the delimiter in each line. IP broadcast address and machine name are optional. If IP broadcast address is omitted, 255.255.255.255 would be specified by default. After input completed, save them to a text file (.txt). Click Load button in Wake-On-LAN dialog, and then open the file that you saved just now. All the targets would then be loaded into Wake-On-LAN dialog. Q. How to use the machine data in Microsoft Office? A. (1) Excel2002: Open your XML file created by LanHelper in the "File>Open" dialog box in Excel. In Import XML dialog box, select "Open the file with the following stylesheet applied" (The only stylesheet it has is pre-selected for you), and click OK button. (2) Excel2000: Import your data to a CSV file in LanHelper, and then open it in Excel2000. (3) Word2000/2002: Open your XML file saved by LanHelper in IE or other web browser, click "Edit>Select All" from the menu bar, and then click "Edit>Copy". Run the Word 2000/2002 program and click "Edit>Paste" from the menu bar. Q. Which ports are used by LanHelper? A. From version 1.30 on, LanHelper opens TCP port 9812 and listen on it. This port is used by LanHelper Integrated Command. In Wake-On-LAN command, the source UDP port is port 9810 and the destination UDP port is port 2304. The other ports may be used by the program are standard Windows system ports, 137, 139, 445. For example, UDP port 137 is used by Refresh Status. Destination TCP port 139 is used by Remote Shutdown and Abort Remote Shutdown. Destination TCP port 445 is used by Remote Execute. UDP port 137 is used by Send Message. Q. How to manually unlock the mouse and/or keyboard if they were locked by LanHelper? A. Just press Ctrl + Alt + Shift + U keys If the keyboard was locked. If only mouse was locked, press Ctrl + Shift + Esc keys to make the Windows Task Manager visible, then use your keyboard (Tab, up arrow, down arrow, Alt + E) to terminate the msspr.exe process. You may fail to terminate this process if you haven't enough permissions. Then another simple way is restarting the computer. |