Backup Central

Hi
Has anyone else had to allow port 1970 through their firewall to allow a remote NMC to connect?

We suddenly found that NMC couldn't be run from a remote site (it has been working fine with the normal port 9000/9001) but found that after the prompt for the username / password to connect, nothing happened. On looking in the firewall, it was blocking port 1970. I've allowed 1970 through and all is now working again.

Maybe I missed something in the docs but don't recall seeing anything about port 1970.

Cheeers... Allan

Allan Nelson
CCS Lancaster
Tel: 01524 595815
--
This message (and any attachments) is for the recipient only NERC
is subject to the Freedom of Information Act 2000 and the contents
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system.


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Hi Allan,

NMC by default doesn't use port 1970, to my knowledge.

Could you check if
<NMC install dir>/etc/gstd.conf has clnt_svc_port pointing to 1970?
<NMC install dir>/web/gconsole.jnlp has 1970 as one of the argument
The client machine's web browser has an old gconsole.jnlp cached?

John

On Thu, Dec 16, 2010 at 6:03 AM, Nelson, Allan <an < at > ceh.ac.uk> wrote:

Hi
Has anyone else had to allow port 1970 through their firewall to allow a
remote NMC to connect?

We suddenly found that NMC couldn't be run from a remote site (it has been
working fine with the normal port 9000/9001) but found that after the prompt
for the username / password to connect, nothing happened. On looking in the
firewall, it was blocking port 1970. I've allowed 1970 through and all is
now working again.

Maybe I missed something in the docs but don't recall seeing anything about
port 1970.

Cheeers... Allan

Allan Nelson
CCS Lancaster
Tel: 01524 595815
--
This message (and any attachments) is for the recipient only NERC
is subject to the Freedom of Information Act 2000 and the contents
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system.


"signoff networker" in the body of the email. Please write to
networker-request < at > listserv.temple.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



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Hi Allan,

I don't think that you missed anything on the docs and I've never seen
anything like that. However, 1970 is still a valid port for both web and
console server and it is possible that NMC is not usig the defaults.

Check with "nestat -a" or equivalent what process is accepting connections on
port 1970 on the NMC server or maybe on other hosts sitting between NMC
server and clients.


jee


On Thursday 16 December 2010 14:03:30 Nelson, Allan wrote:
Hi
Has anyone else had to allow port 1970 through their firewall to allow a
remote NMC to connect?

We suddenly found that NMC couldn't be run from a remote site (it has been
working fine with the normal port 9000/9001) but found that after the
prompt for the username / password to connect, nothing happened. On
looking in the firewall, it was blocking port 1970. I've allowed 1970
through and all is now working again.

Maybe I missed something in the docs but don't recall seeing anything about
port 1970.

Cheeers... Allan

Allan Nelson
CCS Lancaster
Tel: 01524 595815


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Hi

I yesterday upgraded my Centos 5.5 testbed from 7.5sp3 to 7.6sp1 and
seems at port 9001 changes to port 1970.
You can rerun /opt/lgtonmc/bin/nmc_config and refer document how to
change console ports, sorry i can't remember kb number.

Regards, Riku

jee wrote:
Hi Allan,

I don't think that you missed anything on the docs and I've never seen
anything like that. However, 1970 is still a valid port for both web and
console server and it is possible that NMC is not usig the defaults.

Check with "nestat -a" or equivalent what process is accepting connections on
port 1970 on the NMC server or maybe on other hosts sitting between NMC
server and clients.


jee


On Thursday 16 December 2010 14:03:30 Nelson, Allan wrote:

Hi
Has anyone else had to allow port 1970 through their firewall to allow a
remote NMC to connect?

We suddenly found that NMC couldn't be run from a remote site (it has been
working fine with the normal port 9000/9001) but found that after the
prompt for the username / password to connect, nothing happened. On
looking in the firewall, it was blocking port 1970. I've allowed 1970
through and all is now working again.

Maybe I missed something in the docs but don't recall seeing anything about
port 1970.

Cheeers... Allan

Allan Nelson
CCS Lancaster
Tel: 01524 595815



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Thanks for all the replies.
The one below is interesting - glad to see someone else has seen this.
We're running RedHat 5 and Networker 7.6sp1 so maybe some RedHat update has done this.
We did apply some updates a week ago.
I'll check that out - but it'll be in the New Year - I'm off for Christmas now

Thanks again.

Allan.

________________________________________
From: EMC NetWorker discussion [NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of Riku Valli [riku.valli < at > UTA.FI]
Sent: 17 December 2010 06:40
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] NMC - Port 1970??

Hi

I yesterday upgraded my Centos 5.5 testbed from 7.5sp3 to 7.6sp1 and
seems at port 9001 changes to port 1970.
You can rerun /opt/lgtonmc/bin/nmc_config and refer document how to
change console ports, sorry i can't remember kb number.

Regards, Riku

jee wrote:
Hi Allan,

I don't think that you missed anything on the docs and I've never seen
anything like that. However, 1970 is still a valid port for both web and
console server and it is possible that NMC is not usig the defaults.

Check with "nestat -a" or equivalent what process is accepting connections on
port 1970 on the NMC server or maybe on other hosts sitting between NMC
server and clients.


jee


On Thursday 16 December 2010 14:03:30 Nelson, Allan wrote:

Hi
Has anyone else had to allow port 1970 through their firewall to allow a
remote NMC to connect?

We suddenly found that NMC couldn't be run from a remote site (it has been
working fine with the normal port 9000/9001) but found that after the
prompt for the username / password to connect, nothing happened. On
looking in the firewall, it was blocking port 1970. I've allowed 1970
through and all is now working again.

Maybe I missed something in the docs but don't recall seeing anything about
port 1970.

Cheeers... Allan

Allan Nelson
CCS Lancaster
Tel: 01524 595815



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
--
This message (and any attachments) is for the recipient only NERC
is subject to the Freedom of Information Act 2000 and the contents
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system.


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER