Forums

bsleys
bsleys
Offline
Resolved
0 votes
I've tried both ClearOs 6.6 with OpenLDAP and ClearOS 7.1 with Samba Directory and the follow problem persists.

Do a domain login with a user either as a regular user or domain admin and run Google Chrome Browser.
Connect the browser to your gmail account.
Close the browser and restart it.
Google Chrome require you to relogin to your account your username ie e-mail address is remembered but not your full credentials.

If you login to a local account the browser remembers your credentials. Domain logins from windows 7 and 8 also remember the credentials fine.

The above may seem like a minor inconvenience but it's just a easy quick way to demonstrate the problem. The credential problem rears is head in many places for example Visual Studio also require continual re-entry of credentials and can't publish an app at all.

Any help finding a solution would be greatly appreciated as I have customers what will need to eventually upgrade their desktops to win 10.

Bob
Thursday, October 15 2015, 03:55 PM
Share this post:
Responses (8)
  • Accepted Answer

    bsleys
    bsleys
    Offline
    Wednesday, October 21 2015, 05:59 PM - #Permalink
    Resolved
    0 votes
    The chrome account issue doesn't display any bugs or erorrs but I have found one place that does display an error massage that I believe linked to the problems. Windows error below

    The computer must be trusted for delegation and the current user account must be configured to allow delegation. (Exception from HRESULT: 0x80090345)

    Bob
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 21 2015, 05:24 PM - #Permalink
    Resolved
    0 votes
    I mis-read your post and I agree. I don't think it is anything to do with samba, and I won't be able to help further.
    The reply is currently minimized Show
  • Accepted Answer

    bsleys
    bsleys
    Offline
    Wednesday, October 21 2015, 04:44 PM - #Permalink
    Resolved
    0 votes
    its not a chrome/win10 bug since logging into a local account it works fine. Also I believe the same issue is causing problems in other places I just choose the chrome login as a simple way to demonstrate the problem.
    The reply is currently minimized Show
  • Accepted Answer

    Bernd
    Bernd
    Offline
    Wednesday, October 21 2015, 04:36 PM - #Permalink
    Resolved
    0 votes
    I'm not quit sure I got the problem right, but there are still a lot of google chrome/ win 10 related bugs...
    The reply is currently minimized Show
  • Accepted Answer

    bsleys
    bsleys
    Offline
    Wednesday, October 21 2015, 03:04 PM - #Permalink
    Resolved
    0 votes
    I could be wrong but I don't think this an issue about file sharing. I didn't have flexshares installed on the test ClearOS 7.1 server initially but I just installed it and setup a test share. From a win 10 machine using a domain account I can see and add/edit files in the new share just fine. However I don't see and can't access the users home dir. I'm guessing the setting is missing in the smb.conf for that which I'll look at next.

    Bob
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 15 2015, 07:18 PM - #Permalink
    Resolved
    0 votes
    If it is commented out it defaults to "445 139" which should not stop anything from working. I am surprised it does not exist on 7.1. I'll need to check on my play VM, but there are reports of needing to add 445 to get simple sharing to work with Win 10.
    The reply is currently minimized Show
  • Accepted Answer

    bsleys
    bsleys
    Offline
    Thursday, October 15 2015, 05:06 PM - #Permalink
    Resolved
    0 votes
    The line doesn't exist on the ClearOS 7.1 box but does on the ClearOS6.6 box. If I comment it out on the 6.6 box will it mess up the win7 desktops?

    Note the 6.6 is our may box and 7.1 is currently for testing.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, October 15 2015, 04:25 PM - #Permalink
    Resolved
    0 votes
    Can I just check that in /etc/samba/smb.conf you have either "smb ports = 139 445" or you have commented out the line? Apparently simple file sharing does not work with Win 10 and "smb ports = 139".
    The reply is currently minimized Show
Your Reply