Forum Discussion

SuperBeta's avatar
SuperBeta
Level 3
10 years ago

Backup Exec hangs when expanding Server in selection list

I am trying to get the backup exec agent installed and working on a domain controller to back it up with Backup Exec 2010 R3 SP4. The Media server (we will call it Server1) and the remote server (we ...
2010
Agents
Backing Up
Backup and Recovery
Backup Exec
Error messages
Troubleshooting
Windows Server (2003-2008)
  • SuperBeta's avatar
    SuperBeta
    10 years ago

    Just found my solution! Couldn't have done this without the help of the people on this site. Thanks so much for taking the time!

    The solution:
    On the client server, I was running Cerberus FTP which happens to use port 10000 for it's remote administration connection. As you may know, RAWS uses port 10000 for communication as well. Newer versions of this ftp software seems to use port 10001, but I'm not 100% certain this is always the case. It may check during installation if another application is using port 10000 and choose a different port. In this case, I had installed Cerberus first, and then added the RAWS client later, so if there was a port check, it didn't happen. It seems very clear that the Symantec product doesn't do any checks of this type. After I changed which port Cerberus was using, the RAWS agent started working and I could expand my selection list for that server without issue. 

    https://www.cerberusftp.com/support/help/remote_settings.html

    This simple issue has taken quite a bit of my time to figure out. It was an easy fix, but it would have gone a lot faster if I would have taken the time to list all of the services and 3rd party software I had running on the server and looked at those earlier on in the process. 

     

     

SuperBeta's avatar
SuperBeta
Level 3
10 years ago

Just found my solution! Couldn't have done this without the help of the people on this site. Thanks so much for taking the time!

The solution:
On the client server, I was running Cerberus FTP which happens to use port 10000 for it's remote administration connection. As you may know, RAWS uses port 10000 for communication as well. Newer versions of this ftp software seems to use port 10001, but I'm not 100% certain this is always the case. It may check during installation if another application is using port 10000 and choose a different port. In this case, I had installed Cerberus first, and then added the RAWS client later, so if there was a port check, it didn't happen. It seems very clear that the Symantec product doesn't do any checks of this type. After I changed which port Cerberus was using, the RAWS agent started working and I could expand my selection list for that server without issue. 

https://www.cerberusftp.com/support/help/remote_settings.html

This simple issue has taken quite a bit of my time to figure out. It was an easy fix, but it would have gone a lot faster if I would have taken the time to list all of the services and 3rd party software I had running on the server and looked at those earlier on in the process.