Project

General

Profile

Bug #12415

AD/LDAP cannot bind to latest Public FreeNAS SU

Added by Vaibhav Chauhan almost 5 years ago. Updated about 4 years ago.

Status:
Closed: User Config Issue
Priority:
Blocks Until Resolved
Assignee:
John Hixson
Category:
OS
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

http://vb-freenas.sjlab1.ixsystems.com/ is running, latest Public SU; FreeNAS-9.3-STABLE-201511040813 which is not able to bind to AD/LDAP server.
login creds: root/abcd1234

whereas http://vb-fn-nightlies.sjlab1.ixsystems.com/ is running nightlies; FreeNAS-9.3-Nightlies-201511140300, which is able to bind to AD/LDAP server.
login creds: root/abcd1234

Settings below are common to both http://vb-fn-nightlies.sjlab1.ixsystems.com/ and http://vb-freenas.sjlab1.ixsystems.com/

Network:
IPv4 Default Gateway: 10.5.0.1
Nameserver 1: 10.212.0.2

AD server.
Domain Name: ix.internal
Domain account: [please request one, if you do not have, QA AD account ]
Domain Account Password: [please request one, if you do not have, QA AD account]

LDAP SERVER
hostname: qa-ldap.sjlab1.ixsystems.com
base dn: cn=admin,dc=ldap,dc=ix,dc=internal
bind dn: cn=admin,dc=ldap,dc=ix,dc=internal
password: abcd1234

History

#1 Updated by Cy Mike almost 5 years ago

^C[root@vb-freenas ~]# cat /etc/resolv.conf
search sjlab1.ixsystems.com
nameserver 10.212.0.2
[root@vb-freenas ~]# ping 10.212.0.1
PING 10.212.0.1 (10.212.0.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
^C
--- 10.212.0.1 ping statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
[root@vb-freenas ~]# ping 10.212.0.2
PING 10.212.0.2 (10.212.0.2): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host

#2 Updated by Cy Mike almost 5 years ago

global config page showed default gateway IP, but network summary page did not.

netstat -rn showed no default either

ran /etc/netcli and added default route

netstat -rn now shows default as does network summary page.

with network fixed I can now do...

[root@vb-freenas ~]# host -t SRV _ldap._tcp.ix.internal
_ldap._tcp.ix.internal has SRV record 0 100 389 dc08.ix.internal.

#3 Updated by Vaibhav Chauhan almost 5 years ago

  • Status changed from Unscreened to Closed: User Config Issue

had messed up network configuration, following steps fixed the issue.

following checklist should be used in similar situation.

How to Troubleshoot networking issues and AD configuration issues.

1. netstat -rn : should show you, default route,
1. if not, run /etc/netcli
2. configure default route.
2. host -t SRV _ldap._tcp.ix.internal, used for looking the domain controller.
3. service netif restart, restart network stack

#4 Updated by Jordan Hubbard almost 5 years ago

Or just configure the default route properly in the Networking UI. :)

#5 Avatar?id=14398&size=24x24 Updated by Kris Moore about 4 years ago

  • Target version changed from 261 to N/A

Also available in: Atom PDF