tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Brownlee" <osaru_onl...@hotmail.com>
Subject Re: Accessing localhost from a remote computer
Date Tue, 22 Apr 2003 03:42:39 GMT
Sorry, I jumped into the middle of the thread.  I think Tim's last answer is 
what you need.  However, since you know that the connector your interested 
in is binding to port 8080, search your server.xml file for the <Connector> 
tag with port="8080" and see if it also contains the address="localhost" or 
address="127.x.x.x" attribute as Tim suggested.  If you find it, you can 
remove the address attribute.  If that doesn't help, you might ask to check 
the server.xml file on one of the other student's machines.






>From: "JS" <smartt@dcs.kcl.ac.uk>
>Reply-To: smartt@dcs.kcl.ac.uk
>To: <tomcat-user@jakarta.apache.org>
>Subject: Re: Accessing localhost from a remote computer
>Date: Tue, 22 Apr 2003 04:14:01 +0100 (BST)
>
>Hi there, thanks for that.... got a helpful output.
>I can see that the localhost IP adderess.
>
>This is now what I get.
>C:\>netstat -an
>
>Active Connections
>
>   Proto  Local Address          Foreign Address        State
>   TCP    0.0.0.0:1287           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1288           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1291           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1292           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1293           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1298           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1304           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:1305           0.0.0.0:0              LISTENING
>   TCP    127.0.0.1:1032         0.0.0.0:0              LISTENING
>   TCP    127.0.0.1:1073         0.0.0.0:0              LISTENING
>   TCP    127.0.0.1:8005         0.0.0.0:0              LISTENING
>  * TCP    127.0.0.1:8080         0.0.0.0:0              LISTENING
>   TCP    127.0.0.1:8081         0.0.0.0:0              LISTENING
>   TCP    192.168.5.101:1287     137.73.8.3:3128        CLOSE_WAIT
>   TCP    192.168.5.101:1288     137.73.8.3:3128        CLOSE_WAIT
>   TCP    192.168.5.101:1291     137.73.8.3:3128        CLOSE_WAIT
>   TCP    192.168.5.101:1292     137.73.8.3:3128        CLOSE_WAIT
>   TCP    192.168.5.101:1293     137.73.8.3:3128        CLOSE_WAIT
>   TCP    192.168.5.101:1298     137.73.8.3:3128        CLOSE_WAIT
>   TCP    192.168.5.101:1304     137.73.8.3:3128        CLOSE_WAIT
>   TCP    192.168.5.101:1305     137.73.8.3:3128        CLOSE_WAIT
>   TCP    192.168.5.101:137      0.0.0.0:0              LISTENING
>   TCP    192.168.5.101:138      0.0.0.0:0              LISTENING
>   TCP    192.168.5.101:139      0.0.0.0:0              LISTENING
>   UDP    127.0.0.1:1032         *:*
>   UDP    127.0.0.1:1073         *:*
>   UDP    192.168.5.101:137      *:*
>   UDP    192.168.5.101:138      *:*
>
>As u can see, everything is fine on local host where I've added the '*',
>but on the second IP address, the 192 one, no luck... any other insight??
>Cheers
>
> > try using netstat -an (the "n" causes netstat to print numbers instead
> > of  resolving host names and protocols).
> >
> >>From: "JS" <smartt@dcs.kcl.ac.uk>
> >>Reply-To: smartt@dcs.kcl.ac.uk
> >>To: <tomcat-user@jakarta.apache.org>
> >>Subject: Re: Accessing localhost from a remote computer
> >>Date: Tue, 22 Apr 2003 02:55:55 +0100 (BST)
> >>
> >>Hi Tim,
> >>much appreciated cheers.
> >>Here's the latest:
> >>
> >>I ran netstat, output is below...
> >>C:\WINDOWS\jwsdp-1_0_01>netstat -a
> >>
> >>Active Connections
> >>
> >>   Proto  Local Address          Foreign Address        State
> >>   TCP    oemcomputer:8080       OEMCOMPUTER:0          LISTENING TCP
> >>    oemcomputer:8081       OEMCOMPUTER:0          LISTENING TCP
> >>   oemcomputer:1032       OEMCOMPUTER:0          LISTENING TCP
> >>   oemcomputer:1073       OEMCOMPUTER:0          LISTENING TCP
> >>   oemcomputer:1168       OEMCOMPUTER:0          LISTENING TCP
> >>   oemcomputer:137        OEMCOMPUTER:0          LISTENING TCP
> >>   oemcomputer:138        OEMCOMPUTER:0          LISTENING TCP
> >>   oemcomputer:nbsession  OEMCOMPUTER:0          LISTENING UDP
> >>   oemcomputer:1032       *:*
> >>   UDP    oemcomputer:1073       *:*
> >>   UDP    oemcomputer:1168       *:*
> >>   UDP    oemcomputer:nbname     *:*
> >>   UDP    oemcomputer:nbdatagram  *:*
> >>
> >>Is everything in order here??
> >>
> >>Back in server.xml, there are no address attributes with the connector
> >>elements. In fact, no address attrbutes in the whole file.Is there a
> >>specific order for the use of atrtributes??
> >>
> >>Thanks again.
> >>
> >> > Oops, yeah, server.xml.
> >> >
> >> > <Connector address='localhost' >
> >> > or
> >> > <Connector address='127.0.0.1' >
> >> >
> >> > Run netstat -a
> >> > With any luck you'll see: (or close with a lot more stuff)
> >> >
> >> > Active Connections
> >> >
> >> >   Proto  Local Address          Foreign Address        State
> >> >   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
> >> >
> >> >
> >> > -Tim
> >> >
> >> > JS wrote:
> >> >> Hi Tim,
> >> >> I'm assuming you meant server.xml?????
> >> >> If so, I checked, and got a bit lost. There's a load of extra bits
> >> >> in there relating to the JWSDP.
> >> >> Under the GlobalNamingResources attribute, there are 2 services
> >> >> defined... i.e.<service>
> >> >> ....
> >> >> ...</service>
> >> >> <service>
> >> >> ...
> >> >> ...
> >> >> </service>
> >> >>
> >> >> Both of them have connecter elements defined inside them. Which
> >> >> attributes am I looking for to make sure it is bound to
> >> >> "localhost"? Thanks for your help
> >> >> J
> >> >>
> >> >>
> >> >>>Check the lines that say:
> >> >>><Connector ... >
> >> >>>and see if it is explicitly binding to localhost (and only
> >> >>>localhost)
> >> >>>
> >> >>>-Tim
> >> >>>
> >> >>>
> >> >>>JS wrote:
> >> >>>
> >> >>>>Hi there, has anyone experienced this problem before.
> >> >>>>Basically, I have connected my laptop to the university network
> >> >>>>and have an IP allocated to my machine automatically.
> >> >>>>Most students who are using tomcat can then log onto another
of
> >> >>>>the machines on the network and browse the apps on their
> >> >>>>localhost. For some reason I cannot do this when I have my tomcat
> >> >>>>server running. Is there a setting that I need to activate so
that
> >> >>>>I can look at my machine remotely??? By the way, Im the only
one
> >> >>>>who is using the Java Web Services Developer Pack, which has
a
> >> >>>>preinstalled version of tomcat 4.1.2 Thanks
> >> >>>>
> >> >>>
> >> >>>
> >> 
> >>>---------------------------------------------------------------------
> >> >>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >> >>>For additional commands, e-mail:
> >> >>>tomcat-user-help@jakarta.apache.org
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> 
>---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >> >> For additional commands, e-mail:
> >> >> tomcat-user-help@jakarta.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >>
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For
> >>additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >>
> >
> > _________________________________________________________________
> > The new MSN 8: advanced junk mail protection and 2 months FREE*
> > http://join.msn.com/?page=features/junkmail
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For
> > additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online  
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message