Re: [Networker] Unable to add a new client
2008-11-07 15:35:12
EMC support is fantastic when you get a knowledgeable person who's easy
to understand....
They had me add all 4 IP addresses for this client into both hosts files
on both the backup server and the client. This allowed me to issue an
'nsradmin -s backupservername' from the client, meaning the backup
server can now forward and reverse the client name I guess... A
subsequent probe also succeeded with no errors...
> -----Original Message-----
> From: EMC NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Goslin, Paul
> Sent: Friday, November 07, 2008 2:59 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Unable to add a new client
>
> No - This is a new client altogether.... A new DNS name that
> has never been used before...
>
> The admin is now looking into teaming the NIC cards so it can
> use one IP address instead of the 4 he currently has it
> configured for.
>
> Why in the world does Networker DEPEND on reverse DNS ?
> Security ? I guess they never envisioned multi-homed clients
> such as this... If reverse DNS is a feature, what are the
> advantages ??
>
> What I need is a switch on the client definition to disable
> it on a per client basis ....
>
> > -----Original Message-----
> > From: Fazil.Saiyed AT anixter DOT com [mailto:Fazil.Saiyed AT anixter DOT
> > com]
> > Sent: Friday, November 07, 2008 2:45 PM
> > To: EMC NetWorker discussion; Goslin, Paul
> > Cc: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: Re: Unable to add a new client
> >
> >
> > Hello,
> > Are you creating new client or trying to rename one,
> usually, you only
> > supply client id during the later, are you re-using clientid ?
> > Thanks
> >
> >
> >
> > "Goslin, Paul" <pgoslin AT CINCOM DOT COM>
> > Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
> >
> > 11/07/2008 11:40 AM
> > Please respond to
> > EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please
> > respond to "Goslin, Paul" <pgoslin AT CINCOM DOT COM>
> >
> > To
> > NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > cc
> > Subject
> > Re: Unable to add a new client
> >
> >
> >
> >
> >
> >
> > I'm using NMC, so all I get is a single pop-up box entitled Error:
> > 'Invalid client ID', with an OK button...
> >
> > I asked the system admin why it has 4 IP addresses, he said to
> > facilitate throughput, it's a large file server with about
> 3 Terabytes
> > of capacity.
> >
> > How would I go about using the local host file to force it
> to use just
> > one IP address ?? Simply add it the local hosts file with a
> single IP
> > address ?
> >
> > There is no firewall involved as far as I know of...
> >
> > I see nothing in the daemon.raw log file either...
> >
> > > -----Original Message-----
> > > From: EMC NetWorker discussion
> > > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Stan Horwitz
> > > Sent: Friday, November 07, 2008 12:15 PM
> > > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > > Subject: Re: [Networker] Unable to add a new client
> > >
> > > > From: "Goslin, Paul" <pgoslin AT CINCOM DOT COM>
> > > > Reply-To: EMC NetWorker discussion
> > <NETWORKER AT LISTSERV.TEMPLE DOT EDU>,
> > > > "Goslin, Paul" <pgoslin AT CINCOM DOT COM>
> > > > Date: Fri, 7 Nov 2008 11:52:29 -0500
> > > > To: <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
> > > > Subject: [Networker] Unable to add a new client
> > > >
> > > > I am unable to add a new client machine, Networker
> > refuses to allow
> > > > the client to be added using either it's name or one of
> the 4 IP
> > > > addresses that get returned when I do a lookup of it...
> > > >
> > > > Anyone have a method for adding a new Windows 2008 client
> > > that has 4
> > > > IP addresses ???
> > > >
> > > > It has the latest client , 7.4 sp3. The server is
> Win2003 server
> > > > running
> > > > 7.4 sp2.
> > >
> > > Paul;
> > >
> > > What error message do you get when you try to add that client?
> > >
> > > 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
> > > http://listserv.temple.edu/archives/networker.html or via RSS at
> > > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> > >
> >
> > 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
> > http://listserv.temple.edu/archives/networker.html or via RSS at
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
> >
> >
> >
>
> 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
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
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
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|