Dear all,
Am setting up an Aggregate Server in a new office environment. I
install Tomcat and I see it running (the Tomcat welcome page comes
up). I open the firewall "netsh firewall add portopening TCP 80 "ODK
Aggregate" ", then I move to another computer on the same network and
I try going to the IP address of the computer I have installed Tomcat
on from a browser. I get NO Tomcat Welcome page. I try installing on a
second and third machine just to eliminate the off chance that there
is a machine specific setting that is preventing my Tomcat Server
being accessed from a different machine. All three machines Tomcat
servers are inaccessible. Pinging them is not a problem, I get
replies. Am not sure what could be causing such behavious, it would be
useful if I could get some pointers so I know what to ask of the
network administrator (in case it is an issue of the network).
Any help greatly appreciated as always,
Tumaini
Pretty sure Tomcat runs HTTP on 8080 not 80. If you have HTTPS, it runs on 8443.
···
On Thu, May 24, 2012 at 8:14 AM, Tumaini Kilimba wrote:
> Dear all,
> Am setting up an Aggregate Server in a new office environment. I
> install Tomcat and I see it running (the Tomcat welcome page comes
> up). I open the firewall "netsh firewall add portopening TCP 80 "ODK
> Aggregate" ", then I move to another computer on the same network and
> I try going to the IP address of the computer I have installed Tomcat
> on from a browser. I get NO Tomcat Welcome page. I try installing on a
> second and third machine just to eliminate the off chance that there
> is a machine specific setting that is preventing my Tomcat Server
> being accessed from a different machine. All three machines Tomcat
> servers are inaccessible. Pinging them is not a problem, I get
> replies. Am not sure what could be causing such behavious, it would be
> useful if I could get some pointers so I know what to ask of the
> network administrator (in case it is an issue of the network).
>
> Any help greatly appreciated as always,
> Tumaini
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
First, confirm that you can open a browser on the local machine and see
Tomcat (e.g., http://localhost/).
It might very well be that you did not change the port to be port 80, but
are running with the default port 8080 (as Yaw notes); if that is the case,
you would need to specify http://localhost:8080/ to see Tomcat.
Then, confirm that the IP address you were using, and whatever port you
determined you needed (e.g., the :8080 or whatever) will get you to that
page, still from a browser on the machine running Tomcat. e.g.,
http://192.168.0.102/
Finally, move to another machine and see if that same URL works there. If
not, you need to look at your network, and involve your network admin.
Pinging is handled at a much lower layer and does not have anything to do
with Tomcat.
Mitch
···
On Thu, May 24, 2012 at 8:16 AM, Yaw Anokwa wrote:
Pretty sure Tomcat runs HTTP on 8080 not 80. If you have HTTPS, it runs on
8443.
On Thu, May 24, 2012 at 8:14 AM, Tumaini Kilimba tkilimba@ihi.or.tz wrote:
Dear all,
Am setting up an Aggregate Server in a new office environment. I
install Tomcat and I see it running (the Tomcat welcome page comes
up). I open the firewall "netsh firewall add portopening TCP 80 "ODK
Aggregate" ", then I move to another computer on the same network and
I try going to the IP address of the computer I have installed Tomcat
on from a browser. I get NO Tomcat Welcome page. I try installing on a
second and third machine just to eliminate the off chance that there
is a machine specific setting that is preventing my Tomcat Server
being accessed from a different machine. All three machines Tomcat
servers are inaccessible. Pinging them is not a problem, I get
replies. Am not sure what could be causing such behavious, it would be
useful if I could get some pointers so I know what to ask of the
network administrator (in case it is an issue of the network).
Any help greatly appreciated as always,
Tumaini
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
Thanks guys. However, I had done all that before opening this ticket. I had
installed tomcat to run on port 80, and http://localhost/ works fine, I
see the welcome screen for Tomcat. I also *did *try using my IP
http://192.168.1.35/ and that too gives me the Tomcat welcome screen. The
issue is when I try and browse to http://192.168.1.35/ from a different
machine, I get NO welcome screen, I get an error:
The server at http can't be found, because the DNS lookup failed. DNS is
the web service that translates a website's name to its Internet address.
This error is most often caused by having no connection to the Internet or
a misconfigured network. It can also be caused by an unresponsive DNS
server or a firewall preventing Google Chrome from accessing the network.
Here are some suggestions:
- Reload http://http//192.168.2.65 this web page later.
- Check your Internet connection. Reboot any routers, modems, or other
network devices you may be using.
- Check your DNS settings. Contact your network administrator if you're
not sure what this means.
- Try disabling network prediction by following these steps: Go to *Wrench
menu > Options > Under the Hood *and deselect "Predict network actions
to improve page load performance." If this does not resolve the issue,
we recommend selecting this option again for improved performance.
- Try adding Google Chrome as a permitted program in your firewall or
antivirus software's settings. If it is already a permitted program, try
deleting it from the list of permitted programs and adding it again.
- If you use a proxy server, check your proxy settings or check with
your network administrator to make sure the proxy server is working.
- If you don't believe you should be using a proxy server, try the
following steps: Go to *Wrench menu > Options > Under the Hood > Change
proxy settings > LAN Settings *and deselect "Use a proxy server for your
LAN."
Error 105 (net::ERR_NAME_NOT_RESOLVED): Unable to resolve the server's DNS
address.
What sort of network issues could be causing this, as am quite confident
Tomcat is running on port 80 on my machine, and am trying to access my
machine from another machine within the same domain. I need to be able to
articulate to the network administrators what needs to be done to
facilitate tomcat serving up pages to other machines, so any pointers on
what I could ask them to check for would be great.
Any help appreciated,
Tumaini
···
On Thu, May 24, 2012 at 7:29 PM, Mitch S wrote:
First, confirm that you can open a browser on the local machine and see
Tomcat (e.g., http://localhost/).
It might very well be that you did not change the port to be port 80, but
are running with the default port 8080 (as Yaw notes); if that is the case,
you would need to specify http://localhost:8080/ to see Tomcat.
Then, confirm that the IP address you were using, and whatever port you
determined you needed (e.g., the :8080 or whatever) will get you to that
page, still from a browser on the machine running Tomcat. e.g.,
http://192.168.0.102/
Finally, move to another machine and see if that same URL works there. If
not, you need to look at your network, and involve your network admin.
Pinging is handled at a much lower layer and does not have anything to do
with Tomcat.
Mitch
On Thu, May 24, 2012 at 8:16 AM, Yaw Anokwa yanokwa@gmail.com wrote:
Pretty sure Tomcat runs HTTP on 8080 not 80. If you have HTTPS, it runs
on 8443.
On Thu, May 24, 2012 at 8:14 AM, Tumaini Kilimba tkilimba@ihi.or.tz wrote:
Dear all,
Am setting up an Aggregate Server in a new office environment. I
install Tomcat and I see it running (the Tomcat welcome page comes
up). I open the firewall "netsh firewall add portopening TCP 80 "ODK
Aggregate" ", then I move to another computer on the same network and
I try going to the IP address of the computer I have installed Tomcat
on from a browser. I get NO Tomcat Welcome page. I try installing on a
second and third machine just to eliminate the off chance that there
is a machine specific setting that is preventing my Tomcat Server
being accessed from a different machine. All three machines Tomcat
servers are inaccessible. Pinging them is not a problem, I get
replies. Am not sure what could be causing such behavious, it would be
useful if I could get some pointers so I know what to ask of the
network administrator (in case it is an issue of the network).
Any help greatly appreciated as always,
Tumaini
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
PS - I also tried disabling my antivirus just in case that was the
cause.... no joy.
···
On Thursday, May 24, 2012 8:33:18 PM UTC+3, Tumaini Kilimba wrote:
>
> Thanks guys. However, I had done all that before opening this ticket. I
> had installed tomcat to run on port 80, and http://localhost/ works
> fine, I see the welcome screen for Tomcat. I also *did *try using my IP
> http://192.168.1.35/ and that too gives me the Tomcat welcome screen. The
> issue is when I try and browse to http://192.168.1.35/ from a different
> machine, I get NO welcome screen, I get an error:
>
> The server at *http* can't be found, because the DNS lookup failed. DNS
> is the web service that translates a website's name to its Internet
> address. This error is most often caused by having no connection to the
> Internet or a misconfigured network. It can also be caused by an
> unresponsive DNS server or a firewall preventing Google Chrome from
> accessing the network.
> Here are some suggestions:
>
> - Reload this web page later.
> - Check your Internet connection. Reboot any routers, modems, or other
> network devices you may be using.
> - Check your DNS settings. Contact your network administrator if
> you're not sure what this means.
> - Try disabling network prediction by following these steps: Go to *Wrench
> menu > Options > Under the Hood *and deselect "Predict network actions
> to improve page load performance." If this does not resolve the issue,
> we recommend selecting this option again for improved performance.
> - Try adding Google Chrome as a permitted program in your firewall or
> antivirus software's settings. If it is already a permitted program, try
> deleting it from the list of permitted programs and adding it again.
> - If you use a proxy server, check your proxy settings or check with
> your network administrator to make sure the proxy server is working.
> - If you don't believe you should be using a proxy server, try the
> following steps: Go to *Wrench menu > Options > Under the Hood >
> Change proxy settings > LAN Settings *and deselect "Use a proxy server
> for your LAN."
>
> Error 105 (net::ERR_NAME_NOT_RESOLVED): Unable to resolve the server's DNS
> address.
>
> What sort of network issues could be causing this, as am quite confident
> Tomcat is running on port 80 on my machine, and am trying to access my
> machine from another machine within the same domain. I need to be able to
> articulate to the network administrators what needs to be done to
> facilitate tomcat serving up pages to other machines, so any pointers on
> what I could ask them to check for would be great.
>
> Any help appreciated,
> Tumaini
>
> On Thu, May 24, 2012 at 7:29 PM, Mitch S wrote:
>
>> First, confirm that you can open a browser on the local machine and see
>> Tomcat (e.g., http://localhost/).
>> It might very well be that you did not change the port to be port 80, but
>> are running with the default port 8080 (as Yaw notes); if that is the case,
>> you would need to specify http://localhost:8080/ to see Tomcat.
>>
>> Then, confirm that the IP address you were using, and whatever port you
>> determined you needed (e.g., the :8080 or whatever) will get you to that
>> page, still from a browser on the machine running Tomcat. e.g.,
>> http://192.168.0.102/
>>
>> Finally, move to another machine and see if that same URL works there.
>> If not, you need to look at your network, and involve your network admin.
>>
>> Pinging is handled at a much lower layer and does not have anything to do
>> with Tomcat.
>>
>> Mitch
>>
>>
>>
>> On Thu, May 24, 2012 at 8:16 AM, Yaw Anokwa wrote:
>>
>>> Pretty sure Tomcat runs HTTP on 8080 not 80. If you have HTTPS, it runs
>>> on 8443.
>>>
>>> On Thu, May 24, 2012 at 8:14 AM, Tumaini Kilimba wrote:
>>> > Dear all,
>>> > Am setting up an Aggregate Server in a new office environment. I
>>> > install Tomcat and I see it running (the Tomcat welcome page comes
>>> > up). I open the firewall "netsh firewall add portopening TCP 80 "ODK
>>> > Aggregate" ", then I move to another computer on the same network and
>>> > I try going to the IP address of the computer I have installed Tomcat
>>> > on from a browser. I get NO Tomcat Welcome page. I try installing on a
>>> > second and third machine just to eliminate the off chance that there
>>> > is a machine specific setting that is preventing my Tomcat Server
>>> > being accessed from a different machine. All three machines Tomcat
>>> > servers are inaccessible. Pinging them is not a problem, I get
>>> > replies. Am not sure what could be causing such behavious, it would be
>>> > useful if I could get some pointers so I know what to ask of the
>>> > network administrator (in case it is an issue of the network).
>>> >
>>> > Any help greatly appreciated as always,
>>> > Tumaini
>>> >
>>> > --
>>> > Post: opendatakit@googlegroups.com
>>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> > Options: http://groups.google.com/group/opendatakit?hl=en
>>>
>>> --
>>> Post: opendatakit@googlegroups.com
>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>>
>>
>>
>>
>> --
>> Mitch Sundt
>> Software Engineer
>> University of Washington
>> mitchellsundt@gmail.com
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
>
The error message seems to indicate that it is trying to find the hostname
"http", and is not looking for 192.168.1.35.
You might check that you are browsing to the url http://192.168.1.35/ and
not http://http://192.168.1.35/
Mitch
···
On Thu, May 24, 2012 at 11:40 AM, Tumaini Kilimba wrote:
PS - I also tried disabling my antivirus just in case that was the
cause.... no joy.
On Thursday, May 24, 2012 8:33:18 PM UTC+3, Tumaini Kilimba wrote:
Thanks guys. However, I had done all that before opening this ticket. I
had installed tomcat to run on port 80, and http://localhost/ works
fine, I see the welcome screen for Tomcat. I also *did *try using my IP
http://192.168.1.35/ and that too gives me the Tomcat welcome
screen. The issue is when I try and browse to http://192.168.1.35/ from
a different machine, I get NO welcome screen, I get an error:
The server at http can't be found, because the DNS lookup failed. DNS
is the web service that translates a website's name to its Internet
address. This error is most often caused by having no connection to the
Internet or a misconfigured network. It can also be caused by an
unresponsive DNS server or a firewall preventing Google Chrome from
accessing the network.
Here are some suggestions:
- Reload http://http//192.168.2.65 this web page later.
- Check your Internet connection. Reboot any routers, modems, or
other network devices you may be using.
- Check your DNS settings. Contact your network administrator if
you're not sure what this means.
- Try disabling network prediction by following these steps: Go to *Wrench
menu > Options > Under the Hood *and deselect "Predict network
actions to improve page load performance." If this does not resolve
the issue, we recommend selecting this option again for improved
performance.
- Try adding Google Chrome as a permitted program in your firewall or
antivirus software's settings. If it is already a permitted program, try
deleting it from the list of permitted programs and adding it again.
- If you use a proxy server, check your proxy settings or check with
your network administrator to make sure the proxy server is working.
- If you don't believe you should be using a proxy server, try the
following steps: Go to *Wrench menu > Options > Under the Hood >
Change proxy settings > LAN Settings *and deselect "Use a proxy
server for your LAN."
Error 105 (net::ERR_NAME_NOT_RESOLVED): Unable to resolve the server's
DNS address.
What sort of network issues could be causing this, as am quite confident
Tomcat is running on port 80 on my machine, and am trying to access my
machine from another machine within the same domain. I need to be able to
articulate to the network administrators what needs to be done to
facilitate tomcat serving up pages to other machines, so any pointers on
what I could ask them to check for would be great.
Any help appreciated,
Tumaini
On Thu, May 24, 2012 at 7:29 PM, Mitch S mitchellsundt@gmail.com wrote:
First, confirm that you can open a browser on the local machine and see
Tomcat (e.g., http://localhost/).
It might very well be that you did not change the port to be port 80,
but are running with the default port 8080 (as Yaw notes); if that is the
case, you would need to specify http://localhost:8080/ to see Tomcat.
Then, confirm that the IP address you were using, and whatever port you
determined you needed (e.g., the :8080 or whatever) will get you to that
page, still from a browser on the machine running Tomcat. e.g.,
http://192.168.0.102/
Finally, move to another machine and see if that same URL works there.
If not, you need to look at your network, and involve your network admin.
Pinging is handled at a much lower layer and does not have anything to
do with Tomcat.
Mitch
On Thu, May 24, 2012 at 8:16 AM, Yaw Anokwa yanokwa@gmail.com wrote:
Pretty sure Tomcat runs HTTP on 8080 not 80. If you have HTTPS, it runs
on 8443.
On Thu, May 24, 2012 at 8:14 AM, Tumaini Kilimba tkilimba@ihi.or.tz wrote:
Dear all,
Am setting up an Aggregate Server in a new office environment. I
install Tomcat and I see it running (the Tomcat welcome page comes
up). I open the firewall "netsh firewall add portopening TCP 80 "ODK
Aggregate" ", then I move to another computer on the same network and
I try going to the IP address of the computer I have installed Tomcat
on from a browser. I get NO Tomcat Welcome page. I try installing on a
second and third machine just to eliminate the off chance that there
is a machine specific setting that is preventing my Tomcat Server
being accessed from a different machine. All three machines Tomcat
servers are inaccessible. Pinging them is not a problem, I get
replies. Am not sure what could be causing such behavious, it would be
useful if I could get some pointers so I know what to ask of the
network administrator (in case it is an issue of the network).
Any help greatly appreciated as always,
Tumaini
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@**googlegroups.comopendatakit%2Bunsubscribe@googlegroups.com
Options: http://groups.google.com/**group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@**googlegroups.comopendatakit%2Bunsubscribe@googlegroups.com
Options: http://groups.google.com/**group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@**googlegroups.comopendatakit%2Bunsubscribe@googlegroups.com
Options: http://groups.google.com/**group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en
--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com