client host name lenght question

The problem is that hostname you entered could not be resolved and thus it failed. Since you can see that it works for names with 8+ I believe your problem is not number of characters, but the simple fact that hostname can't be resolved.

Nevertheless, it is bad practice to name hosts with 8+ccharacters. You have uname which has 8 characters limit, hostname is 64 (at least HPUX) and nodename I guess the same. However, most applications are still coded to understand or use calls which relay on 8 character limit.

Hi Crvelin,

I had a similar issue. I was able to do nslookup the client machine from server but not able to add the client in networker. When I put the entry in host file I was able to create the client with the same hostname.

But I do not know why it happened.

Could be something broken with bind() on that system. For example, I have an issue on linux platform where nslookup works, but ping does not and this is because cashing daemon has the issue with it. Same system calls used by casing daemon are used by NW so if you have strong auth on client running it will fail. There are several workaround, but the point here is that different system calls/libraries are used when using to read /etc/hosts and to get info via calls used by nslookup. You saw that on your example and I know on issue which I had. So, everything I said before still applies.

Thanks Crveline.