Win a copy of Mesos in Action this week in the Cloud/Virtualizaton forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Tomcat hosting on my local system over internet

 
Sanjaykar Gurram
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi

Sorry, I am not sure if this the right place to post this thread. Actually am looking to host a web application in my local machine(laptop)
using tomcat and make it available over the internet. As my ISP provides me dynamic IP i am using DlinkDDNS for DNS name, for which i configured
in my Dlink wireless router. I made few configurations in my Router so that all requests on port 80 will be redirected to my laptop.

But what happens is nothing, only in my laptop i could access my tomcat home page using DNS name but not in other systems(laptop).

Please guide me in doing this, any good pointers is appreciated.


Thanks,
Gurram
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18156
53
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's possible that your ISP has blocked port 80 serving at their firewall. A lot of ISPs have a "consume-only" clause in their contracts, and it's only because it's a legal restriction without the technical blocking that allows people to host anyway.
 
bhanu chowdary
Ranch Hand
Posts: 256
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Forgive my ignorance.
I always though that for hosting a web application over the internet we have to buy a domain space.
I am totally confused now. Could you please let me know what are the steps that I have to follow so that a simple "hello world" application hosted in my tomcat will be available over the internet??
 
Tim Holloway
Saloon Keeper
Pie
Posts: 18156
53
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
To host a web application, all you need to do is connect a server to the Internet.

However, very few people can remember 216.199.14.18, so I also bought the domain name "mousetech.com" from a domain registration service. Then I set up 2 domain name servers (1 primary and 1 backup) and attached them to the Internet. A lot of people find this to be inconvenient, however, so you can pay someone else such as your ISP or registration service to do the domain name serving (DNS). All DNS is is just the Internet's equivalent of a telephone book for computers. Your browser wants to connect to my webserver, so it makes a DNS request for the IP address of www.mousetech.com. DNS responds with 216.199.14.18 and that's what your browser will plug into the destination address of its tcp/ip packets.

Note that there can be multiple servers in one domain. So my domain is "mousetech.com", but the fully-qualified domain name (FQDN) for my webserver is www.mousetech.com. As opposed to my mailserver, which is mail2.mousetech.com. The mail server is on a different machine with a different IP address, but that's just because I believe in spreading the load around.

So anyone can access my webserver using either the DNS name of www.mousetech.com or the ip address 216.199.14.18. But that's because I pay for a hosting account with my ISP, and a hosting account means specifically, that they permit me to host Internet services. A lot of home accounts, as I said before have legal restrictions against hosting (where available, their hosting products usually cost more).

In many cases, people can take advantage of the fact that the restriction is strictly in the contract and host anyway, although typically you have to use a special DNS service such as DynDNS that can track the server's IP address. That's because one of the things you pay for with a hosting contract is one or more fixed IP addresses. Home accounts usually have DHCP-assigned IP addresses, and the address assigned to your router may change periodically, such as once a week or whenever you power off your router, whichever comes first.

Some ISPs, however, don't just restrict host access in the contract, they restrict it physically. By putting up a firewall between your computer and the Internet that blocks Internet users from accessing your host ports (80 and 443, or whatever). In which case, you either need another contract or another ISP.
 
bhanu chowdary
Ranch Hand
Posts: 256
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks a lot Tim. Thats quite a bit of helpful information.

Can you please elaborate on how can I connect my server(tomcat/weblogic) to the internet?
Tim Holloway wrote:To host a web application, all you need to do is connect a server to the Internet.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic