[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1020
  • Last Modified:

Backup Exec 12.5 setup B2D Folder over network - The Specified User Does Not Exist

I have been trying to set up a B2D Folder on one of my servers. I keep getting the error The Specified User Does Not Exist i have followed the Symantec advice articles but they do not fix my issue.

I have had this working before but one of my servers died & i had to do a full re-install to get it working again & now it will not work.

Please help
0
James Wilkinson
Asked:
James Wilkinson
  • 4
  • 4
1 Solution
 
.Commented:
Hi, Focus on the Backup Exec services account. Are you using the LSA ? are you used the format ADdomainName\Username ? if it is not already the case try switching to the domain administrator account for the BEW services to test this theory.
0
 
James WilkinsonNetwork ManagerAuthor Commented:
When i open the services logon tab the account set is .\Administrator i changed this to ADDomainName\Administrator & restarted all services on both server & client (Both are Servers) & this still persists.

Anymore ideas & a big thankyou

This is frustrating as it seems a common issue but the symantec published fixes do not seem to work for me.
0
 
.Commented:
.\ is good enough actually. Is the target server joined to the domain ?
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 
James WilkinsonNetwork ManagerAuthor Commented:
Yes it's a member server. I have a remote agent service running on both too does this sound like it is related?

I have also tried adding the network location as a shared network drive in my computer but Backup Exec won't allow me to create a B2D folder using G:\ as a directory path it only allows an \\ type of URL
0
 
.Commented:
Usually it means the service account does not exist on the target computer, in your case though you are trying to set up a B2D on a member Server so I do not think that counts based on what you have said. Its common to get this if you are trying to B2D on a NAS box or a machine running Samba. Can you access the UNC path of the share via windows explorer ?
0
 
James WilkinsonNetwork ManagerAuthor Commented:
Yes can resolve both servers in every way using DNS Lookup & can navigate vie windows explorer. I'm trying to setup the B2D on the server machine. So the files will be backed up to a location on the member server. My server is 32bit & my file server is 64bit both server 2003.
0
 
.Commented:
Hi, I have a lot of boxes running all different versions of BEW and I just can not emulate this so other than what I have said I am not sure. Its the kind of thing I prefer to actually look at :(
0
 
James WilkinsonNetwork ManagerAuthor Commented:
Update

I have just tried to search for my server by clicking add a B2D folder & clicking browse. I navigated to my server which i want to connect to & it said that a connection to this server could not be established.

Its strange i can ping it & dns is all correct i can even navigate the folders by using the unc path in windows explorer.

If you ve had anything like this or you have knowledge of what this problem could be please share with me thanks

0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now