|
Here you will find a PC tool that works well to identify the web server running at a URL (it can do other ports too). http://grc.com/id/idserve.htm My AS/400 web server showed correctly until I applied the ID blocking PTF for security. --- Douglas Hart - Sr. Consultant Certified IBM iSeries System Administrator mailto:dhart2@twcny.rr.com Web: http://dhart.no-ip.info > -----Original Message----- > From: midrange-l-bounces+doughart=twcny.rr.com@midrange.com > [mailto:midrange-l-bounces+doughart=twcny.rr.com@midrange.com]On Behalf > Of Narayanan R Pillai > Sent: Tuesday, January 21, 2003 4:30 PM > To: Midrange Systems Technical Discussion > Subject: Re: Jetty on the AS/400 ? > > > David, > > You are right. It will not even tell you if a webserver is > running on that > port, just that "something" is listening on that well known port. > But on the > AS400, if you do a netstat *CNN, it will give you a list with an option > "8=Display Jobs", will it not ? Then an option 8 on the "local-port" > www-http will tell you what job is running listening on that > port. If it is > ( let us say ) DEFAULT QTMHHTTP, then may we not assume that it is the > IBM-Apache httpd running ? If it is something else, would that not be a > starting point to check ? > > Narayanan R Pillai > > > > > ----- Original Message ----- > From: "David Gibbs" <david@midrange.com> > To: <midrange-l@midrange.com> > Sent: Tuesday, January 21, 2003 4:02 PM > Subject: Re: Jetty on the AS/400 ? > > > > "Narayanan R Pillai" <strqst400=/E1597aS9LQAvxtiuMwx3w@public.gmane.org> > > wrote in message 01d901c2c18e$b59a2490$5905000a@ITSPILLAN">news:01d901c2c18e$b59a2490$5905000a@ITSPILLAN... > > > Will it make sense to do a netstat *cnn and check if port 80 is on a > > listen > > > mode ? > > > > That won't tell you anything ... standard web server listens on port 80. > > > > david > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > > To post a message email: MIDRANGE-L@midrange.com > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l > > or email: MIDRANGE-L-request@midrange.com > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) > mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.