Displaying 2 results from an estimated 2 matches for "hitronhub".
2019 Feb 04
1
Windows client still tries to connect to old AD after replacement
...ts:
127.0.0.1 localhost
192.168.0.17 ad.domain.intranet ad
192.168.0.21 domain-ad.domain.intranet domain-ad
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
/etc/resolv.conf:
domain Hitronhub.home
search Hitronhub.home
nameserver 192.168.0.1
/etc/krb5.conf
[libdefaults]
default_realm = DOMAIN.INTRANET
dns_lookup_realm = false
dns_lookup_kdc = true
/etc/samba/smb.conf
# Global parameters
[global]
netbios name = AD
realm = DOMAIN.INTRANET
...
2019 Feb 08
1
Windows client still tries to connect to old AD after replacement
..., this is the old AD domain and shouldn't have
> anything pointing to the new one.
Have deleted this line. This is a hangover from when I tried to connect
both the old and new ADs. No device exists with the IP address
192.168.0.21, luckily.
>> /etc/resolv.conf:
>> domain Hitronhub.home
>> search Hitronhub.home
>> nameserver 192.168.0.1
>
> This is a DC, it should be pointing to itself as a nameserver.
Done.
>> realm = DOMAIN.INTRANET
>> workgroup = DOMAIN
>
> What did you say about workgroups ?
> I do hope t...