Displaying 6 results from an estimated 6 matches for "fexx".
Did you mean:
fcxx
2019 Nov 10
4
Invalid PTR record in reverse lookup zone
...rpa, .ad.home.arpa and 183.168.192.in-addr.arpa are forwarded
to the DC (.183.5 address)
Here is the output for the server:
Collected config --- 2019-11-10-18:30 -----------
Hostname: kronos
DNS Domain: ad.home.arpa
FQDN: kronos.ad.home.arpa
ipaddress: 192.168.183.5 2003:e3:570b:9400:f6xx:xxff:fexx:xxxx 2003:e3:5705:5200:f6xx:xxff:fexx:xxxxxx fd1f:6d10:24a0:1:f6xx:xxff:fexx:xxxx
-----------
Kerberos SRV _kerberos._tcp.ad.home.arpa record verified ok, sample output:
Server: 192.168.183.1
Address: 192.168.183.1#53
_kerberos._tcp.ad.home.arpa service = 0 100 88 kronos.ad.home.arpa.
Samba i...
2019 Nov 10
2
Invalid PTR record in reverse lookup zone
Hello,
I have configured an samba AD DC for use with
some windows and linux machines. The linux machines use
samba for user auth and also as kerberos kdc for
nfs mounts. This works fine so far but after a while
the user can not access the nfs shares anymore.
I tried to analyze the problem and finally found, that
the obtaining a ticket for nfs service failes in this
case because of a wrong
2019 Nov 11
0
Invalid PTR record in reverse lookup zone
...output for the server:
>>>
>>>
>>> Collected config --- 2019-11-10-18:30 -----------
>>>
>>> Hostname: kronos
>>> DNS Domain: ad.home.arpa
>>> FQDN: kronos.ad.home.arpa
>>> ipaddress: 192.168.183.5 2003:e3:570b:9400:f6xx:xxff:fexx:xxxx 2003:e3:5705:5200:f6xx:xxff:fexx:xxxxxx fd1f:6d10:24a0:1:f6xx:xxff:fexx:xxxx
>>>
>>> -----------
>>>
>>> Kerberos SRV _kerberos._tcp.ad.home.arpa record verified ok, sample output:
>>> Server: 192.168.183.1
>>> Address: 192.168.183.1#53
&g...
2020 Apr 29
2
Diagnosing IPv6 routing
On 4/28/2020 4:22 PM, Chris Adams wrote:
> What's in /etc/sysconfig/network-scripts/ifcfg-<name>? I wonder if you
> have IPv6 disabled.
Pasted below. V6 definitely works. I have a second server and gave it a
WAN address and I can connect between them using their WAN addresses.
That's what told me that my ip6tables weren't screwed up and that the
problem lay elsewhere.
2020 Apr 29
0
Diagnosing IPv6 routing
...they did for v4.
So... there's one thing you could try (but probably won't work to a
regular router interface) - see if there's a MAC-derived fe80::/64
link-local address on their end. Get the MAC of the gateway from the v4
ARP entry and expand it to a LL v6 address as fe80::xxxx:xxff:fexx:xxxx
(split the MAC, put ff:fe in the middle). Try ping6 that address with
%em2 appended (have to append the interface when using link-local
addresses). I doubt it'll work, since I know Juniper (which IIRC AT&T
likes) doesn't assign those (I can't remember for sure about Cisco and...
2020 Apr 29
1
Diagnosing IPv6 routing
...t; So... there's one thing you could try (but probably won't work to a
> regular router interface) - see if there's a MAC-derived fe80::/64
> link-local address on their end. Get the MAC of the gateway from the v4
> ARP entry and expand it to a LL v6 address as fe80::xxxx:xxff:fexx:xxxx
> (split the MAC, put ff:fe in the middle). Try ping6 that address with
> %em2 appended (have to append the interface when using link-local
> addresses). I doubt it'll work, since I know Juniper (which IIRC AT&T
> likes) doesn't assign those (I can't remember for...