Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

agurung

42 Posts

8265

June 9th, 2008 17:00

LDAP and GSS-API major error: Miscellaneous failure

Hi All

we are getting below message on our NS20. till now none of our users are having problem access andy CIFS files and folders. we checked our AD and doesn't seems to be any problem.

LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure

this message is logging often so we were wondering if any one of you have suggestion on how we can remove this logging.

Thank you in advance.

Rainer_EMC

8.6K Posts

June 9th, 2008 19:00

are these really the only errors you are getting - or are there any others before or after ?

any idea who/what MONAL is ?

agurung

42 Posts

June 9th, 2008 19:00

Hi Rainer

we have lot of other errors but most of them are for disk quota for other CIFS users from another windows domain.

Monal is namge of CIFS servers for one of the Domain it servers file for.

Thank you again

nandas

1.5K Posts

June 10th, 2008 08:00

Are you getting this error message of late or for a long time? Was there any changes in your AD side recently? It looks like a Kerberoes issue with the CIFS server in the AD. You may try using the resetserverpasswd option with the server_cifs -Join command.

However, I'll suggest to open a case with EMC Support if not already done and they may guide you accordingly with proper troubleshooting.

Thanks,
Sandip

BillStein-Dell

Moderator

 • 

284 Posts

June 10th, 2008 12:00

The GSSAPI Major error is a broad category of errors, and Miscellaneous failure can encompass many different errors.

What you need to look for is the GSSAPI Minor error which follows (somewhere) the GSSAPI Major error. The minor error will tell us much more about what error you are actually receiving.

"Major" and "Minor" are a little misleading in this context; the correct context would be "Main Category" and "Sub-Category". So we know the main category of the error you are getting is "Miscellaneous failure." Beneath that is a sub-category which we need to find which will point us toward the actual error.

-bill

agurung

42 Posts

June 10th, 2008 16:00

Hi Guys

i think we over looked other error message which was along side with the above message and guys you were right.

"LdapClient::connect: error message: Sasl protocol violation, (error code 99)"

does this make any sense to you?

Thank you

Message was edited by:
akg

agurung

42 Posts

June 10th, 2008 16:00

Hi Guys

only thing we change on our AD recently is we migrated our physical AD server to virtual server.

some changes on DC roles, could that be the problem?

Thank you

BillStein-Dell

Moderator

 • 

284 Posts

June 11th, 2008 08:00

The logs can be very useful, but if you're getting stuff flooded in there, it's hard to see exactly what needs to be done. The Sasl protocol violation error is very telling, but there are still a few things that it could be. Please do the following for me; replace server_x with the affected server:

server_log server_x -a -s > log.out
cat log.out | egrep "KERBEROS|LDAP|SMB"


Now you should see some pertinent errors before and after the Sasl protocol error. Please include about 6 lines before and about 6 lines after (from what you get from the above output) and we'll have a pretty good handle on what your issue is.

agurung

42 Posts

June 11th, 2008 16:00

We have Three CIFS Domain they are "1) internal.mit 2)internal.mitacademy 3)syd.internal.mitacademy" there is no trust setup between internal.mit and other domains. it seems to me that some reason all our DCS are not available for hrs at once. i am not sure why that is happening. all our DCs are located on different node of virtual infrastructure and also we have one physical DC.

please find below log as per your suggestion

note:- L-DC1, L-DC2, M-Server are Dcs of internal.mit domain
L-Pokhara, Pokhara are DCs of internal.mitacademy

thank you again

2008-06-12 03:32:21: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:32:21: SMB: 4: Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389
2008-06-12 03:32:21: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:32:21: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:32:21: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:32:21: SMB: 4: Unable to connect to Active Directory server l-dc2.internal.mit (10.0.0.11), port 389
2008-06-12 03:32:21: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:32:21: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:32:21: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:32:21: SMB: 4: Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389
2008-06-12 03:32:21: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:32:21: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:32:21: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:32:21: SMB: 4: Unable to connect to Active Directory server l-dc2.internal.mit (10.0.0.11), port 389
2008-06-12 03:32:21: SMB: 4: GPO update failed for server monal
2008-06-12 03:37:27: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:37:27: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:37:27: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:37:27: SMB: 4: Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389
2008-06-12 03:37:27: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:37:27: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:37:27: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:37:27: SMB: 4: Unable to connect to Active Directory server l-dc2.internal.mit (10.0.0.11), port 389
2008-06-12 03:37:27: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:37:27: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:37:27: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:37:27: SMB: 4: Unable to connect to Active Directory server l-dc2.internal.mit (10.0.0.11), port 389
2008-06-12 03:37:27: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:37:27: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:37:27: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:37:27: SMB: 4: Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389
2008-06-12 03:37:27: SMB: 4: GPO update failed for server monal
2008-06-12 03:40:11: SMB: 4: DCInvalidate M-SERVER from updateW2kInfo
2008-06-12 03:40:11: SMB: 4: DC6bdcdc04: setDCDown DC, refresh if needed (origin=rpc)
2008-06-12 03:40:11: SMB: 3: DC6bdcdc0c M-SERVER[MIT] dispatchIPCtoDC: No Reply TID=800 PID=1001 UID=800
2008-06-12 03:40:11: SMB: 3: cMsRPC_Request::Close bad reply ntStatus=DOMAIN_CONTROLLER_NOT_FOUND
2008-06-12 03:42:02: SMB: 3: KC_GetCreds:gss_acquire_cred_ext failed; majStatus=0xd0000, min=-1765328347
2008-06-12 03:42:02: SMB: 3: DC_GetBlob INTERNAL.MIT\monal L-DC1\HOST=Miscellaneous failure. Clock skew too great.
2008-06-12 03:42:33: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:42:33: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:42:33: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:42:33: SMB: 4: Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389
2008-06-12 03:42:33: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:42:33: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:42:33: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:42:33: SMB: 4: Unable to connect to Active Directory server l-dc2.internal.mit (10.0.0.11), port 389
2008-06-12 03:42:34: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:42:34: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:42:34: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:42:34: SMB: 4: Unable to connect to Active Directory server l-dc2.internal.mit (10.0.0.11), port 389
2008-06-12 03:42:34: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:42:34: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:42:34: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:42:34: SMB: 4: Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389
2008-06-12 03:42:34: SMB: 4: GPO update failed for server monal
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:47:40: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:47:40: SMB: 4: Unable to connect to Active Directory server l-dc2.internal.mit (10.0.0.11), port 389
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:47:40: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:47:40: SMB: 4: Unable to connect to Active Directory server m-server.internal.mit (10.0.0.8), port 389
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:47:40: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:47:40: SMB: 4: Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:47:40: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:47:40: SMB: 4: Unable to connect to Active Directory server m-server.internal.mit (10.0.0.8), port 389
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:47:40: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:47:40: SMB: 4: Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:47:40: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:47:40: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:47:40: SMB: 4: Unable to connect to Active Directory server l-dc2.internal.mit (10.0.0.11), port 389
2008-06-12 03:47:40: SMB: 4: GPO update failed for server monal
2008-06-12 03:52:46: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API major error: Miscellaneous failure
2008-06-12 03:52:46: LDAP: 3: LDAP authentication: Unable to acquire credentials for principal: MONAL$@INTERNAL.MIT. - GSS-API minor error: Clock skew too great
2008-06-12 03:52:46: LDAP: 3: LdapClient::connect: error message: Sasl protocol violation, (error code 99)
2008-06-12 03:52:46: SMB: 4: Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389
2008-06-12 03:55:59: SMB: 4: DCInvalidate L-DC1 from updateW2kInfo
2008-06-12 04:11:12: SMB: 4: >DC=L-POKHARA(172.16.32.3) R=11 T=1 ms S=0,1/-1
2008-06-12 04:27:50: SMB: 4: >DC=M-SERVER(10.0.0.8) R=8 T=1 ms S=0,1/-1
2008-06-12 04:38:06: SMB: 3: Domain='SYD-ACADEMIC' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 04:39:32: SMB: 3: last message repeated 7 times
2008-06-12 04:40:00: SMB: 3: Domain='SYD-ACADEMIC' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 04:42:09: SMB: 3: last message repeated 8 times
2008-06-12 04:42:17: SMB: 3: Domain='SYD-ACADEMIC' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 04:59:32: SMB: 4: >DC=L-DC1(10.0.0.1) R=8 T=1 ms S=0,1/-1
2008-06-12 07:40:51: SMB: 3: Domain='SYD-ACADEMIC' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 07:46:32: SMB: 3: Domain='SYD-ACADEMIC' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 07:49:23: SMB: 3: last message repeated 9 times
2008-06-12 07:49:34: SMB: 3: Domain='SYD-ACADEMIC' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 07:54:46: SMB: 3: last message repeated 5 times
2008-06-12 08:16:08: SMB: 3: Domain='SYD-ACADEMIC' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 08:23:51: SMB: 3: Domain='SYD-ACADEMIC' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 08:24:02: SMB: 3: last message repeated 3 times
2008-06-12 08:24:02: SMB: 3: Domain='syd-academic' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 08:24:04: SMB: 3: Domain='SYD-ACADEMIC' trusted DC='-': ignored errorFlags=0x0 DCStatus=0x547,5
2008-06-12 08:25:23: SMB: 3: last message repeated 2 times

Peter_EMC

674 Posts

June 11th, 2008 23:00

The "clock skew too great" messages:

"This generally occurs because the system's clock deviates too much from the time on the authenticating KDC. You are, generally, allowed upto five minutes of clock skew"

I think there is a time synchronization issue in your environment

agurung

42 Posts

June 11th, 2008 23:00

Hi peter

initially that is what we thought so we set NS20 to sync time with L-DC1. when we checked time in ns20 and l-dc1 its exactly same.

now we do not know why it is still saying time difference.

thank you

Message was edited by:
akg

Peter_EMC

674 Posts

June 12th, 2008 05:00

The datamover was unable to connect to L-DC1
"Unable to connect to Active Directory server l-dc1.internal.mit (10.0.0.1), port 389"

so maybe to time syncing was also impossible?

nandas

1.5K Posts

June 12th, 2008 05:00

Can you also show us the output of the following two commands -

server_cifs server_2
server_date server_2 timesvc stats ntp

It will help understanding your issue.

By the way - It may be wise to open a support case with EMC NAS support for this issue - while we are trying to help you here, which may take longer time.

Thanks,
Sandip

agurung

42 Posts

June 16th, 2008 04:00

Hi Guys

Thanks for your help and i actually had called support this morning and i was told that there could have been some problem with contacting NTP server on that particular time. i am not sure how that could have trigger time skew.

any way i have attached output as you requested perhaps this will make some sense.

[nasadmin@mstorage1 nasadmin]$ server_cifs server_2
server_2 :
256 Cifs threads started
Security mode = NT
Max protocol = NT1
I18N mode = UNICODE
Home Directory Shares DISABLED
Usermapper auto broadcast enabled

Usermapper[0] = [127.0.0.1] state:active (auto discovered)

Enabled interfaces: (All interfaces are enabled)

Disabled interfaces: (No interface disabled)

Unused Interface(s):
if=210_87_42_252 l=210.87.42.252 b=210.87.42.255 mac=0:60:16:1d:1d:90
if=192_168_6_2_Exchange l=192.168.6.2 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=192_168_6_3_SQL l=192.168.6.3 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=192_168_6_95_Virtualservers l=192.168.6.95 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=192_168_6_96_virtualservers_2 l=192.168.6.96 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=192_168_6_10 l=192.168.6.10 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=iscsi_ExchangeData l=192.168.6.71 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=iscsi_ExchangeLog l=192.168.6.72 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=iscsi_msSqlData l=192.168.6.73 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=iscsi_msSqlLog l=192.168.6.74 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=TestMPIO l=192.168.6.80 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=iscsi_exchange2003Data l=192.168.6.75 b=192.168.6.255 mac=0:60:16:1d:1d:8e
if=iscsi_Exchange2003Log l=192.168.6.76 b=192.168.6.255 mac=0:60:16:1d:1d:8e

DOMAIN ACADEMIC FQDN=internal.mitacademy SITE=Default-First-Site-Name RC=89
SID=S-1-5-15-25311a3c-1670357e-247c6e34-ffffffff
DC=LSERVER-1(172.16.32.7) ref=14 time=1 ms (Closest Site)
DC=POKHARA(172.16.32.2) ref=19 time=1 ms (Closest Site)
DC=L-POKHARA(172.16.32.3) ref=9 time=1 ms (Closest Site)
DC=L-POKHARA(172.16.32.120) ref=8 time=1 ms (Closest Site)


***** not sure why there is two entry for DC=L-Pokhara(172.16.32.3 and 172.16.32.120) and 172.16.32.120 doesn't exist anymore.**************

DOMAIN MIT FQDN=internal.mit SITE=Default-First-Site-Name RC=7
SID=S-1-5-15-1edf7ce9-605c78d2-350095-ffffffff
DC=M-SERVER(10.0.0.8) ref=1 time=1 ms (Closest Site)
DC=L-DC1(10.0.0.1) ref=3 time=1 ms (Closest Site)
DC=L-DC2(10.0.0.11) ref=2 time=1 ms (Closest Site)

DC=M-SERVER(192.168.5.5) ref=1 time=0 ms
DC**SMBSERVER(192.168.1.4) ref=1 time=0 ms

CIFS Server DANFE[ACADEMIC] RC=45
Full computer name=danfe.internal.mitacademy realm=INTERNAL.MITACADEMY
if=172_16_32_11 l=172.16.32.11 b=172.16.32.255 mac=0:60:16:1d:1d:90
FQDN=danfe.internal.mitacademy (Updated to DNS)
if=acaDatabackup l=192.168.5.16 b=192.168.5.255 mac=0:60:16:1d:1d:90
FQDN=danfe.internal.mitacademy (Updated to DNS)
Password change interval: 0 minutes
Last password change: Thu Oct 11 23:24:57 2007 GMT
Password versions: 2

CIFS Server MONAL[MIT] RC=3
Full computer name=monal.internal.mit realm=INTERNAL.MIT
Comment='EMC-SNAS:T5.5.30.5'
if=DatabackupNetwork l=192.168.5.15 b=192.168.5.255 mac=0:60:16:1d:1d:90
FQDN=monal.internal.mit (Updated to DNS)
if=10_0_0_21 l=10.0.0.21 b=10.0.0.255 mac=0:60:16:1d:1d:90
FQDN=monal.internal.mit (Updated to DNS)
Password change interval: 0 minutes
Last password change: Mon Jun 16 10:41:47 2008 GMT
Password versions: 2

[nasadmin@mstorage1 nasadmin]$ server_date server_2 timesvc stats ntp
server_2 :
Time synchronization statistics since start:
hits= 6, misses= 0, first poll hit= 1, miss= 0
Last offset: 0 secs, 40214 usecs
Current State: Running, connected, interval=60
Time sync hosts:
0 1 10.0.0.1
0 1 172.16.32.2

jausburn

2 Posts

December 28th, 2009 12:00

I know this looked like it was turning towards a time syncronization issue, but I found an interesting correlation with a problem I'm currently having.  Very similiar in nature, except that the minor error I'm receiving is "Server not found in Kerberos database".

Now, the only time this occurs is when one of the data movers is attempting to communicate with our domain controllers which are both w2k8-64bit and virtualized servers.  I'm digging deeper into this and was wondering if there was ever a solution found for this thread.  The forum post says there's been no answer in the last two years and I'm curious if the problem just went away, or if you just learned to live with it

BillStein-Dell

Moderator

 • 

284 Posts

January 3rd, 2010 07:00

I'm sorry if we weren't clear enough.  The "clock skew" messages only occur if the Data Mover time is more than 5 minutes off of the Domain Controller time to which you are trying to authenticate, so somebody's clock is off.  This is usually an error with the Celerra.  But sometimes it can be an issue with that particular Domain Controller.

The "server not found" messages are a little tougher to decode; there is more than one issue which can cause such a message.  If you haven't done so already, open a Service Request to clear that up.

View More

View All

No Events found!

Top