You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Natasha Popoola <ta...@gmail.com> on 2008/03/26 16:36:00 UTC
problem using DynDNS
Hi,
Newbie question unfortunately....I am attempting to host a servlet, it works fine using http://localhost:8080/Project/servlet/Servlet but I have set up dyndns so it's accessible outside of my network, http://npopoola.doesntexist.com brings up my router set up page so I assume that dyndns is working OK.
But when I try to access the servlet using http://npopoola.doesntexist.com:8080/Project/servlet/Servlet, I get "The connection to the server was reset while the page was loading.". If I try it without specifying the port number, http://npopoola.doesntexist.com/Project/servlet/Servlet, it just says '404 Not Found'.
I have implemented port forwarding for 8080 and stopped the firewall from blocking 8080... does anyone know what I am doing wrong?
Thanks,
Natasha.
_________________________________________________________________
Win 100’s of Virgin Experience days with BigSnapSearch.com
http://www.bigsnapsearch.com
RE: problem using DynDNS
Posted by Natasha Popoola <ta...@hotmail.com>.
Well as my servlet will only be communicating with mobile phones, this is not really a problem. I tried to access the servlet from my mobile and I get the null pointer also, so everything *appears* to be OK.
Thanks again for your help.
> Date: Wed, 26 Mar 2008 13:05:27 -0400
> From: chris@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: problem using DynDNS
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Natasha,
>
> Natasha Popoola wrote:
> | Hmm... well a null pointer exception is what I am supposed to get if
> it is working, I wonder why I get the router setup page then...
> | Thanks for your help anyway.
>
> It's possible that your router is out-smarting you by handling
> connections to the external interface (via the public IP address) as if
> they were connections on the internal interface (via your private
> 192.168.x.y IP address). Technically, your request should be hitting the
> external interface and routed properly, even though you are on the
> "inside" of the network.
>
> You should make sure that your DNS resolver is giving you the expected
> (external) IP address, just in case.
>
> You might want to check to see if your router has a firmware upgrade
> that could fix this, if it truly is the problem.
>
> Another option is to use a client outside your network (which isn't
> particularly convenient, but it should work).
>
> Good luck,
> - -chris
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkfqglcACgkQ9CaO5/Lv0PAGZQCgg2P6xdMkcyYtJepET5x0lO8A
> FEMAnAgwmtx0sQMhgvPUCWi0wCDrAB1l
> =bVC7
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
_________________________________________________________________
Get Hotmail on your mobile. Text MSN to 63463 now!
http://mobile.uk.msn.com/pc/mail.aspx
Re: problem using DynDNS
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Natasha,
Natasha Popoola wrote:
| Hmm... well a null pointer exception is what I am supposed to get if
it is working, I wonder why I get the router setup page then...
| Thanks for your help anyway.
It's possible that your router is out-smarting you by handling
connections to the external interface (via the public IP address) as if
they were connections on the internal interface (via your private
192.168.x.y IP address). Technically, your request should be hitting the
external interface and routed properly, even though you are on the
"inside" of the network.
You should make sure that your DNS resolver is giving you the expected
(external) IP address, just in case.
You might want to check to see if your router has a firmware upgrade
that could fix this, if it truly is the problem.
Another option is to use a client outside your network (which isn't
particularly convenient, but it should work).
Good luck,
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkfqglcACgkQ9CaO5/Lv0PAGZQCgg2P6xdMkcyYtJepET5x0lO8A
FEMAnAgwmtx0sQMhgvPUCWi0wCDrAB1l
=bVC7
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: problem using DynDNS
Posted by Natasha Popoola <ta...@hotmail.com>.
Hmm... well a null pointer exception is what I am supposed to get if it is working, I wonder why I get the router setup page then...
Thanks for your help anyway.
> Date: Wed, 26 Mar 2008 12:48:12 -0400
> From: chris@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: problem using DynDNS
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Natasha,
>
> Natasha Popoola wrote:
> | I have set up dyndns so it's accessible outside of my network,
> | http://npopoola.doesntexist.com brings up my router set up page so I
> | assume that dyndns is working OK.
>
> You may want to change that... you certainly don't want anyone outside
> your network to start messing with your router configuration ;)
>
> | But when I try to access the servlet using
> | http://npopoola.doesntexist.com:8080/Project/servlet/Servlet, I get
> | "The connection to the server was reset while the page was loading.".
> | If I try it without specifying the port number,
> | http://npopoola.doesntexist.com/Project/servlet/Servlet, it just says
> | '404 Not Found'.
> |
> | I have implemented port forwarding for 8080 and stopped the firewall
> | from blocking 8080... does anyone know what I am doing wrong?
>
> I get an NPE when I hit that URL. Does that mean you've solved the problem?
>
> It is possible that you had a <Host> that was not the default host which
> was serving your webapp. If you have <Host name="foo"> and try to access
> it with http://bar/webappName Tomcat will not allow access. However, if
> you have <Engine defaultHost="foo">, then requests to
> http://bar/webappName /will/ go to foo (unless "bar" is also defined as
> a Host).
>
> Hope that helps,
> - -chris
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkfqfkwACgkQ9CaO5/Lv0PD1OgCfaJaQagzsGIq5n/9xy1gsN8yo
> zsAAoJ6D5aOi10iYch8sG/kixMJKzBZp
> =zy4z
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
_________________________________________________________________
The next generation of Windows Live is here
http://www.windowslive.co.uk/get-live
Re: problem using DynDNS
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Natasha,
Natasha Popoola wrote:
| I have set up dyndns so it's accessible outside of my network,
| http://npopoola.doesntexist.com brings up my router set up page so I
| assume that dyndns is working OK.
You may want to change that... you certainly don't want anyone outside
your network to start messing with your router configuration ;)
| But when I try to access the servlet using
| http://npopoola.doesntexist.com:8080/Project/servlet/Servlet, I get
| "The connection to the server was reset while the page was loading.".
| If I try it without specifying the port number,
| http://npopoola.doesntexist.com/Project/servlet/Servlet, it just says
| '404 Not Found'.
|
| I have implemented port forwarding for 8080 and stopped the firewall
| from blocking 8080... does anyone know what I am doing wrong?
I get an NPE when I hit that URL. Does that mean you've solved the problem?
It is possible that you had a <Host> that was not the default host which
was serving your webapp. If you have <Host name="foo"> and try to access
it with http://bar/webappName Tomcat will not allow access. However, if
you have <Engine defaultHost="foo">, then requests to
http://bar/webappName /will/ go to foo (unless "bar" is also defined as
a Host).
Hope that helps,
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkfqfkwACgkQ9CaO5/Lv0PD1OgCfaJaQagzsGIq5n/9xy1gsN8yo
zsAAoJ6D5aOi10iYch8sG/kixMJKzBZp
=zy4z
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org