Allow CED and Sala Inmersiva management traffic
This commit is contained in:
1 parent
11d49dc245
commit
422071ca6a
2 files changed
+32
-4
No files matched your search
@@ -184,8 +184,9 @@ notification logs repeatedly reported `Failed to find a access point ... 8000000
|
||||
Restarting CcmExec restored management-point discovery. The server was listening
|
||||
on TCP 10123, but connections timed out until the missing inbound firewall rule
|
||||
was added. `Set-SguCedNotificationFirewall.ps1` reproduces that rule for only
|
||||
SGU-DC02's CED address, the Domain firewall profile, the notification host process,
|
||||
and source subnet `192.168.54.0/24`.
|
||||
SGU-DC02's CED address, the Domain firewall profile, and the notification host
|
||||
process. It initially allowed source subnet `192.168.54.0/24`; it now also allows
|
||||
`192.168.55.0/24` for the requested Sala Inmersiva management access described below.
|
||||
|
||||
After correcting the port, restart CcmExec only on affected clients when needed,
|
||||
then check their notification keep-alive logs and server-side `CNIsOnline`.
|
||||
@@ -197,6 +198,33 @@ The follow-up validation reported all 39 CED devices reachable and
|
||||
confirmed 39 online notification sessions (6 TCP and 33 HTTP). No operating-system
|
||||
restart or client reinstallation was needed.
|
||||
|
||||
### CED and Sala Inmersiva inter-network access
|
||||
|
||||
At the administrator's subsequent request on October 1, the router's Guest
|
||||
Network Pro **Access Intranet** settings were changed to allow the CED (VLAN 53,
|
||||
`192.168.54.0/24`) and Sala Inmersiva (VLAN 54, `192.168.55.0/24`) networks to
|
||||
communicate. From the CED profile, only Sala Inmersiva was newly selected. After
|
||||
applying and reloading the router, the Sala Inmersiva profile also showed CED
|
||||
selected: the setting is reciprocal. Its pre-existing Main Network selection was
|
||||
preserved. Esports CED and Invitados CED were not selected for this new connection.
|
||||
No SSID, password, subnet, or Wi-Fi GPO scope was changed. Applying the router
|
||||
configuration briefly restarted wireless connections; LCI-77 reconnected using
|
||||
its existing CED profile.
|
||||
|
||||
Authenticated WinRM from SGU-DC02 reached SD-17 (`192.168.55.19`) and SD-21
|
||||
(`192.168.55.20`), with both reporting live SSID **Sala Inmersiva**. Both clients
|
||||
could reach the management point's HTTP endpoint and, after extending the scoped
|
||||
notification firewall rule, TCP 10123. A separate client-to-client test confirmed
|
||||
TCP 2701 from AF-02 on CED to SD-17 on Sala Inmersiva and in the reverse direction.
|
||||
AF-02 could also reach SD-17's WinRM port. These are service reachability checks,
|
||||
not proof that every Windows service accepts connections from every peer.
|
||||
|
||||
Use DNS names or IP addresses in management tools across these subnets. Router
|
||||
routing alone does not make every computer appear automatically in Windows
|
||||
Explorer's Network view. Windows firewall rules, authentication, and enabled
|
||||
management services still apply. New Windows clients still need discovery and
|
||||
client enrollment; Wi-Fi profile deployment remains limited to the CED OU.
|
||||
|
||||
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
|
||||
VLAN 53, or re-enable the preserved Sala de Desarrollo network, as appropriate.
|
||||
|
||||
Reference in new issue
Block a user