Re: Help Me Open Port 81!
- From: pbd22 <dushkin@xxxxxxxxx>
- Date: Sun, 30 Dec 2007 10:15:48 -0800 (PST)
Hi.
Thanks for your reply.
OK, that makes sense. I see why I am getting both .NET and .COM for
the ISP's public IP address.
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.
That is what I thought and tried this and I get "cannot establish
connection".
But, when I try to access this server using its local IP addy
(192.168...), it resolves as expected.
I can also ping the server from anywhere in the local network. I just
can't seem
to get to it from outside using the domain:port convention. This is
why I thought
it may have to do with the fact that SheildsUp! cannot recognize port
81.
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.
I am doing this because the domain2.net server is actually a video
encoder that has a web interface for setup and installation. the .com
server is a web server for hosting my web site. So, I need to
independant
IP addresses on the network for each individual box.
Thanks again for your thoughts.
.
- Follow-Ups:
- Re: Help Me Open Port 81!
- From: Sebastian G.
- Re: Help Me Open Port 81!
- From: Ansgar -59cobalt- Wiechers
- 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
- Re: Help Me Open Port 81!
- From: Ansgar -59cobalt- Wiechers
- Help Me Open Port 81!
- Prev by Date: Re: Filseclab Personal Firewall
- 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
|