The GoTo Community is currently experiencing some technical issues affecting new posts and comments. You may need to reload the page you are on before you can post a comment. We are actively working with our service provider and apologize for the frustration.

Forum Discussion

Active Contributor

7 years ago

4320 error on user login

I have a domain user (unprivileged) that I have added to the access list for their PC as follows: This has always worked in the past for other users but now when the user tries to login they ...

Retired GoTo Contributor

7 years ago

LockonCC You can still dictate the type of access they receive even if you make that user an Admin. If you're having trouble still, I would call into support so they can walk you through the necessary settings.

Active Contributor

7 years ago

Thank you... I understand that you are trying to help but we don't just grant Admin rights and then try to control their access - it's the other way around.

Still looking for a solution for an unpriv'd user...

Thanks

Sunil

LockonCC
Active Contributor
7 years ago
ok, so for anyone who comes to this thread - the issue was a glitch in the Matrix. I reviewed the permissions in logmein (posted above) a few times when I posted the original post.... Now (several hours later) I sat down to review and debug and - guess what? - logmein had no permissions refined at all for that user - in other words they either never got saved or they were deleted from the logmein server for some reason.

I recreated the logmin permissions and now all is well.

Thanks
- AshC
  Retired GoTo Contributor
  7 years ago
  LockonCC Thanks for the follow up!
  - Daver99
    New Contributor
    7 years ago
    Along this same thread, I just did an install on a pc in our office and immediately had a chain of problems - which I didn't get on other pc's here.
    1. After the install, the setup did not recognize the PC as one that uses office 365 credentials (no dedicated local account) - -and hence did not present the option to set up an access code
    -->I had to workaround this by manually creating a LogMeInRemoteUser admin account <--
    2. Trying to then connect generated the above 4320 error. I then had to manually grant "everyone" full access in the logmein control panel options
    ->These extra permissions are not necessary on the other office 365 pc's in the office. I'd like to understand why this one was different? Any ideas?
    
    DR