Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - roliver

Pages: [1]
There are a bunch of Security updates today, many concerning Kerberos.
Are these fixes?
If they are available, are they tested and should I apply them?

Thank you,


Zentyal Development Edition 7.0
Antivirus 7.0.2
FTP 7.0.0
HTTP Proxy 7.0.2
Intrusion Prevention System 7.0.0
Mail 7.0.2
Mail Filter 7.0.0
RADIUS 7.0.0
Virtualization Manager 7.0.1
Web Mail 7.0.0

System Updates - The system components are up to date.
All servers are running in XOA/xcp-ng environment on Dell R720
Primary Domain Controller Zentyal
Secondary Domain Controller is Zentyal also
File Server is a separate Ubuntu 20.04
Windows devices are Windows 10 Pro 22H2 OS Build 19045

Apologies, I'm fairly new to the Ubuntu/Linux world and I am not the original Zentyal installer/configurator here.

I have read Re: AD Stop Working on Windows 11 22H2,35474.msg115368/topicseen.html#msg115368

I just want to inform you that Ubuntu has released the packages that fix the Windows 11 bug with Samba, so if you did not apply any of the proposal workarounds, you just need to update your system packages.

Best regards, Daniel Joven."

This question may answer my issue as I could be confused.

When you say "you just need to update your system packages" do you mean from the Zentyal Software Management\System Updates page within Zentyal, or are we talking about from the OS level?

Details of the issue.

December 16, 2022 late in the afternoon a user complained that they couldn't get to their departmental shared folder. I was able to access it with no issue. Had user reboot PC and upon reboot they could access the file share again.

Monday December 19, none of my users could access File Server by name. \\servername.
\\servername, prior to Dec. 16 would present all shared folders that user has access to.

I was still able to access \\servername and all shared folders on the Ubuntu File Server until mid-day. I then tried \\ip.address and was able to access all shared folders on the file server.
I checked DNS by using test computer that had been offline for awhile which was able to authenticate to the domain with standard domain user.
DNS appeared to be working fine and still appears to be working fine. Windows RSAT DNS tool reports refreshed Timestamps as of this morning.

When I checked package updates I noticed the SMBclient had been updated on the File Server.
I ran package updates on the file server, with no change.
I rolled back to smbclient 14.6, with no change.
I rolled back to I believe, smbclient 14.3 with no change.
I backed up the files from all of the shares on the server and rolled the server back to a snapshot from Oct. 13, 2022 . . . this had no change.
Since I know the File Share was working as expected on December 15, logic tells me, if the issue was with the File Server, it should work when rolled back to the Oct. 13 snapshot.

The other major piece in the puzzle is the Domain Controller(s).

December 19, we saw intermittent loss of service messages on the IP phones which lasted a couple of hours, and then stabilized and we haven't seen that issue since.

I have the secondary DC paused so it doesn't change anything while working on this issue.
I have removed the DNS and Host entries and added them back to the DC.
This seems to have no effect.

Over the past week, net use \\servername of a backup/retired Windows file server has continued to work just fine as well as Windows explorer \\servername\.

I have just attempted net use \\servername to most of my virtual Windows devices and they all complete successfully.

net use \\ubuntufileservername returns  System error 1311, we can't sign you in with this credential because your domain isn't available.

Maybe too much info, maybe not info that's need to assist, but this is the big picture.

Thanks for any assistance.


Pages: [1]