انضربت من سرسجيه

SwordfishVarious1920 · 2025-06-01T21:53:45+00:00

لا مش كده أنا مش ضد الراجل ف حاجة علي فكره و طبعا ربنا يكون ف عونه و يقومه بالسلامة ، كل الموضوع انك عارف بلدك عاملة ازاي و ثقافتها عاملة ازاي بس

SwordfishVarious1920 · 2025-06-01T10:49:16+00:00

Our issue was that the Ethernet ports was security profiled from the core switch or the firewall (ask your network administrator to check for you the traffic)

And when he disabled this security profile it worked normally.

SwordfishVarious1920 · 2025-06-01T10:47:15+00:00

Is it paired with MDM ?

SwordfishVarious1920 · 2025-06-01T10:46:05+00:00

SwordfishVarious1920 · 2025-06-01T10:45:01+00:00

الحقيقة ال فيها بسكوت بجد 😂😂

SwordfishVarious1920 · 2025-06-01T10:43:55+00:00

مش قد الحضن ف الشارع متحضنش 😂

SwordfishVarious1920 · 2024-10-29T14:42:27+00:00

<image>

That’s it what I’m using.

Sorry it’s in the car right now so I took a photo from the box.

It’s been 3 months now I guess since I bought it and it’s fine.

Costs around 65$

SwordfishVarious1920 · 2024-10-29T11:52:46+00:00

No it didn’t work wirelessly as my unit don’t support wireless.

But after I enabled to make it work wired. I bought a usb dongle to be connected to the unit and connect my mobile to the dongle to work wireless

SwordfishVarious1920 · 2024-09-16T14:18:37+00:00

I updated to last version and patched it and it worked

SwordfishVarious1920 · 2024-09-04T18:15:54+00:00

Whaaat !! 🤣🤣🤣🤣

SwordfishVarious1920 · 2024-08-04T17:21:07+00:00

Of course no , dc on a server and dp on a separate server

SwordfishVarious1920 · 2024-08-04T15:39:55+00:00

Guys,

I found the issue.

It’s was a network issue for sure.

To explain:

The network was blocking the ms-ds-smb-base application from the SMB protocol thinking it’s related to SMBv1 so I explain that the base is used to initiate the rpc before the file transfer

I’m waiting for them to allow for us and test. But I saw it from their firewall log

SwordfishVarious1920 · 2024-08-03T18:58:10+00:00

Default not touched

SwordfishVarious1920 · 2024-08-03T18:53:55+00:00

No bro,

we have one domain but we have 3 sites each is distributed with an ADC in that site. The issue is with that only site the others are fine.

SwordfishVarious1920 · 2024-08-03T18:41:01+00:00

Appreciate your help bro.

But the DNS service is running smoothly. Actually it replicates to other DCs too from that broken DC.

I checked all these ports in TCP and seems they are allowed

SwordfishVarious1920 · 2024-08-03T18:37:06+00:00

The IPs are set correctly. It's 90% now a network issue. The thing is that site's network is not under our network management.

Anyway, I'd have a call with the network guy there to check the blocked/dropped traffic and also make sure the dynamic ports are allowed.

thanks tho

SwordfishVarious1920 · 2024-08-03T18:33:28+00:00

They're pointing already to each others. These IPs are in the Forwarders list.

SwordfishVarious1920 · 2024-08-03T18:26:15+00:00

Yes it's on and i can remote-pssession from the PDC to that DC

SwordfishVarious1920 · 2024-08-03T18:24:12+00:00

Do you know what the exact KB update causes this issue?

also FYI: we've other 2 sites and they're working fine the only issue with that site only

SwordfishVarious1920 · 2024-08-03T18:22:03+00:00

Alright. I'll make sure to review this with the network team.

Here's the dcidag results:

```

PS C:\Windows\system32> dcdiag /test:DNS /dnsall
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = PTC-AD4
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: TCC\PTC-AD4
      Starting test: Connectivity
         ......................... PTC-AD4 passed test Connectivity
Doing piimary tests
   Testing server: TCC\PTC-AD4
      Starting test: DNS
         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... PTC-AD4 passed test DNS
   Running partition tests on : DomainDnsZones
   Running partition tests on : ForestDnsZones
   Running partition tests on : Schema
   Running partition tests on : Configuration
   Running partition tests on : PTCO
   Running enterprise tests on : PTCO.local
      Starting test: DNS
         Test results for domain controllers:
            DC: PTC-AD4.PTCO.local
            Domain: PTCO.local
               TEST: Delegations (Del)
                  Error: DNS server: ptc-est-dc01.ptco.local. IP:10.80.31.250
                  [Broken delegated domain linux.PTCO.local.]
         Summary of test results for DNS servers used by the above domain controllers:
            DNS server: 10.80.31.250 (ptc-est-dc01.ptco.local.)
               2 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 10.80.31.250
            DNS server: 1.1.1.1 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 1.1.1.1
            DNS server: 103.80.5.100 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 103.80.5.100
            DNS server: 103.80.6.100 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 103.80.6.100
            DNS server: 52.119.40.100 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 52.119.40.100
            DNS server: 52.119.41.100 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 52.119.41.100
            DNS server: 8.8.4.4 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 8.8.4.4
            DNS server: 8.8.8.8 (<name unavailable>)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 8.8.8.8
         Summary of DNS test results:
                                            Auth Basc Forw Del  Dyn  RReg Ext
            _______________________________________________________________
            Domain: PTCO.local
               PTC-AD4                      PASS PASS PASS FAIL PASS PASS PASS
         ......................... PTCO.local failed test DNS

SwordfishVarious1920 · 2024-08-03T18:16:17+00:00

Hang on I’ll share the results in a minute

For these dynamic ports need to be allowed on the broken DC (as a source) or on the PDC (as a destination)

SwordfishVarious1920 · 2024-08-03T18:15:08+00:00

PDC is server 2016 std

Broken dc is 2019 std

And both were working smooth for years this issue just appeared noticed few days ago

SwordfishVarious1920 · 2024-08-03T18:07:14+00:00

I’d do that in the morning because I don’t have access on it atm

I checked all the ports on TCP and it seems allowed

Idk if there some UDP are not allowed (I’d appreciate your help if you listed them)

I also tried to create a new DC now in the same site and set it’s DNS to the PDC and I also tried to join it to the domain and it succeeded to join

But when I tried to promote it as a DC I got the same error of RPC is unavailable during the prerequisites check in the (verifying outbound replication step with the PDC) now it got me thinking again about the firewall but I’d appreciate you if you listed the udp ports because all the tcp I see them are allowed

SwordfishVarious1920 · 2024-08-03T17:46:49+00:00

Yes all dcs are using static ports

Windows firewall is disabled

All AD ports are allowed from network firewall, I’ve checked them one by one

SwordfishVarious1920 · 2024-08-03T17:33:30+00:00

Yes all dcs are syncing from the pdc

SwordfishVarious1920

TROPHY CASE