Resolve Sala Inmersiva workgroup names from CED

This commit is contained in:
alexrg committed 2026-10-01 15:48:04 -06:00
1 parent 2c90802930
commit 046a815962
3 files changed
+146 -3

No files matched your search

+49 -3
View File
@@ -237,9 +237,55 @@ From LCI-77 with live SSID **Centro de Experiencia Digital**, TCP 3389 to that
address succeeded. An actual RDP connection negotiation returned a 19-byte reply
with negotiation response type 2 and selected protocol 2 (HYBRID/NLA). This
validates the RDP endpoint across the VLANs, not an authenticated desktop session.
Before domain enrollment, use the current IP address and an authorized local
SI-04 account. The bare name alone is not a reliable cross-subnet connectivity
test. No domain enrollment or domain DNS record was created for this test.
This initial test did not enroll SI-04 or create a domain DNS record. Before
enrollment, an authenticated RDP login still requires an authorized local SI-04
account.
#### Workgroup names available from CED
The subsequent DNS repair publishes A records in the existing secure AD DNS
zone `lci.lasalle.mx`, without creating AD computer objects. The router's Sala
Inmersiva client list identified six additional Windows workgroup names:
`SI-02`, `SI-04`, `SI-05`, `SI-06`, `SI-07`, and `SI-08`. Each address was verified
with a direct DNS query to `192.168.55.1` before publication. SI-04 currently
resolves to `192.168.55.138`.
On SGU-DC02, task **LCI - Sala Inmersiva workgroup DNS** runs
`scripts/Sync-SguSalaWorkgroupDns.ps1` as SYSTEM every five minutes, using the
protected folder `C:\ProgramData\LCI-Admin\Sala-DNS`. No credentials are stored.
Its `manifest.json` contains the approved names and their last published
addresses. Only router answers in `192.168.55.0/24` are accepted. The sync refuses
to overwrite records changed by another administrator and stops managing a name
once it has an AD computer object. New names require explicit approval and an
entry in this manifest; arbitrary guest/IoT clients are not imported.
Records have a five-minute TTL. A failed router query preserves the last record
and reports an error in `last-result.json` and the task result; the TTL does not
expire the server record. Review these errors if an address becomes stale.
The first two SYSTEM runs completed successfully with all six records current.
The zone continues to allow secure dynamic updates only.
Domain clients use their domain suffix and existing **CED - DNS de dominio** GPO.
The workgroup administrator PC LCI-77 additionally needed the Wi-Fi connection
suffix `lci.lasalle.mx` and an NRPT rule for that namespace pointing to
`192.168.54.211`; `scripts/Set-SguCedAdminDns.ps1` reproduces this local setup.
The prior suffix is saved in `LCI77-Sala-DNS-before.json` in the protected private
folder. The rule applies only to this DNS namespace; existing Tailscale rules
remain intact. The adapter suffix persists across Wi-Fi profile changes.
Validation used Windows' application resolver (`System.Net.Dns.GetHostAddresses`),
not just an explicit DNS-server query. All six short names resolved on LCI-77
while its live SSID was **Centro de Experiencia Digital**. AF-02, at
`192.168.54.130`, also resolved SI-04 correctly. A TCP connection opened using
the name **SI-04** from LCI-77 reached port 3389 and received a successful RDP
HYBRID/NLA negotiation response. This verifies name resolution and the RDP
endpoint across networks; it does not assert an authenticated desktop session.
To undo this DNS repair, disable the sync task first. Remove only manifest-owned
A records that still match their last published IP and have no AD computer object.
On LCI-77, restore the saved Wi-Fi suffix and remove only the NRPT rule with the
comment `CED domain DNS for local administrator Wi-Fi`. Keep the domain GPO and
unrelated DNS rules. These DNS changes require no router apply or radio restart.
To recover the previous Wi-Fi, first provision an existing known-good profile
and reconnection task on SGU-DC02 and affected PCs. Then restore Aula Flexible on