ShareConnect System Requirements

Windows Host Computer

  • This is the computer that is being access remotely (For example: A work computer you will access from home)
Operating System Windows 7 or later
Server Windows Server 2008 R2 or later
Internet DSL or better (for remote computers)


Mac Host Computer

  • This is the computer that is being access remotely (For example: A work computer you will access from home)
Operating System Mac OS X 10.8 or later
Internet DSL or better (for remote computers)


Viewer (Desktop)

  • This is the desktop computer used to remotely access one of the above host computers (For example: A home computer you use to remotely access a computer located at work)
Web Browser Internet Explorer v11 or later
Google Chrome (latest version)
Desktop App Windows .NET Framework 4.5 or later
Mac OS X 10.11 or later
Internet DSL or better (for remote computers)

Viewer (Mobile)

  • This is the mobile device used to remotely access one of the above host computers (For example: A phone or tablet you use to remotely access a computer located at work)
iOS Devices
Device iPads or iPhones hardware supporting version iOS version 7.0 or later
Operating System iOS 8.0 or later
Internet “Always on” Internet connection; WiFi recommended
Additional Software Free ShareConnect app from the iTunes Store
Android Devices
Device Android tablet and phones
Operating System Android 3.0 (Honeycomb) or later for tablets and Android 4.0 (Ice Cream Sandwich) or later
Internet “Always on” Internet connection; WiFi recommended
Additional Software Free ShareConnect app from the Google PlayStore

Client Computer

Operating System Windows 7 or later
Server Windows Server 2008 R2 or later
Internet DSL or better
Additional Requirements .NET Framework 4.0 or later


File Server

Operating System Windows 7 or later
Server Windows Server 2008 R2 or later
Internet DSL or better
Additional Requirements .NET Framework 4.0 or later

Related:

Sysfer.dll crashes applications

I need a solution

From Thursday 17/10/19 I have a problem with several machines
Shows me the following message (image attached) on the Windows error screen and can not use several programs
in order to fix it I did a reinstallation of the operating system.
any solution?
 
thanks
 
 
0

1571328239

Related:

Provisioning Server 7.6 – Windows 2012 R2 shows “getting device ready” every time the machine boots up .

Getting devices ready is a OS related process wherein all the devices are been enumerated (Moreover we call it a hardware enumeration) .it is actually not an issue but it’s a process that its executed every time the machine boots up .If OS detects a change in the device it enumberates it and install the required driver for that device.

By default its run every time the machine start.

Reference to Microsoft link : http://blogs.technet.com/b/wincat/archive/2012/09/06/device-management-powershell-cmdlets-sample-an-introduction.aspx

( Hardware enumeration is something that the vast majority of Windows users don’t need to worry about. Thanks to an extensive PnP infrastructure, the process of identifying devices, installing drivers and controlling those devices is handled transparently by the Operating System)

Related:

Sophos Anti-Virus for Linux and Unix: Communication with Update Server uses HTTPS by default

This article is to advise that Sophos Anti-Virus (SAV) for Linux and Unix will use TLS secure protocol HTTPS to communicate with the configured Update Servers.

The following sections are covered:

Applies to the following Sophos product(s) and version(s)

Sophos Anti-Virus for Unix 9.15.0

Sophos Anti-Virus for Linux 9.14.2

  • Linux (supported Linux platforms)
  • Unix (Supported Unix platforms)

From version 9.15.0 of SAV for Unix and version 9.14.2 of SAV for Linux, SAV will use the secure TLS HTTPS protocol for communicating with the configured Update Server. If an HTTPS connection cannot be established after a 10 minute timeout, it switches back to an HTTP connection automatically.

If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.

This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Related:

7021483: Reflection Products and Microsoft Windows XP

Designed for Windows XP – Optimized Status

The following list of Reflection products and components have been tested with Windows XP and have earned the Microsoft “Designed for Windows XP – Optimized” status.

Note: Although Microsoft’s XP certification program has been discontinued, Attachmate continues to test our products with Windows XP. For a list of newer Reflection products tested with XP, see the next section, Other Products Tested Under Microsoft Windows XP.

Refer to your product documentation to determine which products and components are included on your Reflection product CD.

Reflection 14.0 Products

Reflection for Multi-Host Enterprise Standard Edition 14.0

Reflection for Multi-Host Enterprise Professional Edition 14.0

Reflection Suite for X 14.0

Reflection for UNIX and OpenVMS 14.0

Reflection for HP with NS/VT 14.0

Reflection for IBM 14.0

Reflection X 14.0

Reflection NFS Client 14.0

Reflection 14.0 Product Features

Reflection for ReGIS Graphics 14.0

Reflection for UNIX and OpenVMS 14.0

Reflection FTP Client 14.0

Reflection LPD 14.0

Reflection 13.x Products

Reflection for Multi-Host Enterprise Standard Edition 13.x

Reflection for Multi-Host Enterprise Professional Edition 13.x

Reflection Suite for X 13.x

Reflection for UNIX and OpenVMS 13.x

Reflection for HP with NS/VT 13.x

Reflection for IBM 13.x

Reflection X 13.x

Reflection NFS Client 13.x

Reflection 13.x Product Features

Reflection for ReGIS Graphics 13.x

Reflection for UNIX and OpenVMS 13.x

Reflection FTP Client 13.x

Reflection LPD 13.x

Other Products Tested Under Microsoft Windows XP

The following product were tested under Windows XP, but were not submitted for Microsoft “Designed for Windows XP – Optimized” status because Microsoft’s XP certification program has been discontinued.

Reflection 2014 Products

Reflection 2014

Reflection for IBM 2014

Reflection for UNIX and OpenVMS 2014

Reflection 2011 Products

Reflection for IBM 2011 R1

Reflection for UNIX and OpenVMS 2011 R1

Reflection Standard Suite 2011 R1

Reflection 14.1 Products

Reflection for Multi-Host Enterprise Standard Edition 14.1

Reflection for Multi-Host Enterprise Professional Edition 14.1

Reflection Suite for X 14.1

Reflection for UNIX and OpenVMS 14.1

Reflection for HP with NS/VT 14.1

Reflection for IBM 14.1

Reflection X 14.1

Reflection for Secure IT Products

Reflection for Secure IT Windows Client 7.0 or higher

Reflection for Secure IT Windows Server 7.0 or higher

For more information about supported platforms, see Technical Note 1944.

Reflection for the Web Products

Reflection for the Web 2014, 2011, or 2008 client components will run on Windows XP as long as Reflection for the Web is running on a system that meets minimum system requirements for the operating system, the Java runtime environment, and the web browser.

For a list of system requirements, see the Reflection for the Web Technical Specifications: http://www.attachmate.com/Products/Terminal+Emulation/refweb/rweb/rweb.htm.

For additional information about Reflection for the Web and Java Virtual Machines, see Technical Note 1674.

Note: Windows XP is not a server operating system. We do not recommend running Reflection for the Web server components in a production environment on a workstation operating system such as XP.

Products and Components with Known Issues

The following products and components have known issues with the Microsoft Windows XP operating system.

Reflection NFS Client

Reflection NFS Client version 12.0 or higher has earned the Microsoft designed for Windows XP, Optimized status. Reflection NFS version 10.0 or higher can be installed on Windows XP.

Reflection NFS Client versions 9.0 or earlier are incompatible with Windows XP. Attachmate strongly recommends that you do not attempt to install Reflection NFS Client versions 9.0 or earlier to Windows XP.

Important: If you have Reflection NFS installed and are planning to upgrade existing workstations to Windows XP, you must first uninstall Reflection NFS Client (all versions). Not uninstalling NFS prior to upgrading may leave your workstation in an unstable state. Beginning in Reflection 14.1, NFS Client is no longer available. For details, see Technical Note 2495.

Reflection TimeSync

Windows XP’s built-in Windows Time Service uses the same TCP/IP port as the Reflection TimeSync component. Due to this conflict, use of Reflection TimeSync on Windows XP is not recommended. Attachmate Technical Support recommends using Windows Time Service instead of Reflection TimeSync on Windows XP. See the sections below for information about Reflection TimeSync in specific environments, and uninstalling Reflection TimeSync.

Note: Beginning in version 14.1, TimeSync is no longer available. If you have TimeSync installed on your system, it will be removed when you upgrade to 14.1.

Computers Upgraded to Windows XP

If you install Reflection TimeSync to a Windows 2000 computer and then upgrade that computer to Windows XP, Reflection TimeSync will no longer function due to the port conflict.

Reflection 10.x or Higher

In version 10.x, Reflection TimeSync is not available for installation to Windows XP.

Notice

This technical note is provided for informational purposes only. ATTACHMATE CORPORATION makes no representation or warranty that the functions contained in our software products will meet your requirements or that the operation of our software products will be interruption or error free. ATTACHMATE CORPORATION EXPRESSLY DISCLAIMS ALL WARRANTIES REGARDING OUR SOFTWARE INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Related:

7021829: Java Memory Management in Reflection X Advantage

Memory Use Overview

Attachmate Java applications rely on the Java Virtual Machine (JVM) to manage memory. The JVM allocates a pool of memory at startup and applications running in that JVM share that memory. Each Attachmate application that uses Java sets a maximum value for the size of the JVM memory pool. (This is also called the Java heap size.) The JVM can use memory, as required, up to this specified limit. As memory use approaches this limit, the JVM will recycle unused memory so that it remains available to applications running in the JVM.

When viewing memory used by a Java application, note the following:

  • All applications running in a JVM draw memory from the JVM memory pool, not from the Windows operating system memory. The memory used by all applications running in the JVM will never exceed the specified heap size for that JVM.
  • The JVM will recycle available memory back to the applications running in that JVM as needed, but this doesn’t happen until the memory use approaches the heap limit. Because of this, applications running in a JVM may not actually require all the memory reported in the Windows Task Manager at any given time.

In the Windows Task Manager, some Java applications create processes that use an application-specific image name. (For example Reflection X Manager and Reflection X Manager for Domains create processes listed under rxmgr.exe and rxmgrdomains.exe). Other applications (including the Reflection X Service) create processes that use java.exe as the image name.

If you also run other applications that consume a lot of memory, you may see performance issues. As Windows runs out of the random access memory (RAM) needed to run your applications, it uses something called virtual memory to compensate. When the available RAM runs low, Windows moves data from RAM to disk storage in a file called the paging file. Moving data to and from the paging file frees up RAM so your computer can complete its work, but reading data from the disk is slower than reading data directly from memory.

Memory Troubleshooting

On most systems, you will not need to modify your settings using any of the following troubleshooting techniques. The Reflection X Advantage default JVM settings provide sufficient memory to address the memory demands created by most X clients and servers. The default maximum heap size also ensures sufficient memory will be available on most systems for your Windows applications that don’t use this JVM. However, in some cases, contention for memory may prevent Reflection X Advantage applications from launching, or affect the performance of other applications on your system.

If your system’s memory is limited or fragmented, you may see one of the following indications that memory limits are preventing Reflection X Advantage applications from running.

  • In version 5.0 or later, you see a message saying “Application failed to start due to insufficient memory.”
  • In version 4.2 or earlier, the Reflection X Advantage application fails to launch, and the Windows Event log shows a message like the following:

“The description for Event ID (1025) in Source (RXAdvantage) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The event log file is corrupt.”

If memory limits prevent Reflection X Advantage from running, or you have determined that contention for memory is affecting performance of other applications, consider the following approaches.

Install Reflection X Advantage using the 64-bit Installer

If you have installed Reflection X Advantage using the 32-bit installer on a 64-bit system, and Reflection X Advantage applications fail to launch, reinstall using the 64-bit installer. The memory limit on 64-bit processes is much larger than the limit on a 32-bit processes.

Add RAM

The more RAM your computer has, the faster your programs will generally run. If a lack of RAM is slowing your computer, you may have success using the following adjustments. However, if none of these solutions result in better performance, adding additional RAM is the best solution.

Reduce the Maximum Memory Available to the JVM

Reducing the maximum memory limit for Reflection X Advantage (also called the Java heap size) can resolve the problem of Reflection X Applications failing to launch and can also increase the amount of memory available to other applications.

Note: This solution may affect performance in Reflection X Advantage. If memory is available Reflection X Advantage sessions cache images, the results of certain calculations, and other data. These actions can improve drawing performance and compression over low-bandwidth networks. If changing the Java heap size results in slow performance or X client failures, the value is probably set too low.

To change the maximum memory available to the Reflection X Advantage JVM:

  1. Close X Manager if it is running.
  2. Navigate to the Reflection X Advantage installation folder. (The default location for most installs is C:Program FilesAttachmateReflection).
  3. Locate rxmgr.alp (if you use standalone X Manager) or rxmgrdomains.alp (if you use X Manager for Domains) and remove the read-only attribute from this file. (Right-click, select Properties, clear the “Read-only” checkmark, then click OK.)
  4. Open the *.alp file in a text editor, such as Notepad.
  5. In the line that begins “alp.java.command.options=” locate the -Xmx setting. (The default value is -Xmx900m in version 5.0 and -Xmx1024m in version 4.2 and earlier.) Change this to a smaller value (for example: -Xmx700m).

Note: The *.alp files are replaced by newer, default files when you upgrade your Reflection X Advantage product. If memory problems reappear after an upgrade, see Technical Note 2530, “Installing Newer Versions of Reflection X Advantage If You Have Edited Rxmgr.alp.”

Increase Virtual Memory

You can increase the amount of virtual memory available by increasing the minimum and maximum sizes of the paging file.

This change can result in slower performance in Reflection X Advantage and other applications because of excessive disk paging. This solution may work for you if there are idle applications that can be paged out at times.

To modify virtual memory in Windows:

  1. Open the System Properties dialog box. (In Windows 7: Start menu > right-click Computer > Properties > Advanced system settings.)
  2. On the Advanced tab, under Performance, click Settings.
  3. Click the Advanced tab, and then, under Virtual memory, click Change.
  4. Click Custom size and set values for Initial size (MB) and/or Maximum size (MB).

Increases in size usually don’t require a restart, but if you decrease the size, you will need to restart Windows.

Add Additional Reflection X Advantage Nodes

If you are running Reflection X Advantage in domain mode and are experiencing memory contention on the domain node, you can experiment with using multiple nodes to help alleviate memory problems. Reflection X Advantage supports creating multiple nodes on the same system. This change effectively increases the allowed memory available to run sessions. You can also add nodes on remote systems. This increases both the number of CPU cores available and amount of available memory.

To add nodes to a domain, use the rxsconfig command line utility. For details, see “Set Up Domain Nodes” in the Reflection X Advantage product Help.

The number of sessions that a node can support depends on what kind of domain services are configured for the session (such as whether the session has a headless server running on the node) and how active the clients of the session are. You can monitor the load on your nodes using the Administrative Console. As an initial approximation, a session without a headless server can be expected to require about 1MB, and with a headless server about 25MB of heap space. For a 1GB heap (the default), this can be anything from about 30-1000 sessions. With a large number of sessions, resources such as cores and network bandwidth become a bigger concern.

Related:

7021821: Troubleshooting Reflection X Advantage Domain Connections

There are many reasons why a connection attempt may fail. After a failure occurs, a related message is shown in the bottom of the X Manager for Domains user-interface that may help identify the problem. For example:

Use the guidelines in the sections below to troubleshoot the failed connection. This note is organized into the following troubleshooting topics:

Additional detail regarding the problem may be available in log files created by both the X Manager for Domains and the Reflection X Advantage domain controller. For more information, see the Logging section below.

Network Firewall

Note: Beginning in Reflection X Advantage 4.0, predefined ports are used. If your environment has a network firewall, you need to upgrade to 4.0.

A network firewall cannot be running between any Reflection X Advantage 3.x or earlier domain nodes, including those running the X Manager for Domains and those running a Reflection X Advantage domain controller. This is because in domain mode, Reflection X Advantage uses random, ephemeral ports for communication between all of its components. If a network firewall is running, you may see one of the following messages:

  • “Failed to establish bidirectional communication with the domain controller.”

This message appears when the Reflection X Advantage domain controller cannot connect to the X Manager for Domains.

  • “Failed to connect to host <hostname>.”

This message appears when the X Manager for Domains cannot connect to the Reflection X Advantage domain controller. Besides checking for a firewall, ensure that the RX Service is running on the Reflection X Advantage domain controller.

Resolution: Upgrade to Reflection X Advantage 4.0 or disable the network firewall between the Reflection X Advantage domain nodes.

Note: Personal firewalls can be used if they work at the application level, as the Microsoft Windows Firewall does. For information about configuring Reflection X Advantage for use with the Windows Firewall, see Technical Note 2240.

Network Address Translation

Note: Beginning in version 4.0, you can configure Reflection X Advantage to work in a NAT environment.

Network Address Translation (NAT) must not exist between nodes running Reflection X Advantage 3.x or earlier. This is because Reflection X Advantage components provide IP address information to other Reflection components for communication, which would not be updated by the NAT tables. You may see the following error message:

“Failed to establish bidirectional communication with the domain controller.”

Resolution: Upgrade to Reflection X Advantage 4.0 or disable the Network Address Translation between nodes that run Reflection X Advantage.

Logging into a Reflection X Domain

When the X Manager for Domains is launched, the following login window displays.

2466_2.gif

User name and password fields

The input required depends on how the applicable Reflection X Advantage domain controller was set up. Multiple authentication mechanisms are supported and the default mechanism varies based on operating system.

For example, if the domain controller is running on a UNIX or Linux operating system, Pluggable Authentication Modules (PAM) is the default authentication mechanism, so your UNIX or Linux user name and password would likely be required. If the domain controller is running on a Windows operating system, Windows Domain (or Windows local) is the default authentication mechanism, so your Windows domain (or Windows local) credentials would likely be required. There are other authentication mechanisms as well, such as LDAP. If you are unsure which credentials to use, check with the domain administrator.

Domain field

The name or IP address of the host running the Reflection X Advantage domain controller should be entered here.

Note: Do not enter your Windows domain in this field.

Resolution: Follow these examples.

Example 1: Logging into a Reflection X Advantage domain controller running on a UNIX host

2466_3.gif

Example 2: Logging into a Reflection X Advantage domain controller running on a Windows host

2466_4.gif

Windows Domain and Local Authentications

When Reflection X Advantage is installed on a Windows operating system and a Reflection X Advantage domain controller is created, the default authentication mechanism is a Windows domain. The Windows domain configured by default will depend on how the Windows session was logged into before installing Reflection X Advantage.

For example, if the Windows session was logged into with a user from a domain (such as ‘attachmate’), the domain configured by the Reflection X Advantage domain controller will be ‘attachmate’. If the Windows session was logged into with an account local to the Windows machine, and the PC name is ‘rxa-dc.attachmate.com’, the domain configured by the Reflection X Advantage domain controller will be ‘RXA-DC’.

Understanding which domain has been configured for a Reflection X Advantage domain controller on Windows enables users to input the appropriate credentials.

Resolution: If you are unsure which domain has been configured, check with the host or Reflection X Advantage administrator.

Mixing Versions of Reflection X Advantage

All components in a Reflection X Advantage domain must be running the same version. If attempting to use the X Manager for Domains to log into a Reflection X Advantage domain running a different version, then you may see the following message:

“Version mismatch: Local version=<build number>, Remote version=<build number>.”

Resolution: Upgrade the earlier version of Reflection X Advantage to match the newer installation.

Machines with Multiple Network Adapters

If the Reflection X Advantage domain controller has more than one network adapter, there is a chance the wrong one may be utilized by the domain controller. The correct adapter can be configured by editing the rxs.conf file on the domain controller. In that file, there will be a few entries like the following:

wrapper.java.additional.1=<keyword=value>

wrapper.java.additional.2=<keyword=value>

wrapper.java.additional.3=<keyword=value>

Resolution: Add another entry, using the next number in sequence, and the keyword and value combination below:

wrapper.java.additional.4=-Djava.rmi.server.hostname=<IP address of correct network adapter>

After making this change, restart the RX service.

Domains on Linux

Note: This information in this section does not apply to version 4.0 or higher.

When you try to log on to a Reflection X Advantage domain, you receive a “Permission Denied,” “Failed to connect to domain,” or “Domain communication error” message.

Machines used with Reflection X Advantage must have a host name that is resolvable either through DNS or by an entry in a hosts file. Some Linux distributions place an entry in /etc/hosts that maps the machine’s host name to an address in the local loopback space (127.0.0.2 or 127.0.1.1, for example); using a local loopback address causes communication issues in Reflection X Advantage.

Resolution: Upgrade to Reflection X Advantage version 4.0, or remove entries in /etc/hosts that map the host name to a local loopback address, or add an entry containing the machine’s true IP address and host name to the hosts file.

Connections to Domain Nodes

You may be able to log into the domain, but when you try to start a session, a message like the following displays:

Failed to connect to node:127.0.0.2:22002

This message may display if there is a firewall blocking access to the node, or if there is a problem resolving the IP address (for example, in a NAT environment). If the problem is due to an incorrect or unusable IP address, starting in version 4.0, an alternate address can be configured as a fallback. The alternate address can be created using the rxsconfig command line utility or the X Administrative Console.

Request Technical Support

If you have worked through this technical note and are still unable to connect, contact Attachmate Technical Support. For information about contacting Attachmate technical support, see http://support.attachmate.com/contact/.

If you are asked to send in a log file, follow the steps below.

Logging

Logs are generated for the X Manager for Domains, the Reflection X Advantage domain controller, and the Reflection X Advantage domain nodes. See the log locations below, along with information about how to increase logging if needed..

Note: All log files in version 3.0 and earlier are named output.txt. Beginning with version 4.0 loging information has been broken down into a larger number of files, each with a descriptive name such as “xmanager.log” and “domain.log”.

X Manager for Domains:

Windows:%USERSPROFILE%attachmaterxlogs

UNIX:~/attachmate/rx/logs

Reflection X Advantage domain controller:

Windows:%ALLUSERSPROFILE%attachmaterxlogs

UNIX:/opt/rxadvantage/logs

Sometimes a higher level of logging is required than what is provided by default. You can enable debug logging by using the file provided here for download from the Attachmate Download Library: log.xml.

To use the log.xml file, follow the steps below.

  1. Download and save the file into the appropriate directory on each system running Reflection X Advantage that you want to increase debugging on.

Windows – Reflection X Advantage standalone installation:

C:Program FilesAttachmateReflection X Advantage

Windows – Installed with Reflection X 2011:

C:Program FilesAttachmateReflection

UNIX:/opt/rxadvantage

  1. Edit this file entry to specify the location and name for the debug log:
<param name="file" value="path/file_name"/>

Windows Example:

<param name="file" value="c:/path/rxa.log"/>

UNIX Example:

<param name="file" value="path/rxa.log"/>
  1. Restart the X Manager for Domains and RX Service on the domain controller so that the new logging will take effect.

Note: All Reflection X Advantage logging will be redirected to the files specified. Once the debug log has been taken or the connection problem resolved, we recommend you remove the log.xml file and restart the appropriate Reflection X Advantage component(s).

Uploading

To upload the log file, see https://upload.attachmate.com/.

Related: