samba4 dc "network location cannot be reached"
Posted
by
mitchell babies peters
on Server Fault
See other posts from Server Fault
or by mitchell babies peters
Published on 2013-11-09T00:15:30Z
Indexed on
2013/11/09
4:00 UTC
Read the original article
Hit count: 466
domain-controller
|samba4
to clear the air centos 6.4? (maybe 6.3) as the server, running samba 4.0.10, trying to add a windows 7 client that has connectivity to the server.
this is what windows shouts as me as it mocks my dependence on network infrastructure.
"the network location cannot be reached."
i have access to the domain contoller (dc)
im using the dc as the domain name server (dns) already, and the name is correctly resolving, and it is correctly forwarding outbound traffic.
i have nothing but self taught experience with active directory(ad) so if i am missing something obvious, please shout it out, but keep the verbal abuse to a minimum. i checked samba4DC + my error and found nothing relevant to my issue, if i missed something please point me in that direction.
- the weekend is just starting as i write this so i probably wont be back on to check this post for a day or three, but i might because this mystery is killing me.
i followed the samba4 as a dc guide here and i supplimented gaps with this
i have tested kerberos, ntp, and set my DC as the clock to sync to in my windows client and it appears to be a very small fraction of a second off so that shouldn't be it.
also, firewall and selinux are both off for testing.
i have also tried disabling ipv6, and cleared the registry of ipv6 records (allegedly the default samba4 as a DC runs as windows server 2003 which allegedly does not support or tolerate the existence of ipv6, fair warning, i heard this on the internet so it is probably a lie)
i have tried a few other things that i have forgotten because i have been doing this for a day and a half now.
ideas welcome. suggestions for alternatives are also welcome, as long as they are free. i was given a budget of $0 dollars and told to implement active directory (no prior knowledge of active directory at that point).
© Server Fault or respective owner