RL:
> 192.168.*.*
> is a private thingie that never gets resolved with DNS
That's non-sense. They will of course not get resolved by *public* DNS
servers, but nothing prevents you from resolving them through a
*private* one. My private network is running on 192.168.1.x addresses
and they get
On 1/29/2021 11:38 AM, RL wrote:
On the relevant clients, are all three with full name in /etc/hosts ?
Else failure is standard as
192.168.*.*
is a private thingie that never gets resolved with DNS
Regards, R.
I am not actually using those RFC1918 IP addresses, I just put those in
as
On windows, entering the server entries in the file/
/
/ c:\Windows\System32\Drivers\etc\hosts/
/might help? Maybe give it a try on the clients?/
/
/
/Regards, R.
/
On 1/29/21 8:44 PM, Jeffrey E Altman wrote:
Rainer,
OpenAFS UNIX/Linux clients and server only use the IP addresses in
Rainer,
OpenAFS UNIX/Linux clients and server only use the IP addresses in the
CellServDB file. The fully qualified domain names are only used by
OpenAFS Windows clients.
Jeffrey Altman
On 1/29/2021 2:38 PM, RL (rainer.laat...@t-online.de) wrote:
> On the relevant clients, are all three with
On the relevant clients, are all three with full name in /etc/hosts ?
Else failure is standard as
192.168.*.*
is a private thingie that never gets resolved with DNS
Regards, R.
On
On our buster servers the OpenAFS client (1.8.2) has an issue with
provisioning an AFS token. When I attempt to get an AFS token it very
often takes a long time.
$ aklog (this can up to 30 seconds or more)
After some investigation it looks like aklog is trying the AFS DB
servers listed in
