[Networker] odd "Not a valid hotname" error

2012-01-25 12:29:05
Subject: [Networker] odd "Not a valid hotname" error
From: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
Date: Wed, 25 Jan 2012 12:27:20 -0500
This is unusual. I had to recreate my NMC installation recently. So I 
created a new VM, installed NMC, all works well. During the installation 
of NMC, it created a client and a saveset to save the DB (savepsm". Yet 
when I go to change the group it's in (from "Default"), I get an error 
that the client's name is not a valid host name, and I can't move it. So I 
figured I would delete it, and re-create it. And I get the same error when 
trying to re-create the client.

The client properly exist in DNS, both forward and reverse; I verified 
that from both the VM and my NW server. I can ping it from the server, and 
vice versa. The VM is in even the "servers" file of the server, and the NW 
server is in the "servers" file of the VM.

So what could be causing this? I thought this error would be caused by 
fault DNS, but a nslookup works properly on both machines, and I have full 
connectivity, and no firewall issues (I know, because I created other 
clients on the NMC running on this VM yesterday)

Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel:  215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at or
via RSS at

<Prev in Thread] Current Thread [Next in Thread>