04-24-2024 06:48 AM
My Windows Server Core having an internal address of 192.168.50.2, when natting it (NAT) it has an address of 192.168.99.36 (I'm installing Windows Server Core image on an EVE-NG VM and the EVE-NG VM is installed on ESXi).
I have a Cisco ISE VM installed on my ESXi having an address of 192.168.99.35.
Cisco ISE could ping SRVCore.local, server.com, ise1.SRVCore.local, core2019r2.SRVCore.local (Windows Server domain names).
But when joining Cisco ISE via its GUI to the Active Directory installed on Windows Server Core, I can't join it an it ends with a TIME OUT ERROR.
CiscoISE policy applying on switch problem
CiscoISE: Bug Search Tool におけるpatch番号の読み方
To Upgrade CiscoISE PSN node , best option to re-image to latest version 2.3 or 2.4 ISO file
ISE: SponsorPortalのユーザをActiveDirectory上のユーザで認証する設定
Joining 3802s to a 2504/5508/5520 after it has been on a 9800
Re: Cisco ISE node lost connection to Active Directory after Restore
04-25-2024 06:42 AM
I can't remember, but I think as a requirement the AD shouldn't be behind a NAT device. This is definitely the case with ISE-PIC and AD probes and I think the same applies to joining ISE to the AD.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide