Prev: Wedding Planning Sites - NOT unethical
Next: Juniper ssg-140 web filtering
From: jdrott1 on 15 Apr 2008 19:17
i have a Firebox® X Edge E-Series router i just installed. i have no
problems getting out to the internet after setting up the box. i
can't seem to figure out the incoming connections for rdp and http.
i've opened port 80 and directed the traffic to my webserver (vista
business iis 7.0) and port 3389. the browser says my webpage can not
be found. anything i missed?

From: Leythos on 15 Apr 2008 22:36
In article <194adef2-9172-4fd7-9a0b-
6d0d0a935ddd(a)m44g2000hsc.googlegroups.com>, jonathandrott(a)gmail.com
says...
> i have a Firebox® X Edge E-Series router i just installed. i have no
> problems getting out to the internet after setting up the box. i
> can't seem to figure out the incoming connections for rdp and http.
> i've opened port 80 and directed the traffic to my webserver (vista
> business iis 7.0) and port 3389. the browser says my webpage can not
> be found. anything i missed?

What firewall rules did you create to map external to internal?

Are you using the browser inside the network to try and connect to your
PUBLIC DNS name for the server?

Can you connect to the IIS from inside the lan?

Did you change the firewall on your VISTA WORKSTATION - as Vista is NOT
A SERVER by any means.

--
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free(a)rrohio.com (remove 999 for proper email address)
From: daveh551 on 16 Apr 2008 11:47
On Apr 15, 6:17 pm, jdrott1 <jonathandr...(a)gmail.com> wrote:
> i have a Firebox® X Edge E-Series router i just installed. i have no
> problems getting out to the internet after setting up the box. i
> can't seem to figure out the incoming connections for rdp and http.
> i've opened port 80 and directed the traffic to my webserver (vista
> business iis 7.0) and port 3389. the browser says my webpage can not
> be found. anything i missed?

One thing that may or may not be applicable: I just went through a
similar situation where I was trying to set up my home router to pass
incoming traffic to test out a website I was writing. After spending
several days trying different router rules, I finally called Verizon
Tech Support (I have FiOS, and they supplied the router, though they
don't manufacture it). After dancing around with several tech support
people who didn't want to be helpful, one of them made the comment,
"Oh, we block incoming traffic on port 80. You have to have a business
account for that."
From: Sebastian G. on 16 Apr 2008 13:05
daveh551 wrote:


> "Oh, we block incoming traffic on port 80. You have to have a business
> account for that."


I hope you took the consequence and left them.
From: daveh551 on 16 Apr 2008 14:23
On Apr 16, 12:05 pm, "Sebastian G." <se...(a)seppig.de> wrote:
> daveh551 wrote:
> > "Oh, we block incoming traffic on port 80. You have to have a business
> > account for that."
>
> I hope you took the consequence and left them.

I wish! Unfortunately, at my house, they're the only game in town.
For testing purposes, I accessed the server with an alternate port
number.
 |  Next  |  Last
Pages: 1 2
Prev: Wedding Planning Sites - NOT unethical
Next: Juniper ssg-140 web filtering