Jump to content

jon.boehlke

Members
  • Content count

    3
  • Joined

  • Last visited

  • Days Won

    1

jon.boehlke last won the day on April 11 2012

jon.boehlke had the most liked content!

Community Reputation

3 Neutral

About jon.boehlke

  • Rank
    Occasional Forum Poster
  1. To determine the necessary dependencies first run: rpm -qpR Linux_Client-7_7_100.rpm The 32 bit binaries are locate in /lib. For RHEL6 X86_64 server install the following: yum install glibc.i686 yum install libgcc.i686 Install the retrospect client. rpm -i Linux_Client-7_7_100.rpm
  2. Roxio states the RHEL 5 is supported by Retrospect 7.7 for Windows. When will there be support for a linux client for RHEL6 X86_64? To follow up: I used yum to install the dependencies by specifying i686 (glibc.i686). Retrospect client in successfully installed on RHEL6 x86_64.
  3. Trying to use Retrospect client for linux on X86_64 RHEL.

  4. Retrospect 7.7 client for linux does not support RHEL6 X86_64. The dependencies for the .rpm are located in paths not found by the client. Any thoughts on a workaround? Will Roxio keep up with development of new RHEL clients?

  5. It is evident that UDP/TCP ports 497 are not the only ports Retrospect 6.5 uses to communicate with Clients. When utilizing piton multicast to locate clients on the subnet, Retrospect clients communicate back to the server listening through random UDP ports such as 1591. This is easily seen by running netstat before and after trying to add new clients. Each time an add is attempted using the multicast the ports that the server is listening on change: for example; from 1591 to 1595. Because the firewall settings on Windows 2003 server are static it is not possible to select ports to leave open for the server to listen for client responses. Is there a way to set a fixed port for server to listen on? Or maybe some other workaround?
×