yesterday I updated a UCS 4.2 to 4.3 and since then shares on a Windows Server 2012R2, which acts as AD client, are not accessable anymore.
Event ID 4625 appears in the event log:
Fehler beim Anmelden eines Kontos.
Antragsteller:
Sicherheits-ID: NULL SID
Kontoname: -
Kontodomäne: -
Anmelde-ID: 0x0
Anmeldetyp: 3
Konto, für das die Anmeldung fehlgeschlagen ist:
Sicherheits-ID: NULL SID
Kontoname: user
Kontodomäne: domain
Fehlerinformationen:
Fehlerursache: Bei der Anmeldung ist ein Fehler aufgetreten.
Status: 0xC000005E (<--- bedeutet, keine Anmeldeserver verfügbar)
Unterstatus:: 0x0
I removed the server from the domain once and added it again, which works without problems, but SMB is still not available.
Any (quick) help is welcome and many thanks in advance.
Ich habe ein ähnliches Problem.
Der Windows-Rechner ist im Explorer nicht mehr unter \\192.168.0.x zu erreichen, ebenso die entsprechende Freigabe. Per ping, nslookup und Tracert ist alles ok. Durch Zufall habe ich jedoch festgestellt, dass der Zugriff über den Namen (\\Servername) funktioniert. Das kann aber nicht die Lösung sein.
allgemein wird hier Englisch bevorzugt, deshalb die Antwort in Englisch- wenn das nicht geht, nochmal melden.
Is your UCS Server a virtual machine? Or does it provide virtualisation with the UVMM App?
It sounds indeed weird, beeing reachable by ping etc but the Shares only with name. So what does your client says about nslookup <servername>?
Go on the UCS-command line and check the output of the following commands:
Just to make sure:
You are on a windows client (who ist joined to the UCS-Domain) and you are trying to access a share which is configured on a Windows2012 server?
Or are you trying to access an UCS share from your win 2012?
Are these original values or did you hide some parts here?
When you try to access are there any strange things logged at the same time in /var/log/samba? Verify the time frame to find entries.
@JensB I doubt it is related to the original topic.
You can access the share by name, but not by IP. This points to some sort of name resolution or IP configuration. In case this is still valid, I would suggest to create a new topic so we do not get confused here.
I try to access shares on the Windows 2k12R2 server from any possible client outside the domain.
SMB from linux to Windows fails. Same with Windows 7 clients.
The values you mentioned are copied from the eventlog on the W2k12R2 server without modification.
Nothing is logged in any log-file within /var/log/samba/.
I can access the share if I use a local user of this server, but not with any domain-user.
After a timeout, I get this error-message:
Sorry, currently no idea. I assume there is no firewall in-between anywhere?
Another question which came into my mind:
Is it at all valid to access Windows-Servers from a machine which is not part of the AD-Domain? I am not sure about this… you might be right it SHOULD work…but…
Sooo, @codedmind and @JensB can access their shares via the DNS hostname/FQDN of the server but not via the IP. @onex: Your screenshot also shows only the IP of the server. Did you try to connect via the DNS hostname/FQDN? I’m asking, because accessing via DNS hostname/FQDN is done via Kerberos authentication (at least Kerberos is preferred) while accessing via IP address has to use NTLM for authentication (because Kerberos requires a working DNS resolution). So it might acutally be, that NTLM has some problem, while Kerberos does not (see also https://help.univention.com/t/8373/).
Of course, that’s not a solution, but it might get us closer to the actual problem.
I have restored the backup of UCS 4.2-3. On this is the UCR-Variable on DC-Master samba/ntlm/auth empty.
The problem occurred when connecting from a Windows PC to a Windows share.
I have 3 servers:
1 - Univention server (VM) as DC
1 - Windows Server 2016 (VM) as member
1 - Windows Server 2008 as member
I’m having issues between windows server, i cannot acess 2016 server shares from 2008 using ip address, only name.
I’m having issues when connection from any computer via Remote desktop to Windows Server 2016 (some times don’t connect other times takes to long), don’t have issues when connect to 2008
