Hi,

 

How do i avoid typing port number in url. let's say i have www.abc.com i have configured it to on port 1890 because ISP has blocked port 80.

 

my website is accessible only if i use port number at the end of the URL. like www.abc.com:1890

 

help me aovid typing 1890.

 

Thanks,

 

 

Whats it running on?

MMmmm..

 okie..

 1. Bookmark the link www.abc.com:1890
2. Create an hyper link to this www.abc.com:1890  .. so you just need to click on bookmark.
3. write www.abc.com:1890 on a text file and save it on desk top. Each time you have to go to that URL, you can simply copy and paste (so you dont need to type it ;)

lol..

Okie ..now serious..

As an web client, you must type URL with port if you  wanna specify different port than the one  that protocal uses by default (which, in case of http protocal is 80).

  Webserver can make the change to listen to an unused port as default.. not the client.

Jaynir

You are probably trying to host a site from your home using your cable internet. Unfortunately cable providers block port 80 so that people cannot host websites from home. I think you can pay a per month fee for them to enable port 80 for you.

Hosting your site in any other port besides 80 or ssl port 443 require you to put the port number in the URL. If you absolutely have to use another port use port 8080 coz most of the times company firewalls block other ports and your site won't be accessible from outside.

Ans,

so basically you are saying NOOOO...!!

 

ne0, i agree on what you said. but can't use 8080 and 443.

I would be better off paying extra to ISP to have them unblocked port 80. 

Ans,

so basically you are saying NOOOO...!!

 

ne0, i agree on what you said. but can't use 8080 and 443.

I would be better off paying extra to ISP to have them unblocked port 80. 

@jaynir,

It is possible -- you can run web services on any available ports, feed DNS servers with the constantly changing Dynamic IPs to point to the same box, turn your workstation into an SMTP server, and more!  I am planning on spending some time this weekend to put together the steps to accomplish this (at least the port forwarding part). I will either publish a video, or a written manual soon. Stay tuned!!

~@~

You can probably install an apache server on your home system. Then use that to redirect the url of your choice to the url of your site.

is interesting topic. saajha, you have a follower.

using dyndns i was able to convert my pc into a server. I was using windows 2003 but am planing on upgrading to 2008 because of IIS 7. All i had to do was register with dyndns download dyndns update client, redirect incoming traffic from my router to the local host (server).

DynDns provides several customized domain name that you can choose from for free, but to have your own domain register with dyndns they charge around 27$.

The problem i am facing now is, i could only host one web site, i want to see if there is a possiblity to host multiple. AS DynDns provides upto 5 domain for free.

 Saajha, any luck???

Yep, that's one of the main keys - Dynamic DNS.

It allows redirecting traffic to your machine regardless of the IP addresses that your ISP provides you with. So, once you have the web service running on your box, and have your Gateway (Router) configured to allow traffic to say, port 12345; outside users can surf the site. But I believe the original question was about being able to allow users to reach the site without the need of typing in the port number.
Eg.,  www.domain.com instead of www.domain.com:12345

And on that, you are right -- you can pick one of the customized domain names for free, but you're stuck with that name -- or end up paying their charge to do that!  Hmm.. but there's a really neat trick on having your own domain name accept connections going to port 80 -> going to one of those 'customized domain names' -> and being redirected to your domain name and the port other than 80/443. (Hint Hint!! ;) ) All that, without paying the DDNS people for the service.

I know it's no big deal to pay 20 something dollars per year or so. But you feel great when you bypass such obligations and restrictions and figure out something else on our own! You're almost there ..though!!! ;-)

I did spend about 2 hours Saturday morning, putting together the steps - and I chose to do a video demo. I also purchased a domain name for 2 bucks (and some change) to test with, and got it up and running, and verified that I could hit it from outside the network w/o typing in the port #. It's all there, but haven't published it yet -- because I wanted to add some 'cool' noise in the background, and my VISTA machine doesn't support recording from the speakers for some obnoxious reason -- and when I move it over to the XP box, it crashes with a codec error --- turns me nuts!

So, just to have a look -- go to www.securitty.info
I have an Ubuntu machine running apache2 -- you should be able to hit the site ~~ and also get some additional clue on the last part you're exploring! Just a quick note though: All there is, is a flash welcome page. You might need to use IE (as opposed to Firefox) to see it.

BTW, I'll try getting the demo published on the site - hopefully next weekend.

~@~

Well after multiple tries i could finally load your page. I could finally see you. I will work on my 2008 and see what i can come up with.

But will definitely be looking forward to your demo.

and you said around 2 buck for domain. Where did you get that from go-daddy. Is it the same price throught or just a first year.

2 bucks don't hurt especially when you can host your own server and redirect it to xxx.is-a-geek.com
That's what i am thinking of.

 

The domain was leased for a year. I should have used the word 'leased' instead! I got it from ActNowDomains (www.ActNowDomains.com) for $2.19. I think all available .info domains are available to register for that price range.

~@~

OK... so I ended up documenting the steps than continuing with the 'demo'.

So, I leased a domain name from one of the name providers. I knew there were a number of steps to go through before I'd have the homepage running the way I wanted. The first step really was to point the domain name to my network's public IP address, so that the 'outside world' could access the network and the site. Since I did not have a DNS server of my own, I created an account on ZoneEdit (www.zoneedit.com). ZoneEdit provides DNS name resolution service to its members' domain names (I think there's a limit of 5 or so, which was not an issue for this purpose).

OK.. so ZoneEdit would translate the domain name resolution request, and forward the HTTP traffic to my IP address. But I'd still have a problem -- My ISP wouldn't give me a static IP address; meaning, my public IP would not remain the same for too long. As a workaround, I used the free service provided by no-IP (www.no-ip.com) that would let the world identify my web server running machine with a static name- so any changes to the IP would always point to the same host. I believe zoneedit also provides this service for free.

Now, when a user types in www.securitty.info, ZoneEdit does the name resolution and tries to direct traffic to my IP, but my IP is supposed to be dynamic, because of which I just created an account with no-ip to get a permanent hostname service. So, there's a contradiction!!

The goal is to send the traffic over to the no-ip's hostname as opposed to the dynamic IP address. Hmm.. but DNS can only translate domain names to IPs. How can I get around that?

So, what I did was --- used 'Web Forward' feature offered by ZoneEdit.

With that:
User types www.securitty.info
ZoneEdit's DNS gets contacted
Zone Edit's web forward translates the domain name to Eg., www.abc.no-ip.com
Zone Edit's DNS server does a recursive lookup by forwarding the request to No-IP's DNS
No-IP's DNS replies to ZoneEdit's DNS with the correct IP address
ZoneEdit saves it in its local cache (if the IP was not previously cached)
Traffic gets redirected to the IP address suggested by No-IP's DNS
No-IP has an agent that constantly runs on one of the machines in the network and keeps on updating it any IP address changes.

Now, back on my local network:
My ISP doesn't allow me to run web server on port 80
I change the ACL of my router to allow traffic coming to Eg., port 12345
Set Apache to run www on port 12345
Instruct No-IP to forward port 80 traffic to 12345

At this point, from the end user's perspective, it's fully transparent. HTTP request goes to www.securitty.info; reply comes back.
From Zone-Edit's perspective, the request needs to be forwarded to a different domain name, whose IP needs to be fetched, and provided to the user requesting access.
From No-IP's perspective, port 80 traffic going to a given hostname needs to be forwarded to an 'updated' IP address and its port 12345.
From the web server's perspective, a request coming to port 12345 needs to get served. It has no knowledge of the fact that the request is really a redirection of the traffic originally destined to port 80.

That's all....

~@~

P.S. - I may have to add a disclaimer here --- This is solely for educational purposes. Going beyond ISPs' protocols might be against the law. Please do not misuse the knowledge.