Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About axian

  • Rank
    Occasional Forum Poster
  1. axian

    Linux Client No Longer Seen

    Nate, You gave me the fix. I had to remove the client from the server and add it again. I didn't think it was necessary, but thank you for the help.
  2. axian

    Linux Client No Longer Seen

    The problem continues even if I bring down the alias, restart the service, and if I use retroclient -ip. I'm out of ideas except to call retrospect's tech support.
  3. axian

    Linux Client No Longer Seen

    I have tried reinstalling the client several times while making sure all retrospect files are deleted. The client runs on the adapter (eth0) -- not the alias (eth0:0). Installing another adapter would be the same logical setup so I don't see how that would solve the problem.
  4. We have a Mac OS 9.2.2 as our backup server with Windows, Macs, and one Linux client. Everything has been working and the Linux (RH 8) was seen in Retrospect. We recently changed our internal IP addresses to a different range. After the change was successful, Linux was no longer seen in Retrospect on the Mac. Both computers can ping each other as they are in the same subnet. The Linux box has one NIC with an internal address and a public address as an alias. I have tried reinstalling retrospect on Linux and I have tried /usr/local/dantz/client/retroclient -ip x.x.x.x to bind it to the internal address. I have also turned off iptables to make sure it wasn't a firewall issue. I've had no success. I cannot add the client by address as we do not have the license for that feature. Any help would be much appreciated.
  5. axian

    OS X 5.1 and 506 error from linux client

    I have tried reinstalling the package several times with RPM and the tarball and the results never change. There was one time when I reinstalled the package from RPM that everything worked fine and the system got backed up. But the next day I had to reboot the Linux box and then Retrospect could no longer connect because of error 506. There is nothing special about this box.
  6. axian

    OS X 5.1 and 506 error from linux client

    Quote: coult said: Fixed - my linux client has two ethernet interfaces. I explicitly specified the correct address using retroclient -ip #.#.#.# and now all is fine. I have this same problem and when I issued retroclient -ip #.#.#.# nothing changed and I got the message that retroclient is already running. In fact, I can't use any of the retroclient flags for some reason. I'm running RH 8.0 and if anybody could help me, that would be wonderful.