Actually, it probably isn't even probably either of them. It is the local tomcat installation home, which has a link to the manager.
On Tue, Mar 23, 2010 at 9:07 AM, Pid <p...@pidster.com> wrote: > On 23/03/2010 13:55, bill turner wrote: > >> On Tue, Mar 23, 2010 at 8:40 AM, Caldarale, Charles R< >> chuck.caldar...@unisys.com> wrote: >> >> From: bill.turner [mailto:worldwidewi...@gmail.com] >>>> Subject: newbie: accessing tomcat admin page from another machine >>>> >>>> I thought I should be able to access the administrator from >>>> other machines in my network using the latter but I cannot. >>>> >>> >>> What exactly do you mean by "administrator"? >>> >> >> >> Well, the administrator, which I thought was quite obvious, is the console >> one sees when you install tomcat, start it up and type in localhost:8080. >> I >> don't know how to be clearer than that. See the documentation. >> > > Perhaps you mean the 'manager' application? > The 'admin' application was discontinued in Tomcat 6.0, hence the query. > > > > p > > What exact URL are you using from the alternate machines? What exactly >>> happens when you try? (In case you haven't figured it out yet, you need >>> to >>> be specific when you report problems.) >>> >>> >> I thought the URL entered was fairly obvious. But, if not, here it is: >> http://hal9000:8080. That resulted in *Unable to Connect*. >> I also tried the ip address with the port number (see one of my other >> postings). That resulted in a timeout. >> Sorry for not being clearer. I guess I thought it was all obvious. >> >> >> I can see various hal9000 shared directories from windows >>>> explorer, including the tomcat home on hal9000. >>>> >>> >>> Not really relevant; that just shows Windows networking to be functional, >>> which uses different mechanisms to resolve host names. >>> >>> >> I realized that. I was just trying to show that I do have network >> connectivity. >> >> >> what I am doing wrong. >>>> >>> >>> 1) Is the name "hal9000" known via DNS to the other machines? >>> >>> >> No. I didn't think of that. :-( I don't have a DNS server running. This is >> a >> home network. It just never occurred to me. >> >> >> 2) Try using the fully qualified DNS name of the target machine. >>> >>> 3) Try using the IP address of the target machine. >>> >>> >> This just ended up with a timeout. >> >> >> 4) Insure that firewalls on hal9000 and the other machines are not >>> blocking >>> connections. >>> >>> >> I will have to check this. >> >> >> - Chuck >>> >>> >>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY >>> MATERIAL and is thus for use only by the intended recipient. If you >>> received >>> this in error, please contact the sender and delete the e-mail and its >>> attachments from all computers. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
