Re: Help Me Open Port 81!
- From: Ansgar -59cobalt- Wiechers <usenet-2007@xxxxxxxxxxxxxxxx>
- Date: Sun, 30 Dec 2007 17:48:09 +0100 (CET)
pbd22 <dushkin@xxxxxxxxx> wrote:
On Dec 30, 4:56 am, "Sebastian G." <se...@xxxxxxxxx> wrote:
pbd22 wrote:
But SheildsUp tells me that I have all my ports as stealth
(including 80) and tells me that 80 is closed.
So what?
I am guessing the fact that sheilds up is telling me is closed is
the problem
Why is this a problem?
but I can't seem to figure out how to open it.
Well, how do you know that the forwarding doesn't work? So far you
have presented nothing that would indicate so.
Well, your response was about as useful as, it seems, my question. If
I am missing information that could help you (politely) troubleshoot
my problem, it would be useful to know "what" that information is.
Update -
When I designate domain1.com as port 80 and
when I designate domain2.net as port 81
I get the domain1.com web site when I type in
either domain1.com and domain2.net.
When I designate domain2.net as port 80, both
the .net and .com requests forward to domain2.net.
Any suggestions as to what I am doing or what additional
information I should be providing?
I'll go out on a limb and assume the following:
- Your router is assigned a public IP address by your provider.
- Both domain1.com and domain2.net resolve to the public address
assigned to your router.
- Somewhere behind your router are two servers with private IP addresses
(192.168.0.5 and 192.168.0.6).
- Both servers run a web server instance, one hosting domain1.com, the
other hosting domain2.net.
- The servers are not running any kind of personal firewall.
- Your router is configured to forward port 80/tcp to 192.168.0.5:80 and
port 81/tcp to 192.168.0.6:80.
Correct?
In that case, when a user directs his browser at either domain1.com or
domain2.net the names are resolved to the external IP address of your
router, the browser connects to that address port 80/tcp (the default
port for HTTP), the router forwards the connection to 192.168.0.5:80,
which host only domain1.com, but not domain2.net. Thus the latter
requests will fail.
If you want to keep that setup, you need to point your browser towards
domain2.net:81 to be able to access domain2.net hosted by 192.168.0.6.
However, why are you using two servers in the first place? One web
server can easily host multiple domains, so you'd just need to forward
port 80/tcp to a single server and it will serve requests for either
domain.
And please use RFC 2606 domain names in your examples next time. That's
what they're reserved for in the first place.
cu
59cobalt
--
"If a software developer ever believes a rootkit is a necessary part of
their architecture they should go back and re-architect their solution."
--Mark Russinovich
.
- Follow-Ups:
- Re: Help Me Open Port 81!
- From: pbd22
- Re: Help Me Open Port 81!
- References:
- Help Me Open Port 81!
- From: pbd22
- Re: Help Me Open Port 81!
- From: Sebastian G.
- Re: Help Me Open Port 81!
- From: pbd22
- Help Me Open Port 81!
- Prev by Date: Re: Help Me Open Port 81!
- Next by Date: Re: Filseclab Personal Firewall
- Previous by thread: Re: Help Me Open Port 81!
- Next by thread: Re: Help Me Open Port 81!
- Index(es):
Relevant Pages
|
|