You cant really use portmapper behind a firewall. You have to specify a TCP port. Basically, this is what happens:
Using Portmapper: - AR Client connects to UDP port 111 and asks what TCP port is arserver running on? - portmapper replies "on this instance, its on XXX" - AR Client says "thanks" and connects using TCP to that port. This port can change everytime the arserver restarts. So the firewall will never know or can not guess. What you need to do is forget about UDP 111. Select a TCP port that is not used, open the Admin tool >> server information >> connection ports and settings and put a TCP port in there. The AR server will need to be restarted. Tell the firewall/network people the new TCP port number, TCP 80 for midtier. Depending on the mail setup you have, and on what OS. But TCP 25 is the norm. Kind regards Danny Kellett Quoting "Dignard, Norman" <[EMAIL PROTECTED]>: > > > Can someone tell me all the ports and protocols required to allow AR to > function behind a firewall using both AR client and Web . > > We're running v7.01 patch 2. We have an AR server running Oracle 10g on > and HPUX box with email and a Web server running apache/tomcat. > > > > From what I've been able to discern from the docs and support we need > the following bi directional access > > > > 25 - for email > > 80 - for web access > > 111 - we are using the default install with port mapper. > > > > Do both TCP/UDP need to be enabled for each port? Any others RPC ..... > > > > The documentation is not very clear. Please advise. > > > > > > Regards, > > Norm > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the > Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
