So its probably just a case where they have blocked the ports that were already configured. Find out what kind of 'change' they implemented on their firewall and that might give us an idea where to go from there..
Joe
----- Original Message ----
From: Linda M. King <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; Joe DeSouza <[EMAIL PROTECTED]>
Cc: Linda M. King <[EMAIL PROTECTED]>
Sent: Wednesday, August 30, 2006 7:42:53 PM
Subject: Re: 4.5.2 Notifier vs. Firewall issue
From: Linda M. King <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; Joe DeSouza <[EMAIL PROTECTED]>
Cc: Linda M. King <[EMAIL PROTECTED]>
Sent: Wednesday, August 30, 2006 7:42:53 PM
Subject: Re: 4.5.2 Notifier vs. Firewall issue
Joe,
Yes, it did go from v3x to v4.5.x several years ago. And, yes, the
notifications were working fine after the upgrade and for the past few
years, but failed very recently as I described. I have been here 1.5 yrs.
and have never had any user issues with the notifier separate from general
arserver issues/outages until this.
Linda
On Wed, 30 Aug 2006 16:33:35 -0700, Joe DeSouza <[EMAIL PROTECTED]>
wrote:
>If I am not mistaken the parameters you have configured were good for
version 3.. has this system grown up from an upgrade from version 3? If so
were the notifications working after the upgrade?
>
>Joe D'Souza
>Remedy Developer / Consultant,
>BearingPoint,
>Virginia.
>
>
>
>----- Original Message ----
>From: Linda M. King <[EMAIL PROTECTED]>
>To: [email protected]
>Sent: Wednesday, August 30, 2006 6:31:20 PM
>Subject: Re: 4.5.2 Notifier vs. Firewall issue
>
>
>Responses to several posters (including Joe):
>
>Yes, this is the case. It was working, they made changes in the firewall,
now it's not working.
>
>I don't know if they turned on NAT, I will find out. I did read in a few
docs that enabling NAT made Notifier impossible to use...
>
>We're on a UNIX server, and in the ar.conf file neither of these
parameters are set - ARNTTCPPORT and ARNTTCPCLIENTPORT. Also, nowhere in
the 4.5 docs are these two parameters mentioned, although I did see them
mentioned for later versions than 4.5.2 in the archives. Are they
applicable to 4.5.2?
>If so, what should they be set to?
>
>In the Server_Admin_Guide.pdf v4.5 pg 6-8 (pg 150 of the pdf)there is a
picture and info, but it's too general. The most specific info is the
paragraph I quoted (below) in my original message. I can send along the
4.5 pdf if someone thinks it would help them help me...
>
>Thanks for the feedback so far! Any other thoughts?
>
>Linda
>
>FYI - here's the entire nfy.conf file (FYI - the commented-out line has
been that way since 4/2004, the firewall changes happened in the last
month) and all applicable lines from the ar.conf for my 4.5.2 server:
>
>"nfy.conf" 5 lines, 132 characters
>Notifier-Specific-Port: 51501
>#Notifier-Outbound-Port: 51502
>Register-With-Portmapper: T
>TCD-Specific-Port: 51586
>Max-Users: 25000
>~
>
>"ar.conf" 39 lines, 1247 characters
># Directory that contains the database files, log files, and notification
># files for the AR server
>Register-With-Portmapper: T
>Notifier-Specific-Port: 51501
>TCD-Specific-Port: 51586
>Private-RPC-Socket: 390620 14 14
>Private-RPC-Socket: 390635 30 30
>Private-RPC-Socket: 390680 1 1
>Private-RPC-Socket: 390681 3 3
>Private-RPC-Socket: 390685 1 1
>Private-RPC-Socket: 390686 1 1
>~
>
>
>On Wed, 30 Aug 2006 14:17:04 -0700, Joe DeSouza <[EMAIL PROTECTED]>
>wrote:
>
>>I think Lindas problem is that it was working prior to some configuration
>changes in the firewall.. so I assumed that they already had these
>parameters set in the clients and the servers config file but the changes
>in the firewall configuration messed up these... so all they need to do is
>open those ports that were configured prior to the changes to the firewall
>configuration...
>>
>>Joe D'Souza
>>Remedy Developer / Consultant,
>>BearingPoint,
>>Virginia.
>>
>>
>>
>>----- Original Message ----
>>From: "McKenzie, James J C-E LCMC HQISEC/L3" <[EMAIL PROTECTED]>
>>To: [email protected]
>>Sent: Wednesday, August 30, 2006 4:56:51 PM
>>Subject: Re: 4.5.2 Notifier vs. Firewall issue
>>
>>**
>>Joe and Linda:
>>
>>If they are not set, set them. If you are in a WINDOWS environment, you
>will have to set these in WINDOWS not in the ar.ini file. This is for both
>server and client. If you are in UNIX, set them in the ar.conf file on the
>server and in the ar.ini file on the client (note 4.5.2 has a native UNIX
>client.) Sadly, I don't have my 4.5.2 guides anymore. It had a pretty
>picture of what Linda is trying to do and how to set it up.
>>
>>James McKenzie
>>L-3 GSI
>>
>>________________________________
>>From: Action Request System discussion list(ARSList)
>[mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
>>Sent: Wednesday, August 30, 2006 1:51 PM
>>To: [email protected]
>>Subject: Re: 4.5.2 Notifier vs. Firewall issue
>>
>>
>>**
>>Check your ar.conf file (if you are on UNIX) or ar.cfg file (if your
>server is windows) and look for the port numbers you have configured for
>ARNTTCPPORT and ARNTTCPCLIENTPORT on your clients ar.cfg file.. these are
>the ports that need to be allowed on your firewall..
>>
>>Hope that helps
>>
>>Joe D'Souza
>>Remedy Developer / Consultant,
>>BearingPoint,
>>Virginia.
>>
>>
>>----- Original Message ----
>>From: Linda M. King <[EMAIL PROTECTED]>
>>To: [email protected]
>>Sent: Wednesday, August 30, 2006 4:41:38 PM
>>Subject: 4.5.2 Notifier vs. Firewall issue
>>
>>
>>Hello all,
>>Company I work for made recent changes to their firewall and now users can
>>login to their Notifier 4.5.2 tools, but don't receive any notifications.
>>User & Admin tool access is fine.
>>They want to know what ports to open on the firewall so the Notifications
>>server & Notifier clients can communicate successfully.
>>I'm having trouble with what to tell them since all the knowledge base and
>>ARSlist archived articles are about Alert v. 5 and above and not Notifier
&
>>ARS server v4.5.2. The 4.5.2 documentation also hasn't been real helpful
>>and I'm not well-versed enough in this to direct the firewall guys
>>effectively where to look or what to try next.
>>Can someone point me to the info I'm missing or help out?
>>The 4.5.2 documentation says: "Remedy Notifier client connects to a
>>specific port of the Notification server, and registers with user
>>information. After verifying the user information on the AR System server,
>>the Notification server provides an acknowledgment to Remedy Notifier
>>client. Registration of Remedy Notifier with the Notification server is an
>>RPC call, and the responding acknowledgment is a TCP call using a
different
>>port. (excerpt is from page 150, Server_Admin_Guide.pdf v4.5)
>>Our 4.5.2 ARS server is set up to use (register with) portmapper and is
>>configured with a Server TCP/IP port 51586, Notifier Server TCP/IP port
>>51501. These ports have been opened on the firewall, and we've put the
TCP
>>port # in the Notifier tool, no luck. How do I determine what RPC port
>>notifier is using? I don't see anything relating to that in either the
>>nfy.conf or ar.conf files, just the TCP port settings.
>>What am I missing? Where should I (or the firewall/server folks) look
>next?
>>Thanks for any help!
>>Linda M. King
>>[EMAIL PROTECTED]
>>__________________________________________________________________________
_
>____
>>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
><http://www.wwrug.org/>
>>__20060125_______________________This posting was submitted with HTML in
>it___
>>__20060125_______________________This posting was submitted with HTML in
>it___
>>
>>__________________________________________________________________________
_
>____
>>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
>___________________________________________________________________________
____
>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
>___________________________________________________________________________
____
>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
Yes, it did go from v3x to v4.5.x several years ago. And, yes, the
notifications were working fine after the upgrade and for the past few
years, but failed very recently as I described. I have been here 1.5 yrs.
and have never had any user issues with the notifier separate from general
arserver issues/outages until this.
Linda
On Wed, 30 Aug 2006 16:33:35 -0700, Joe DeSouza <[EMAIL PROTECTED]>
wrote:
>If I am not mistaken the parameters you have configured were good for
version 3.. has this system grown up from an upgrade from version 3? If so
were the notifications working after the upgrade?
>
>Joe D'Souza
>Remedy Developer / Consultant,
>BearingPoint,
>Virginia.
>
>
>
>----- Original Message ----
>From: Linda M. King <[EMAIL PROTECTED]>
>To: [email protected]
>Sent: Wednesday, August 30, 2006 6:31:20 PM
>Subject: Re: 4.5.2 Notifier vs. Firewall issue
>
>
>Responses to several posters (including Joe):
>
>Yes, this is the case. It was working, they made changes in the firewall,
now it's not working.
>
>I don't know if they turned on NAT, I will find out. I did read in a few
docs that enabling NAT made Notifier impossible to use...
>
>We're on a UNIX server, and in the ar.conf file neither of these
parameters are set - ARNTTCPPORT and ARNTTCPCLIENTPORT. Also, nowhere in
the 4.5 docs are these two parameters mentioned, although I did see them
mentioned for later versions than 4.5.2 in the archives. Are they
applicable to 4.5.2?
>If so, what should they be set to?
>
>In the Server_Admin_Guide.pdf v4.5 pg 6-8 (pg 150 of the pdf)there is a
picture and info, but it's too general. The most specific info is the
paragraph I quoted (below) in my original message. I can send along the
4.5 pdf if someone thinks it would help them help me...
>
>Thanks for the feedback so far! Any other thoughts?
>
>Linda
>
>FYI - here's the entire nfy.conf file (FYI - the commented-out line has
been that way since 4/2004, the firewall changes happened in the last
month) and all applicable lines from the ar.conf for my 4.5.2 server:
>
>"nfy.conf" 5 lines, 132 characters
>Notifier-Specific-Port: 51501
>#Notifier-Outbound-Port: 51502
>Register-With-Portmapper: T
>TCD-Specific-Port: 51586
>Max-Users: 25000
>~
>
>"ar.conf" 39 lines, 1247 characters
># Directory that contains the database files, log files, and notification
># files for the AR server
>Register-With-Portmapper: T
>Notifier-Specific-Port: 51501
>TCD-Specific-Port: 51586
>Private-RPC-Socket: 390620 14 14
>Private-RPC-Socket: 390635 30 30
>Private-RPC-Socket: 390680 1 1
>Private-RPC-Socket: 390681 3 3
>Private-RPC-Socket: 390685 1 1
>Private-RPC-Socket: 390686 1 1
>~
>
>
>On Wed, 30 Aug 2006 14:17:04 -0700, Joe DeSouza <[EMAIL PROTECTED]>
>wrote:
>
>>I think Lindas problem is that it was working prior to some configuration
>changes in the firewall.. so I assumed that they already had these
>parameters set in the clients and the servers config file but the changes
>in the firewall configuration messed up these... so all they need to do is
>open those ports that were configured prior to the changes to the firewall
>configuration...
>>
>>Joe D'Souza
>>Remedy Developer / Consultant,
>>BearingPoint,
>>Virginia.
>>
>>
>>
>>----- Original Message ----
>>From: "McKenzie, James J C-E LCMC HQISEC/L3" <[EMAIL PROTECTED]>
>>To: [email protected]
>>Sent: Wednesday, August 30, 2006 4:56:51 PM
>>Subject: Re: 4.5.2 Notifier vs. Firewall issue
>>
>>**
>>Joe and Linda:
>>
>>If they are not set, set them. If you are in a WINDOWS environment, you
>will have to set these in WINDOWS not in the ar.ini file. This is for both
>server and client. If you are in UNIX, set them in the ar.conf file on the
>server and in the ar.ini file on the client (note 4.5.2 has a native UNIX
>client.) Sadly, I don't have my 4.5.2 guides anymore. It had a pretty
>picture of what Linda is trying to do and how to set it up.
>>
>>James McKenzie
>>L-3 GSI
>>
>>________________________________
>>From: Action Request System discussion list(ARSList)
>[mailto:[EMAIL PROTECTED] On Behalf Of Joe DeSouza
>>Sent: Wednesday, August 30, 2006 1:51 PM
>>To: [email protected]
>>Subject: Re: 4.5.2 Notifier vs. Firewall issue
>>
>>
>>**
>>Check your ar.conf file (if you are on UNIX) or ar.cfg file (if your
>server is windows) and look for the port numbers you have configured for
>ARNTTCPPORT and ARNTTCPCLIENTPORT on your clients ar.cfg file.. these are
>the ports that need to be allowed on your firewall..
>>
>>Hope that helps
>>
>>Joe D'Souza
>>Remedy Developer / Consultant,
>>BearingPoint,
>>Virginia.
>>
>>
>>----- Original Message ----
>>From: Linda M. King <[EMAIL PROTECTED]>
>>To: [email protected]
>>Sent: Wednesday, August 30, 2006 4:41:38 PM
>>Subject: 4.5.2 Notifier vs. Firewall issue
>>
>>
>>Hello all,
>>Company I work for made recent changes to their firewall and now users can
>>login to their Notifier 4.5.2 tools, but don't receive any notifications.
>>User & Admin tool access is fine.
>>They want to know what ports to open on the firewall so the Notifications
>>server & Notifier clients can communicate successfully.
>>I'm having trouble with what to tell them since all the knowledge base and
>>ARSlist archived articles are about Alert v. 5 and above and not Notifier
&
>>ARS server v4.5.2. The 4.5.2 documentation also hasn't been real helpful
>>and I'm not well-versed enough in this to direct the firewall guys
>>effectively where to look or what to try next.
>>Can someone point me to the info I'm missing or help out?
>>The 4.5.2 documentation says: "Remedy Notifier client connects to a
>>specific port of the Notification server, and registers with user
>>information. After verifying the user information on the AR System server,
>>the Notification server provides an acknowledgment to Remedy Notifier
>>client. Registration of Remedy Notifier with the Notification server is an
>>RPC call, and the responding acknowledgment is a TCP call using a
different
>>port. (excerpt is from page 150, Server_Admin_Guide.pdf v4.5)
>>Our 4.5.2 ARS server is set up to use (register with) portmapper and is
>>configured with a Server TCP/IP port 51586, Notifier Server TCP/IP port
>>51501. These ports have been opened on the firewall, and we've put the
TCP
>>port # in the Notifier tool, no luck. How do I determine what RPC port
>>notifier is using? I don't see anything relating to that in either the
>>nfy.conf or ar.conf files, just the TCP port settings.
>>What am I missing? Where should I (or the firewall/server folks) look
>next?
>>Thanks for any help!
>>Linda M. King
>>[EMAIL PROTECTED]
>>__________________________________________________________________________
_
>____
>>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
><http://www.wwrug.org/>
>>__20060125_______________________This posting was submitted with HTML in
>it___
>>__20060125_______________________This posting was submitted with HTML in
>it___
>>
>>__________________________________________________________________________
_
>____
>>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
>___________________________________________________________________________
____
>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
>___________________________________________________________________________
____
>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
