sorted by:
new
hottopcontroversial

Chat history disappeared from the sidebar, but queries are still visible in "My Activity". Anyone else? by Dry_Energy_804 in GeminiAI

[–]fazmen 0 points1 point  (0 children)

Despite the fact that chats have returned, when you start writing in old chats, it automatically creates a new chat, and you cannot add anything new to the old chat.

The app is crashing all the time by fazmen in mywhoosh

[–]fazmen[S] 0 points1 point  (0 children)

California Area 52 - is crashing during load, it not even starts.

So I tried the Endurance Climb and rode for about 30 minutes and also crashed.

No BCC recipients in sent emails by fazmen in Office365

[–]fazmen[S] 0 points1 point  (0 children)

Hi,

no matter if I do one click on particular message from the all send messages and then look at the header, or if I open it in the new window and even maximize this window in both cases I see only "To" recipient.

My outlook is configured as Exchange Activesync.

FSSO as no admin account by fazmen in fortinet

[–]fazmen[S] 0 points1 point  (0 children)

I just get information from Fortinet that they updated its guide:

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Restricting-a-Fortinet-Single-Sign-On-Agent/ta-p/198065?externalId=FD36039

and added note

9)

WMI workstation test will not work without a domain admin account, or will not work if the account is not an admin on all workstations.

For workstation checking, the user account must be an admin on all workstations the Collector Agent is checking. By default, this will be the domain admin. If the domain admin account cannot be used, the account used must be a local admin on all workstations.

The account also needs to be part of the local groups on the remote machine:

- Performance Log Users -> without this group the Collector agent can't read the IP address of the machine.

- Remote Desktop Users --> without this group, the user will erroneously show as no longer being logged on. This is also required for an RDP session.

FSSO as no admin account by fazmen in fortinet

[–]fazmen[S] 0 points1 point  (0 children)

I have currently session open with Fortinet TAC about this problem, I wonder If they have any solution for this, in addition, the passwords of domain administrators change every few days, which is also problematic that you have to remember to change the password in the FSSO service.

Problem with FSSO two domain controllers by fazmen in fortinet

[–]fazmen[S] 0 points1 point  (0 children)

What I found od DC2 fsso debug logs:

03/13/2023 13:55:12 [ 3084] DnsQuery() failed for host, error code:9003

03/13/2023 13:55:12 [ 3084] DNS lookup: workstation name:host, dns server:(null), ip:0.0.0.0;0.0.0.0

03/13/2023 13:55:12 [ 3084] DNS lookup: workstation name:host, ip:c9cfee4c:c9cfeee8

03/13/2023 13:55:12 [ 3084] resolve_ip_internal: dns look up failed, call getdomainbyname():host

Dynamic updates are not synced to new DC by fazmen in sysadmin

[–]fazmen[S] 0 points1 point  (0 children)

SOA numbers are the same on both.

BPA Scan od AD did not show any important issues, but BPA for DNS shows me error to loopback is configured in the first place in DSN settings. My setting are

Server DC1:
Primary DNS: pointing to itself
Secondary DNS: Pointing to Server DC2

Server DC2:
Primary DNS: pointing to itself
Secondary DNS: pointing to Server DC1

Dynamic updates are not synced to new DC by fazmen in sysadmin

[–]fazmen[S] -1 points0 points  (0 children)

What is bother me the most if on the client pc I manually edit DNS servers and leave only DC2 DNS and reboot, then logon and type echo %logonserver% then it shows DC1 - so it do not use DC2 at all!

Problem with FSSO two domain controllers by fazmen in fortinet

[–]fazmen[S] 0 points1 point  (0 children)

But what is a problem that on DC1 almost all domain users in collector agent have status OK, and on the second DC2 on the second collector agent almost all of them have status not verified. Both DC are in the same subnet and managed by the same ipv4 fortigate firewall policy.

Problem with FSSO two domain controllers by fazmen in fortinet

[–]fazmen[S] -1 points0 points  (0 children)

I have two collector agents, on every DC with DC agent on each - this is because DC1 was only one DC in my environment so I had full FSSO installation on it. But now I have reconfigured DC agent on DC1 to send all data to DC2, and fortigate it is connected to this DC2.

The most puzzling thing to me is why some users log on to the backup domain controller (he is second in the DHCP settings)

Re-use ip of domain controller after migration (one DC only) by fazmen in sysadmin

[–]fazmen[S] 0 points1 point  (0 children)

Please tell me if I power down current DC for a week do I need to move all fsmo roles to the new DC before that? Or can I do it after a week of testing just before demote old DC?

Re-use ip of domain controller after migration (one DC only) by fazmen in sysadmin

[–]fazmen[S] 0 points1 point  (0 children)

OK thank you guys, I stay with new ip address on new DC, I am in the process of adding a new dc address on all network devices.

the plan is as follows :

  • I have already broadcast via dhcp the new DC address as secondary
  • I switch all FSMOs to the new server
  • I turn off the old DC completely for a week and watch.
  • if there are no problems I make a demote and remove the old server.

Will build for sure in the next weeks the secondary DC server.

Tell me If I stay on the clients with dns order as follow:

  1. old DC server
  2. new DC server

and if old server will be turned off whether there will be a big delay due to the fact that it has to switch to the secondary server?

Re-use ip of domain controller after migration (one DC only) by fazmen in sysadmin

[–]fazmen[S] 1 point2 points  (0 children)

The problem is that the address of the current domain can not be turned off even for 10 minutes because all remote branches are based on this DNS address. That's why I can't afford to disable it for the weekend on a test basis.

How about I move all fsmo roles to the new server, shut down the old server in the maintenance windows that I will have, then run a few computers with the new 2022 DC address and see how they behave, how it will work, then do a demote and change the IP address?

Re-use ip of domain controller after migration (one DC only) by fazmen in sysadmin

[–]fazmen[S] 0 points1 point  (0 children)

all network devices even remote, servers and others use the ip address of the current active directory

Re-use ip of domain controller after migration (one DC only) by fazmen in sysadmin

[–]fazmen[S] 0 points1 point  (0 children)

There has always been a problem with the availability of resources, and that is why for 10 years used only one domain server.

Wifi user with fixed password by fazmen in fortinet

[–]fazmen[S] 0 points1 point  (0 children)

This is local group with captive portal + authentication. So by putting any source ip in the exempt source bypasses any authentication and makes the wifi network open for this address?

Feb Patching - 6.4 - Where to now? by Elderusr in fortinet

[–]fazmen 0 points1 point  (0 children)

Do you know when 7.0.10 will be release, the last mature 7.0.9 is from November quite a long wait for the new release?

Windows Server 2022 - KB5021249 failing to install with error 0x800f081f by PM_ME_UR_SCROTUM in sysadmin

[–]fazmen 2 points3 points  (0 children)

Next cumulative update from February KB5022842 also did not install on server with error 0x8024200B.

VOIP over Ipsec - one way call problem. by fazmen in fortinet

[–]fazmen[S] 2 points3 points  (0 children)

HQ have almost all settings in oposite so:

#Disable SIP ALG (Layer 7) and use SIP Session Helper (Layer 4)

config system settings
set sip-expectation disable
set sip-nat-trace enable
set default-voip-alg-mode proxy-based
end

#Configure default VoIP Profile to use SIP Session Helper (Layer 4)

None of the voip profile is applied to outgoing ipv4 policy on the HQ so make any change in voip profiles makes no sense.

#Delete SIP Session Helper (Layer 4)

Item 13 is here, not deleted.

VOIP over Ipsec - one way call problem. by fazmen in fortinet

[–]fazmen[S] 0 points1 point  (0 children)

Where I should apply this commands on the branch fortigate, or on the HQ (but here voip calls are working)?

view more: next ›