Michael L
asked on
Windows Server 2016 VM as Cisco Call Manager NTP Server Issues
Experts,
I'm having issues completing the Cisco Call Manager setup because it doesn't recognize my Windows 2016 PDC's NTP service.
Both are VMs on different ESXi hosts.
I can ping the Call Manager VM.
The switch recognizes the PDC as a Stratum 2 source.
My Windows domain and CM are on separate VLANs on this switch.
There's no access to the Internet or any other external source.
I did research and apparently the fact that the PDC is a VM can cause issue, but surely there's a solution.
Thanks in advance!
I'm having issues completing the Cisco Call Manager setup because it doesn't recognize my Windows 2016 PDC's NTP service.
Both are VMs on different ESXi hosts.
I can ping the Call Manager VM.
The switch recognizes the PDC as a Stratum 2 source.
My Windows domain and CM are on separate VLANs on this switch.
There's no access to the Internet or any other external source.
I did research and apparently the fact that the PDC is a VM can cause issue, but surely there's a solution.
Thanks in advance!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I know the VLANs were created to keep traffic separate, but I'm not sure how they're configured exactly. We have three VLANs; Management, Data, Voice. Our Management and Data VLANs pass traffic between each other, and those VLANs are configured exactly like the Voice VLAN. The Call Manager would be the first device on the Voice VLAN to try to talk to the other two VLANs. I do think the switch's configuration is the culprit, though.
You'll need to work with your networking team to address that then.
ASKER