Resco Explorer (v8.00)

Frequently Asked Questions

1. Installation
2. Common questions
3. Encryption
4. Registry
5. ZIP Compression
6. Infrared Support
7. Bluetooth Support
8. Network drives mapping
   1. I can see no "Computers Near Me" in the Network Drive Mapping window.
   2. The Network Drive Mapping window spends a lot of time scanning "Computers Near Me"
   3. I can see my desktop computer listed in the Network Drive Mapping window but I am unable to map its drive because it yields the following error: "A device with the same name already exists..."
   4. I am not able to map a network drive.
   5. I am not able to map a network drive and I suspect that the system uses an invalid account which I previously saved as the default account for drive mapping.
   6. I have my desktop computer connected to a Windows NT domain and I am unable to map its shared drive.
   7. I have problems connecting to Windows Server 2003 running as a domain controller.
   8. I am not able to map the Linux (or MAC) Samba drive
9. FTP Addin

8. Network drives mapping

8.1. I can see no "Computers Near Me" in the Network Drive Mapping window.

Please check the IP subnets in the Settings dialog. The desktop PC and the PDA must use the same subnet and this subnet must be listed in the settings. Use the Autodetect feature which enumerates all PDA's network adapters and collects all active subnets for scanning.

If your network structure is a complicated one and the auto-detect feature does not work, please turn it off and manually specify the subnets which have to be scanned.

8.2. The Network Drive Mapping window spends a lot of time scanning "Computers Near Me"

One of your active network adapters has presumably selected the huge IP subnet (the range of IP addresses considered to be "Computers Near Me"). You can resolve this issue by choosing the smaller subnet under Connection Settings or you can disable the "Autodetect Mode" under Map Drive Settings and choose only the part of the subnet that has to be scanned. Be careful to specify all subnets covering all the computers you want to access. Ask your system administrator to help you choose the proper values.

8.3. I can see my desktop computer listed in the Network Drive Mapping window but I am unable to map its drive because it yields the following error: "A device with the same name already exists..."

Try to change the device ID (Start Menu/Settings/About/Device ID). Type a unique name (e.g. FirstnameSurnamePPC) and do not use the underscore. After pressing OK you will have to soft-reset the device to apply the changes. This is a known bug of the PocketPC OS. You don't have to be afraid of loosing the ActiveSync profile settings. This action will only rename your current profile.

8.4. I am not able to map a network drive.

Ensure that you are using the same account (login and password) which exists on the desktop computer and has enough permissions to map and access the shared drive. If you don’t know which account is used refer to the next question. If the account used is correct and you are mapping the drive from a computer connected to the Windows NT domain refer to Q6.

8.5. I am not able to map a network drive and I suspect that the system uses an invalid account which I previously saved as the default account for drive mapping.

An account (login and password) used for mapping a drive is managed by the system. The system prompts you for the login and password the first time you are trying to map a drive. The Login dialog contains also an option allowing you to save the account. If you select this option the account is saved and used as default during the next mapping attempt. The system will never prompt you for login and password again for this drive so you have to be careful when saving the proper account.

The account is not visibly stored. The only way to clear it is to convince the system of its invalidity. Disable the account on the source network computer (or in the domain). When the account cannot access the network, the system will ask for the password anew.

8.6. I have my desktop computer connected to a Windows NT domain and I am unable to map its shared drive.

The servers on an NT domain often manipulate the hostname resolution on their member computers. If you have a notebook and you'll connect it to the domain, it is possible that you'll no longer be able to perform hostname resolution in the workgroup (e.g. at home).

The gist of this problem is that the computer's Node Type setting is changed from broadcast to point-to-point. When the desktop computer uses the point-to-point Node Type, you will not be able to map its drives on your Windows CE based device (tested on PocketPC).

If you are a skilled user you can resolve this problem by following the instructions below. To check your Node Type setting run the Command Prompt (Cmd.exe) on your desktop PC and type the following command: ipconfig /all. Scroll up and look for the Node Type setting (it is at the beginning). It should be set to “Broadcast”. If it is set to something else (e.g. Point-to-point or Peer-to-Peer) you will have to change it:
Run Regedit and select the following key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters

Look for the key DhcpNodeType. If you find it, please try to rename it to DhcpNodeType_Backup and restart the computer. Consult our support for details and more help.

8.7. I have problems connecting to Windows Server 2003 running as a domain controller.

Windows CE networking is not able to map the drives from the servers using SMB signing.

This can be solved by changing the following setting in the Domain Controller Security Policy under Local Policies --> Security Options
Microsoft Network Server: Digitally sign communications (always): Disabled

8.8. I am not able to map the Linux (or MAC) Samba drive

This problem is similar to 8.7. You need to disable SMB signing. Please try to locate the "smb.conf" file and add the line use spnego = no under section [global]