This isn't exactly a Samba problem, but I am hoping the experts here can
help me.
I have been trying to get my OpenIndiana system to join a Samba4 domain and
I was running into multiple problems. So I decided to test against a true
Windows Server (2003) domain, to see if there is something wrong
You can try to find your record doing: (taking from the official how-to)
host -t SRV _ldap._tcp.samdom.example.com.
2013/2/22 Lee Allen l...@leecallen.com
This isn't exactly a Samba problem, but I am hoping the experts here can
help me.
I have been trying to get my OpenIndiana system to
That also fails:
lal...@oi.allenlan.net:~$ host -t SRV _ldap._tcp.allenlan.net.
Host _ldap._tcp.allenlan.net. not found: 3(NXDOMAIN)
lal...@oi.allenlan.net:~$ host -t SRV _ldap._tcp.dc._msdcs.allenlan.net.
Host _ldap._tcp.dc._msdcs.ALLENLAN.NET. not found: 3(NXDOMAIN)
I can manually add these
Maybe you can try to do a setup domain again.
2013/2/22 Lee Allen l...@leecallen.com
That also fails:
lal...@oi.allenlan.net:~$ host -t SRV _ldap._tcp.allenlan.net.
Host _ldap._tcp.allenlan.net. not found: 3(NXDOMAIN)
lal...@oi.allenlan.net:~$ host -t SRV
I did quite a bit more research on this. Everything I read says an AD DNS
should automatically set up those entries. I found a few trouble-shooting
documents that suggested checking them, but nothing indicating why they
might be wrong, and what to do about it.
I agree that tearing down the
I think he's seeing this with both S4 and WS2003 as a DC, so I don't know
that setting up the domain again will solve the problem. Provisioning a
domain on WS2003 (or S4 TBH) is a very simple process. It's hard to say
with such little info, but I'm guessing it's a client network configuration
- is
