Nope, NTP is working everywhere. It has been suggested to me that "sslenabled y" is not necessary when using kaccount (kerberos) since kerberos by it's nature is encrypted auth. But, I cannot seem to find any documentation which specifically calls this out with regards to how this works with Celerra. It just seems odd to me that the process of connecting to AD using an "LDAP" command clearly uses port 389 according to the tcpdump, works fine, but when forcing it to use 636 fails.
To be clear, the only reason we are using the kerberos option is to be able to export shares using "sec=krbp5", of which there is very minimal documentation around what the real requirements are to do such a thing.
SAMEERK1
296 Posts
0
March 7th, 2012 02:00
please check this primus article from powerlink : emc231825
hope this helps
Sameer Kulkarni
downhill2
2 Intern
•
157 Posts
0
March 7th, 2012 05:00
Nope, NTP is working everywhere. It has been suggested to me that "sslenabled y" is not necessary when using kaccount (kerberos) since kerberos by it's nature is encrypted auth. But, I cannot seem to find any documentation which specifically calls this out with regards to how this works with Celerra. It just seems odd to me that the process of connecting to AD using an "LDAP" command clearly uses port 389 according to the tcpdump, works fine, but when forcing it to use 636 fails.
To be clear, the only reason we are using the kerberos option is to be able to export shares using "sec=krbp5", of which there is very minimal documentation around what the real requirements are to do such a thing.
thanks for the tip though.