Actually, I'm running Red Hat Enterprise Linux. Sorry I didn't mention that
in my first post.

I found the "nsrports" tool - must have missed it the first time (probably
logged into the wrong server). Anyway, the current configuration is this:
**

*[root@server ]# nsrports
Service ports: 7937-9936
Connection ports: 0-0 *
**

I've never adjusted the port range before, so this must be the default
setting. Is it really necessary to have such a wide range? I'd guess that
only a very few would suffice. At least I must define a port range that
doesn't interfere with port 9050, which is the port my application need to
use.

**
On 12/9/08, Goslin, Paul <pgoslin AT cincom DOT com> wrote:

> It should be located in \Program Files\Legato\nsr\bin\ directory...
>
> If it's not, then you have an old version of Networker installed or your
> installation is incomplete...
>
> > -----Original Message-----
> > From: EMC NetWorker discussion
> > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Kenneth Holter
> > Sent: Tuesday, December 09, 2008 8:05 AM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: Re: [Networker] Getting NetWorker client to skip
> > specified ports at startup
> >
> > Thanks for the tip. The command doesn't seem to be installed
> > with the NetWorker client software, so do you know where to get it?
> >
> > On 12/9/08, Brendan Sandes <brendannetworker AT gmail DOT com> wrote:
> > >
> > > use the nsrports command.
> > >
> > > something like "nsrports -S 7937-7940" (depending on whether the
> > > client is also a storage node or other functions you may need more
> > > ports).  That command needs to be run on the client in question and
> > > you need to stop and start NetWorker on the client for it to take
> > > effect
> > >
> > >
> > > Brendan
> > >
> > >  On Mon, Dec 8, 2008 at 7:31 PM, Kenneth Holter
> > <kenneho.ndu AT gmail DOT com>wrote:
> > >
> > >> Hi.
> > >>
> > >>
> > >> One of our applications depends on binding to port 9050 at
> > startup.
> > >> Last weekend the application did not come up after a
> > reboot, as the
> > >> NetWorker client had come first to using this particular port. Is
> > >> there some way of getting NetWorker client to _not_ use this port
> > >> (and maybe other specified
> > >> ports) so that the affected applications do not crash/fail?
> > >>
> > >> Regards,
> > >> Kenneth Holter
> > >>
> > >> 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