You are viewing limited content. For full access, please sign in.

Question

Question

Web Access - Set access rights, "domain account not found" immediately after finding the domain account

Web Client
Updated February 19, 2015
asked on February 12, 2015 • Show version history

In web access I get the message "domain account not found" after selecting Add and choosing the domain account. I literately just searched for and found the domain account, how can it not be found? This happens with all domain accounts and only in Web Access. Laserfiche client works with the same accounts without a problem.

 

 

Update: Is there an issue with Domains that have a pre-Windows 2000 domain name? For example the domain is company.com but the pre-Windows 2000 domain name is CPY and the user logins are CPY\username instead of company\username?

0 0

Replies

replied on February 18, 2015

Hey Chad,

 

I imagine the details contained within your update are the culprit here.  If the server is looking to find domain accounts within a certain domain, but the actual domain has a different name, then surely it won't find the accounts properly.  I'm no expert with Active Directory, specifically how it pertains to the different versions of Windows OS, but if there's a way to resolve the differences in domain name, I'd look into that as my first troubleshooting step.

 

If you continue to have trouble even after resolving the domain names, I'd recomend opening up a support case for additional troubleshooting.

0 0
View 1 previous reply
replied on February 18, 2015

Thanks Rob

I think they want to pre-Windows 2000 configuration in order to shorten their domain name. It appears to be common with school districts. I do see that when adding a user in the client it properly uses the pre-Windows 2000 prefix. It is hard to tell exactly what is happening with the web version since all the fields from the client are not available.

0 0
replied on February 18, 2015

Kinda taking a shot in the dark here, but if they'd like to use a shorter domain name, aren't they able to make that change across the board?  If the domains have the same name, then you can simply set it up to find the single domain name and hopefully have the accounts be found easily.  Is there a reason that they need to keep the full domain name for post-Windows 2000?  

0 0
replied on February 19, 2015

My guess is they need it for DNS reasons. The short name allows users to login easily while the long name (which is the same as their website) allows them to match their public dns entries with their internal dns entries. The only way I can verify that the short name is even the cause is to install a new domain controller in a test environment. Even then it is not a problem with the DC, it is something going on with the web version of the client. If the web version used the same query as the client it would find the user on these types of domains.

0 0
replied on February 19, 2015

Your best bet would likely be to take this to our Support team.  There's no good technical reaason as far as I know of that would cause the same account to be found in the desktop client and not found in the web client.  If you're able to figure it out, please make sure to post your solution here to help others in the future who run into similar issues!

 

Thanks and good luck, Chad!

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...