Idru
Level 3
Joined 14 years ago
User Profile
User Widgets
Contributions
Re: Backup Exec 2010 - Linux Remote Agent logon failure
Thanks for the reply, Like I said in the post, I can telnet to the server, no problem. The problem occurs on selection. As far as I can see from posts etc, logon account should be just username, not username@LINUXSERVER correct? Nothing is output in log still, so it's not an actual authentication problem. Also, the fact that it shows up as "Failed to log on to Microsoft Windows" show that it doesn't actually attempt to authenticate to the agent. I find this odd.. :)208Views0likes0CommentsBackup Exec 2010 - Linux Remote Agent logon failure
Hello everyone, I've never set up a Backup Exec agent for Linux before, but there's a first time for everything. Got the agent installed, and set up. It publishes to the mediaserver and is listening on port 10.000 on the agent server(checked with netstat locally aswell as a telnet connection from media server). I'm using root as logon account. When setting up backup job I get the "Failed to log on to:"-error. However it seems it doesn't actually try to connect. "./beremote --log-console" doesn't output anything when I try to set up the job, and the error is saying "Failed to log on to Microsoft Windows" I should mention that the servers are not on the same lan, and connecting via wan, but all ports that should be opened, are open at both ends. Tried setting the logon account as both restricted and unrestricted, aswell as username 'root' and 'root@servername.FQDN' Agent key is installed, off course ;) Any suggestions much appreciated. /aageBE 2010 - Backup of other domain
Hello, We have a domain - let's say main.local - where backup is running just fine on all agents. We have an IPSEC-tunnel towards one of our sister companies - second.local - and are setting up backup for the second domain. From the backup server on main.local I've installed agents just fine on the second.local-servers, two-way trust between domains is set up and the backup-operators to log on as batch job on all policies affecting servers. I even tried setting the administrator from main.local to log on as batch job on second.local. Still, I get error "Failed to log on to: second.local" when trying to set up the backup-job and expanding domain second.local. All my searching for solutions seem to end up with either "log on as batch" missing or two way trust missing. However this is all in place, and the agents are installed and running. No events for the logon is registered on either main or second, so it's as if the logon-attempt doesn't happen. Trying to browse etc between the two domains works just fine. Anyone have any ideas?238Views0likes4Comments