Atelier Web Remote Commander - FAQs Please check also the FAQ in the Help file of the software. Q: Does AWRC work with Windows 7? A: Yes, AWRC works very well with Windows Vista and later, which includes, of course, the latest Microsoft Operating Systems, Windows 7 and Windows Server 2008/2008R2. For Windows Vista and later specific questions please read here.

Q: How can I connect to various remote computers at the same time?

A: Just launch another instance of AWRC and connect. No configuration is needed.

Q: Is it possible various AWRC clients to connect at the same time to a remote machine?

A: Yes and no configuration is needed for that.

Q: How can a Domain Administrator connect to a workstation within Active Directory?

A: Enter the user name in the form User@Domain or Domain\User

Q: How can I produce Ctrl+Alt+Del on the remote computer?

A: You can produce Ctrl+Alt+Del (the security attention sequence) by pressing Ctr+Alt+D. On the registered version, other Hot Key sequences are possible.

Q: Why am I unable to connect to other remote computers?

A: Either within a local area network or across the Internet, AWRC requires Microsoft Networks to be operative - Client for Microsoft Networks installed on both local and remote machines and File and Printer sharing enabled at least on the remote machine.
If the remote computer platform is Windows XP Professional, the access is only possible within the classical sharing and security model for local accounts. This is enabled from Control Panel / Administrative Tools / Local Security Policy / Network access: Classic - local users authenticate as themselves. You can obtain the same result from Windows Explorer / Tools / Folder Options / View and uncheck Use Simple File Sharing (In Windows Vista and Windows 7 uncheck Use Sharing Wizard (Recommended). This will revert you to the classical model as well).

Q: Which ports are used by AWRC?

A: AWRC does not open any ports, it simply requires Microsoft Networks. Microsoft Networks uses port 445 (Windows NT used also 135, 137, 138, 139) . However, operations performed by AWRC run only through TCP port 445 (Windows 2000 and above) or TCP port 139 (Windows NT 4. Windows 2000 and above can use as well if port 445 is not available). Ports 135, 137, 138 and one of 139 or 445 can be blocked by the firewall or router without interfering with AWRC operation.

Q: You say that AWRC is transparent to firewalls but I can't get it to work within my Company LAN!?

A: The firewall is blocking the use of Microsoft Networks, in particular port 445 (or port 139, if Windows NT). See the question Which Ports are used by AWRC.

Q: How safe is AWRC for use across the Internet?

A: Microsoft Networks, in particular port 445 and even port 139 are safe when you have a good password. Since all security is based on the password, all exploits are just password-guess dictionary attacks. A good password will take millions of years to be guessed.
Additionally, AWRC may use strong encryption which makes virtually unbreakable the data exchange between both end-points.

Q: Can I use AWRC across a VPN?

A: Yes, AWRC works very well with the VPN products we are aware of.

Q: How fast is AWRC?

A: AWRC was tested to be faster than practically every other remote access softwar, including all VNC variants. It is not faster than software that uses so-called display mirror drivers. The portable nature of AWRC allowing connections without remote software installs does not make it suitable to be used with mirror drivers (which require reboot after install and  reboot after uninstall).

Q: Why does the mouse flicker on the remote machine?

A: The mouse only flickers when View Layered Windows is selected in the Configuration (this is not the default). Due to hardware and OS implementation reasons, in most cases there is no way around it unless we used a mirror driver. We are not using a fake mouse cursor (i.e, hide the real mouse cursor and draw a bitmap simulating a mouse cursor), because it causes a drag and other adverse effects.

Q: Can I use AWRC on a Windows Server running Terminal Services?

A: You can without restrictions with AWRC 6.0 or later.

Q: How can I connect to another computer across the Internet?

A: The same rules apply, see the previous questions. If the local and remote computers are behind routers and personal firewalls you must make sure that:

• The local computer personal firewall allows outgoing connections on TCP port 445 (TCP port 139, if Windows NT). Normally this does not require action on your part.
• The router on the remote network forwards TCP port 445 (TCP port 139, if Windows NT) to the private IP address of the target machine.
• The personal firewall of the remote machine allows incoming connections on TCP port 445 (port 139, if Windows NT).

See these YouTube videos in full screen:

Q: Does AWRC work with Windows 64-bit Operating Systems?

A: It works very well with all 64-bit Windows Operating Systems (the latest one as of this writing is Windows Server 2008R2).

Q: I have been trying and can not connect to my XP Home Edition laptop!?

A: You can not, have another look at the Requirements in the Help file.

Q: Is it possible to launch AWRC from the command line and make a connection?
A: yes, it is possible. The syntax is:
Path\awrc.exe /r=<Remote Host> /u=<User> /p=<Password>
For example:
"C:\Program Files\Remote Commander\awrc.exe" /r=192.168.1.100 /u=Administrator /p=Mypassword