How is the /etc/hosts file set up? If /etc/hosts has entries for B, C, and D in it then Remedy will never go outside the firewall.
# # Internet host table # 127.0.0.1 localhost 192.168.1.1 a a.mydomain.net 192.168.1.2 b b.mydomain.net 192.168.1.3 c c.mydomain.net 192.168.1.4 d d.mydomain.net Or 192.168.1.1 a a.mydomain.net b b.mydomain.net c c.mydomain.net d d.mydomain.net FYI: We are on Solaris and we use the 1st method (giving each logical server it's own IP). Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow Sent: Thursday, February 28, 2008 3:06 PM To: [email protected] Subject: Re: Two quick port questions Let's throw a wrench in there. We have a physical Solaris host named "A". It has 3 logical servers B,C, and D on it. Each of these logical servers is installed with an identical Remedy install EXCEPT none use portmapper so they all have specific ports specified. Box B uses ports 7800/7801 for arserver/pluginserver, C uses 7900/7901, etc. If logical box "B" tries to ping itself as b:7801 and is using it's logical name - would it route outside of the machine to the firewall? I have no idea. The name "B" is not the same as the physical host name "A" so how is this resolved? Each port had to be specifically opened on the firewall and we only opened the AR Server ports (7800, 7900, etc). Otherwise they are non-routable. I also tried adding this: Server-Plugin-Alias: REMEDY.ARF.SLASETUP REMEDY.ARF.SLASETUP using localhost:7801 ...it didn't work - so I tried: Server-Alias: REMEDY.ARF.SLASETUP REMEDY.ARF.SLASETUP using B:7801 (where B is the actual logical server name). I did NOT try the physical server name... -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of William H. Will Du Chene Sent: Thursday, February 28, 2008 2:06 PM To: [email protected] Subject: Re: Two quick port questions A port is more or less like a cell phone. Most of us carry one for use, and likewise, each of us prefer to have our own. When we have to share them with others, the situation that it creates is somewhat awkward. The very same thing is true communications ports. First question - yes. The AR System server and the plug in server cannot share the same port. There is nothing that says that they cannot be one port up from each other, however. Second question - No. The AR System server should be able to connect to it locally provided that it knows what port the server is on. Interestingly enough, I am not sure if a remote address can connect to a plugin server like that. I've never tried. Just for the sake of curiousity, it would be neat if someone could try it and post the answer. HTH. > William, > > Others will let me know if I am wrong, but I think internal unless you > are using some code (api) to talk to the plugin from out side the box. > > hbr > > On Thu, Feb 28, 2008 at 2:44 PM, William Rentfrow < > [EMAIL PROTECTED]> wrote: > >> ** AR Server 7.1 patch 001 on Solaris - SLM 7.1/IM 7.03 >> >> Does the plugin server port have to be different than the ar server >> port if you are not using portmapper? I believe so...but nothing >> explicitly says so in the docs for 7.1 >> >> Also, let's assume the arserver is on port 7800 and the plugin-port >> is configured to be 7801. Does port 7801 have to be open to the >> outside world? Or does it just communicate with the arserver? >> >> William Rentfrow, Principal Consultant [EMAIL PROTECTED] C >> 701-306-6157 O 952-432-0227 >> > > > -- > Howard Richter > ITIL Foundation Certified > Red Hat Certified Technician > CompTIA Linux+ Certified > [EMAIL PROTECTED] > Resume = http://hotjobs.yahoo.com/resumes/hrichter_1/masterresume20(2) > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
