0xe000fe29 - Authentication failed on connection

Hi,
I’ve a problem connecting to a remote agent backuping files or system state data. The Backup Exec Server Version 12.5 incl. all actual patches. And the remote agent has been reinstalled several times. Anyway we did a lot of troubleshooting as recommended in these KB article until I found a workaround for the problem. It works, when we use directly the ip address in the job, I case of NetBIOS or FQDN name.

http://seer.entsupport.symantec.com/docs/277422.htm
http://seer.entsupport.symantec.com/docs/284886.htm
http://seer.entsupport.symantec.com/docs/302358.htm

BENGINE: [05.25.09 16:05:03] [0000] [2364] 05/25/09 16:05:03 Updating status for: 'Testsicherung RMTS01' (0x18 0x0)
BENGINE: [05.25.09 16:05:03] [0000] [2364] 05/25/09 16:05:03 Status for: 'Testsicherung RMTS01' updated
BENGINE: [05.25.09 16:05:03] [0000] [2364] 05/25/09 16:05:03 BackupJob::MergeBEVSRJobLogsIfNecessary: No VSR log file found, no merging necessary
BENGINE: [05.25.09 16:05:03] [0000] [2364] 05/25/09 16:05:03 Ending job 'Testsicherung RMTS01' with error status (-536805847)
BENGINE: [05.25.09 16:05:03] [0000] [2364] 05/25/09 16:05:03 Job thread terminating

http://seer.entsupport.symantec.com/docs/315820.htm

BENGINE: [05.25.09 16:41:42] [0000] [7008] 05/25/09 16:41:41 NDMPAgentConnectorSmiley FrustratedetupConnection(): Data Server = RMTS01
BENGINE: [05.25.09 16:41:42] [0000] [7008] 05/25/09 16:41:41 Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000
BENGINE: [05.25.09 16:41:42] [0000] [7008] 05/25/09 16:41:41 ndmpConnectEx: Querying the neighbour advertisement cache to discover information on 'RMTS01' ...
BENETNS: [05.25.09 16:41:42] [0000] [7656] 05/25/09 16:41:41 NRDS API - client connected.
BENETNS: [05.25.09 16:41:42] [0000] [5892] 05/25/09 16:41:41 Connecting to BE Database.
BENETNS: [05.25.09 16:41:42] [0000] [5892] 05/25/09 16:41:41 Successfully connected to BE Database.
BENETNS: [05.25.09 16:41:42] [0000] [5892] 05/25/09 16:41:41 Reading agent database record for rmts01.domain.local.
BENETNS: [05.25.09 16:41:42] [0000] [5892] 05/25/09 16:41:41 Found agent record 3 for rmts01.domain.local.
BENETNS: [05.25.09 16:41:42] [0000] [5892] 05/25/09 16:41:41 Disconnected from BE Database.
BENETNS: [05.25.09 16:41:42] [0000] [7656] 05/25/09 16:41:41 NRDS API - client disconnected.


http://seer.entsupport.symantec.com/docs/284155.htm

WORKAROUND:
http://seer.entsupport.symantec.com/docs/304321.htm
Backup the server by user defined selection by IP address work fine
This all sounds to be a DNS problem. But all DNS resolution are OK. We do have the problem only on one server, all other work fine.
Question: Any idea, what can be the problem? Why does it work by using the ip address directly?

Thanks for any assistant
Regards, Thomas

6 Replies

We use IP addresses, and this

We use IP addresses, and this was based on what a tech at Symantec said was better than using name resolution. Using an IP address (as long as it wasn't DHCP-assigned) would ensure that we wouldn't have any issues when connecting to agents.
Using this method, we haven't had the error you're getting. If it's DNS, check your DNS server to make sure you don't have duplicate entries. Have you also tried to put that server's IP address/name into the hosts file to see if that clears the issue up?

BELogonUser: beclass::IsThisMe() returned error: 87

Thanks for answering Craig,
Yes, it works as a workaround with ip addresses. Adding the ipaddress into hosts or lamhosts file does not cleanup the issue.

If we logging the issue on the agent site, we get the typical password error: 87 if using NetBIOS or FQDN name it fails twice.
[10788] 05/25/09 18:03:46 ndmpRun: Control connection accepted : connection established between end-points 192.168.120.12:10000 and 192.168.120.15:1438
[4580] 05/25/09 18:03:46 BELogonUser: beclass::IsThisMe() returned error: 87
[4580] 05/25/09 18:03:46 LogonType set = [LOGON32_LOGON_INTERACTIVE][0x2]
[4580] 05/25/09 18:03:47 LogonUser failed: Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort.
[4580] 05/25/09 18:03:47 LogonUser failed for user: RM\Administrator
[4580] 05/25/09 18:03:47 BELogonUser: beclass::IsThisMe() returned error: 87
[4580] 05/25/09 18:03:47 LogonType set = [LOGON32_LOGON_INTERACTIVE][0x2]
[4580] 05/25/09 18:03:47 LogonUser failed: Falscher Parameter.
[4580] 05/25/09 18:03:47 LogonUser failed for user:
[4580] 05/25/09 18:03:47 @@@@@@@MyCloseSocket called with sockfd = 1160(0x488) retval = 0

... and with the IP address it works ..but it fails first with the same error 87 too.
[10788] 05/25/09 18:09:02 ndmpRun: Control connection accepted : connection established between end-points 192.168.120.12:10000 and 192.168.120.15:1500
[13928] 05/25/09 18:09:02 BELogonUser: beclass::IsThisMe() returned error: 87
[13928] 05/25/09 18:09:02 LogonType set = [LOGON32_LOGON_INTERACTIVE][0x2]
[13928] 05/25/09 18:09:02 LogonUser(LOGON32_LOGON_INTERACTIVE-0x2) success
[13928] 05/25/09 18:09:02 Successfully impersonated RM\Administrator
[13928] 05/25/09 18:09:02 WhoAmI( ) reports: RM\Administrator
[13928] 05/25/09 18:10:38 @@@@@@@MyCloseSocket called with sockfd = 1220(0x4c4) retval = 0
[13928] 05/25/09 18:10:38 dataAcceptConnection : Data Connection information: A connection was established between end-points 192.168.120.12:3466 and 192.168.120.15:1519.

User ID/Password in AD is correct, but what does the agent really receive?
We are backuping 3 servers remote, which works fine without error 87 using host names.
All remote agents aue on the same level.

Thanks for some more assistant or hints
Regards, Thomas

IP address workaround - worked and then stopped...

HI all.  I have been plagued by the same issue for more than a month now.

Environment:  Server 2003 Standard R2 32-bit running Backup Exec 12.5, updated.

I tried removing and reinstalling the remote agent, with the necessary restart, and the problem remained.  Then, myteriously, it worked!  I then moved my backup operation from my workstation to an old Dell server to take advantage of the PCI-X slot's performance and the trouble started again.  I've tried creating new service accounts, trying the existing Administrator account, undoing that and going back to the original service account...  It has worked on the "new" server, by the way.

I'm backing up data from three servers:  domain controller (also SAN host and file server), Exchange server and SQL server.  Only the domain controller is giving me trouble.  When the job fails, the dialog box that appears gives the following information:  "The job failed with the following error: Authentication failed on connection to the server. Make sure that the user account has the appropriate permissions and that the password was typed correctly."



In the job log under Completion Status:

"Final error: 0xe000fe29 - Authentication failed on connection to the server. Make sure that the user account has the appropriate permissions and that the password was typed correctly.
Final error category: Security Errors

For additional information regarding this error refer to link V-79-57344-65065"



In SGMon's logging, I see:

"BENGINE: [04/06/09 11:41:12] [3596] ERROR: 4 Error: Connection has not been authorized"



I created a user-defined selection using the server's IP address and it worked.  I ran a few test backups ok, and then I edited a selection list and ran another backup - failed.  With the same details.

I'm really at a loss here.  I can't decide if it's domain security that's not playing ball, the network cabling that's up to maggots or if it's the backup software.  If you can make some suggestions, I'll be grateful.  If you need more information, please ask.  Thanks in advance.

IP address workaround - worked and then stopped...

By the way, if I enable user-share selections in the BE console and select the data using the shared resource names, the backup works.  This was the case previously when the problem first surfaced.  I had successful backups this way, until I was able to reinstall the agent and reboot the server.

Therefore:
  • Can it be that the agent is not functioning properly, and how would I analyse this?
  • It doesn't seem likely that DNS or NETBIOS name resolution is to blame, otherwise backups would fail when using share-selection too, wouldn't they?

BELogonUser: beclass::IsThisMe() returned error: 87

Thanks for you imput, TQPG
It sounds to be the same problem, then I have. But I don’t have a solution for it, yet. Except the workaround above, which still works in my case.
In an other case with simular connection problems, but not the same one, I could solve the problem by updating the network device driver. But I could not test it yet, if it will works in this case too.
Anyway, I asume the problem is on the remote agent side and any advise to the BELogonUser returned error: 87 and how it works may welcome here.
 

ip address workaround


Unfortunately we have a very similar issue, however there server that is giving us a problem is the web front end of our SharePoint server farm. When using the share point agent, and entering the web server ip address of the web server backup exec resolves this to Net Bios name which negates this as a usable work around.

I have added both the net bios name and fqdn into the hosts file on the backup server to no avail.