Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
This may be hard to explain, but I'll do the best that I can.
In general, I have a machine, behind a Linksys router, that has a small series of port that are opened to allow them to be open to the outside internet, for server reasons... (Http on 80, VNC on 5800 and 5900 respectively, and a few other random ports open for uTorrent, etc...) In specific, I would like to perhaps host a webpage on port 80, in some subfolder, or whatever, that would map to a different port, and make it look completely transparent to the outside world.
So for example, blah.com:80 is my website...
And blah.com:64444 is my uTorrent web adminstration site.
I would like be able to go to blah.com/torrent, and have it 'redirect' to the port 64444, but without the outside world knowing it.
The reason for this is on a few terminals at work, I can not only access port 80 on servers. IF I try, blah.com:WHATEVER PORT OTHER THAN 80, It will not work.
I have tried a few simple things, but with no solution yet.
First, I made a page redirect. <Meta> redirect, but again, the actual HTML just tells the terminals browser to instead bring up blah.com:64444...
Second, I made a virtual directory, and tried a redirect in the IIS server properties. Again. Same thing. I believe when you access the virtual directory, it specifies to the terminal's browser to redirect, and specifally pull up blah.com:64444 (what is listed in the IIS options for the virtual directory as the redirect URL).
I hope that all makes sense, and I will certainly be watching for replies, and so if you have more questions to further identify my requirements, then that's all great.
I believe I'm looking for a program that will accept an URL, on port 80 (the only port the terminal can speak out on...), redirect that to port 64444, have the server process the data, and request, blah blah, and then change the 64444 port number, BACK to port 80 (the only port the terminal can talk out on, and apparently receive data back on)...
Or maybe, my Linksys can do that for me. See incoming port 80 data, change the port number to port 64444, send it to the 64444 port on my server, process and retransmit the results, router again sees port 64444 traffic, and converts it to port 80 traffic...
Problem with the router doing it, all incoming 80 traffic would be redirected, and not just the virtual directory's traffic.
Thanks in advance to all the great people out here!

I don't unfortunately think that does help. I appreciate your response, and what it does, is give more detail of what I already am able to do.
What I need to attempt to do, is make a website appear to run on port 80, to the remote machine accessing that website.
I hope something exists to help me with this problem!
Brian

As far as I know, it's a redirect of sorts. I don't know what else can be done unless dyndns.org can do it for you.

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |