HPE GreenLake Administration
- Community Home
 - >
 - Networking
 - >
 - Wireless
 - >
 - M and MSM Series
 - >
 - Re: MSM - Authentication via Active Directory
 
M and MSM Series
        1840178
        Members
    
    
        3745
        Online
    
    
        110162
        Solutions
    
Forums
        Categories
Company
Local Language
                
                  
                  back
                
        
                
        
                
        
                
        
        
        
                
        
                
        
        
        
                
        
              
              Forums
Discussions
Forums
- Data Protection and Retention
 - Entry Storage Systems
 - Legacy
 - Midrange and Enterprise Storage
 - Storage Networking
 - HPE Nimble Storage
 
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
                
                  
                  back
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
                
            
            
                
            
                
            
                
            
                
            
            
                
            
                
            
            
                
            
                
              
            Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
 - Appliance Servers
 - Alpha Servers
 - BackOffice Products
 - Internet Products
 - HPE 9000 and HPE e3000 Servers
 - Networking
 - Netservers
 - Secure OS Software for Linux
 - Server Management (Insight Manager 7)
 - Windows Server 2003
 - Operating System - Tru64 Unix
 - ProLiant Deployment and Provisioning
 - Linux-Based Community / Regional
 - Microsoft System Center Integration
 
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
        Information
        Community
Resources
Community Language
        Language
        Forums
Blogs
Topic Options
			
				
					
	
			
		
	- Subscribe to RSS Feed
 - Mark Topic as New
 - Mark Topic as Read
 - Float this Topic for Current User
 - Bookmark
 - Subscribe
 - Printer Friendly Page
 
- Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
08-30-2010 02:14 AM
08-30-2010 02:14 AM
			
				
					
						
							MSM - Authentication via Active Directory
						
					
					
				
			
		
	
			
	
	
	
	
	
			
				
					
					
						I am installing an MSM765 controller and have run into a problem with authentication via Active Directory.  The controller shows that it is "Joined" to the AD domain.  However, when a wireless client tries to authenticate  the following messages appear in the log.  The machine at ip address 10.66.241.217 is one of the Microsoft domain controllers.
Aug 27 12:16:08 debug iprulesmgr The controller has authorized station (mac-address='E8:06:88:78:BE:A6').
Aug 27 12:16:08 debug iprulesmgr Sending RADIUS Packet (Length:'266',Code:'Access-Request',Id:'237') to RADIUS Server (Ip:'127.0.0.1',Port:'1645') for User (nas-port:'21',username:'europe\ppmm').
Aug 27 12:16:09 warning radiusd Cound not bind to AD; DNS unreachable? (Client not found in Kerberos database)
Aug 27 12:16:09 debug radiusd E:rlm_ldap: bind to 10.66.241.217:636 failed Unknown error
Aug 27 12:16:09 debug radiusd E:rlm_ldap: (re)connection attempt failed
The MSM configuration guide only mentions joining the controller to the AD domain. But is there something more that needs to be done? Is there some specific configuration required for Kerberos?
					
				
			
			
				
			
			
				
			
			
			
			
			
			
		
		
		
	
	
	
Aug 27 12:16:08 debug iprulesmgr The controller has authorized station (mac-address='E8:06:88:78:BE:A6').
Aug 27 12:16:08 debug iprulesmgr Sending RADIUS Packet (Length:'266',Code:'Access-Request',Id:'237') to RADIUS Server (Ip:'127.0.0.1',Port:'1645') for User (nas-port:'21',username:'europe\ppmm').
Aug 27 12:16:09 warning radiusd Cound not bind to AD; DNS unreachable? (Client not found in Kerberos database)
Aug 27 12:16:09 debug radiusd E:rlm_ldap: bind to 10.66.241.217:636 failed Unknown error
Aug 27 12:16:09 debug radiusd E:rlm_ldap: (re)connection attempt failed
The MSM configuration guide only mentions joining the controller to the AD domain. But is there something more that needs to be done? Is there some specific configuration required for Kerberos?
		1 REPLY 1
	
	            
            
		
		
			
            
                - Mark as New
 - Bookmark
 - Subscribe
 - Mute
 - Subscribe to RSS Feed
 - Permalink
 - Report Inappropriate Content
 
08-30-2010 11:30 AM
08-30-2010 11:30 AM
			
				
					
						
							Re: MSM - Authentication via Active Directory
						
					
					
				
			
		
	
			
	
	
	
	
	
			
				
					
					
						The message "Client not found in Kerberos database" was due to the fact that the Windows domain entry for the controller had been deleted.  After joining the MSM controller to the domain again, authentication work correctly.
					
				
			
			
				
			
			
				
			
			
			
			
			
			
		
		
		
	
	
	
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
		
	
	
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP