Re: Users going directly to WebSphere, not Apache, how to prevent?

[<Matt.Haas@xxxxxxxxxxx>]

You should look to see if WebSphere can be set to only accept traffic
from specific IP addresses. If so, just let it accept traffic from your
box's IP address(es) and 127.0.0.1. If not, you'll probably need to use
a firewall to block access to that port. There are some things built
into TCP/IP that let you control some of this stuff as well but I'm not
familiar with them.

Matt 

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Walden H. Leverich
Sent: Wednesday, September 20, 2006 12:07 PM
To: Web Enabling the AS400 / iSeries
Subject: [WEB400] Users going directly to WebSphere, not Apache,how to
prevent?

I posted this on Midrange-L, but Rob suggested this might be a good
forum too...


All,
 
I've got a situation where some users are going to directly to the
internal web server in WebSphere (portal) and not going through the
apache server front end to access my portal apps. I need to stop this. 
 
If I understand how the apache plug-in works, it effectively forwards
WebSphere traffic to the web server in WebSphere, but it does so
"internally." That's fine, but how do I stop users from accessing the
web server externally? In my case the WebSphere web server is running on
port 30020. 
 
And yes, I know, "there are rarely technical solutions to managerial
problems" so I should just tell the users not to go to 30020. <G>
 
-Walden
 
--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)