CTAS is an application for Cyberoam. This application needs to be installed on the PDC and ADC for SSO to work.
But there were port being used in the CR CLI command and the CTAS GUI. The ports being used by the CR are following:
6677 UDP
5566 UDP
6060 UDP
6060: This port is used to send the user information from the AD to Cyberoam. AD conveys msg to CR that user1 has logged in and also when to kick him off. This msg contains the username only.
5566: This port is used to convey msgs between two domain controllers. Suite is installed on the PDC while the agent is installed on the additional domain controller. If the users gets logged in to the ADC, then agent installed on the ADC has to inform user details to the suite installed on the PDC. If you are using the Win2008 then create an exception for this port.
6677: This is very important port number, create an exception for this port on your domain controller. This port is used by the CR to interact with the Suite installed on the PDC. Let's say a UserA went home with his laptop along. Did his work all night came back office in the morning with remaining work to complete. He opened his laptop and all his sessions were open(browsers, messangers, outlook). As soon as his connects his laptop to the wireless of the wired network he gets and IP address. When CR gets a request from this IP address neither the CR has any record nor the AD(because he just did not switch his laptop, he hibernated his laptop). In this scenario, CR sends an msg to AD to send WMI query or read registry (according your settings) to find out the user who is logged in to that IP.
But there were port being used in the CR CLI command and the CTAS GUI. The ports being used by the CR are following:
6677 UDP
5566 UDP
6060 UDP
6060: This port is used to send the user information from the AD to Cyberoam. AD conveys msg to CR that user1 has logged in and also when to kick him off. This msg contains the username only.
5566: This port is used to convey msgs between two domain controllers. Suite is installed on the PDC while the agent is installed on the additional domain controller. If the users gets logged in to the ADC, then agent installed on the ADC has to inform user details to the suite installed on the PDC. If you are using the Win2008 then create an exception for this port.
6677: This is very important port number, create an exception for this port on your domain controller. This port is used by the CR to interact with the Suite installed on the PDC. Let's say a UserA went home with his laptop along. Did his work all night came back office in the morning with remaining work to complete. He opened his laptop and all his sessions were open(browsers, messangers, outlook). As soon as his connects his laptop to the wireless of the wired network he gets and IP address. When CR gets a request from this IP address neither the CR has any record nor the AD(because he just did not switch his laptop, he hibernated his laptop). In this scenario, CR sends an msg to AD to send WMI query or read registry (according your settings) to find out the user who is logged in to that IP.
Facing verification error while executing the verification process of Binance is quite obvious and mostly new comers get into such issues. Users are unable to execute the right process and they also need to understand that it might take a few days. To avoid such trouble, you can always take help from the team via Binance support number which is always functional. The team is ready to assist you and helps you in fixing all kind of queries in no time. You need to reach them the moment you get into trouble and get instant solutions in fraction of time.
ReplyDelete