Re: IIS on SBS 2003 behind COX Cable...

From: tcg_gilbert (tcggilbert_at_discussions.microsoft.com)
Date: 03/09/05


Date: Tue, 8 Mar 2005 21:51:01 -0800

That seemed to work! I found a different place to configure it under Server
Management / connect to interenet and also in the mmc called Routing and
Remote Access under IP routing. I could not find the firewall settings under
advanced in the network adapapter properties. THanks a ton for the help.
I'm sitll having issues hitting it from inside my day job companies
network.... but they are behind a proxy and some other things so I think that
is causing the issue.
THanks again!

"Jason Brown [MSFT]" wrote:

> Under 'network connections', get to the network adapter in question, and
> pull up the properties page. Under 'Advanced' there's a section for
> configuring the firewall - what you do next depends on your service pack
> level. running XP SP2 or 2k3 SP1 Release Candidate, you's hit settings, go
> to the exceptions tab and add a new port. on lower pack levels, it's similar
> but slightly less intuitive.
>
> I would assume this being SBS that you're not running an SP1 Beta, so once
> you have your connection properties, under the advanced tab click 'settings'
> and you should get a new dialog with a list of services allowed. Go to Add,
> then fill in
>
> Description: Web on 81
> IP: your IP address or computer name here
> external port: 81
> internal port: 81
> TCP selected.
>
> OK that and you should (once it's enabled) be able to drill through the
> firewall and see port 81 services.
>
>
> --
> Jason Brown
> Microsoft GTSC, IIS
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "tcg_gilbert" <tcggilbert@discussions.microsoft.com> wrote in message
> news:C4C3FA48-6778-4A82-957B-CA540ACDAA48@microsoft.com...
> > Jason,
> > I know I have windows firewall enabled, but dont' have any clue as to
> > where
> > to go to configure it? Thanks so much for the quick reply. Also a good
> > point about checking with cox. I'm not planning on using the server for
> > hosting.... just trying to get familiar with the functionality of SBS 2003
> > and IIS.
> > Thanks again and if you know how to configure the windows firewall please
> > post back.
> > Thanks.
> > Josh
> >
> > "Jason Brown [MSFT]" wrote:
> >
> >> Do you have the windows firewall enabled, with an exception for web
> >> server?
> >> that would allow port 80 but not port 81. just a guess..
> >>
> >> btw, I suspect Cox don't just block port 80 - they may actively frown on
> >> web
> >> servers and may have a clause in their TOS about it. I'd advise checking
> >> with them before facing that web server outwards, lest you get your
> >> service
> >> terminated unexpectedly.
> >>
> >> --
> >> Jason Brown
> >> Microsoft GTSC, IIS
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "tcg_gilbert" <tcggilbert@discussions.microsoft.com> wrote in message
> >> news:5A72BC94-5DDA-47CA-8DA7-2B388E59799A@microsoft.com...
> >> > I'm testing the external website functionality of SBS 2003 for my small
> >> > business. I would like to play with the functionality that SBS 2003
> >> > provides
> >> > in IIS. I have the default website up and running and configured to my
> >> > external LAN Card. I"m pointing the default website to that IP address
> >> > and
> >> > have it configured for port 80. I know that COX blocks port 80,
> >> > however I
> >> > am
> >> > able to to see the website from inside my network (I"m using a netgear
> >> > router). When I switch the website to use port 81 and try to get to my
> >> > website it stops working? I"m using the port forwarding feature of my
> >> > Netgear wireless router. I've also set the port code of my external
> >> > facing
> >> > LAN card to the DMZ. Still does not work. It seems like IIS doesn't
> >> > recognize port 81 as a valid HTTP port?
> >> >
> >> > Here is the short and skinny of my setup:
> >> >
> >> > Using COX cable as my internet provider:
> >> > NetGear Router assigned port forwarding for HTTP requests of ports 80
> >> > to
> >> > 83
> >> > to my external IP: 192.168.0.20
> >> > NetGear Router assigned 192.168.0.20 as DMZ
> >> > In IIS: Set the default web to use 192.168.0.20 with Port 81
> >> > Set the DNS Properties of the server to use 192.168.0.1 (my netgear
> >> > router)
> >> > as a forwarder.
> >> > Using IE6 trying to hit the url http://MYCOXIP:81
> >>
> >>
> >>
>
>
>



Relevant Pages

  • Re: How to Maintain an IIS Server?
    ... > server running on a Windows 2000 server. ... before a firewall and antivirus have been installed]. ... open ports; however, this will not identify which program is using the port. ...
    (microsoft.public.inetserver.iis.security)
  • Re: CEICW fails at firewall config
    ... ISA Server prevents connection to a remote desktop when you connect through ... Remote Web Workplace on a Windows Small Business Server 2003-based computer ... Acceleration Server as a firewall. ... connection uses TCP port 4125. ...
    (microsoft.public.windows.server.sbs)
  • Re: How to Maintain an IIS Server?
    ... >> server running on a Windows 2000 server. ... > before a firewall and antivirus have been installed]. ... > program or executable using that port. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Activesync / Airsync - Alternative Ports
    ... Setup a reverse HTTP proxy. ... Another idea is to use the PPTP capabilities of a Windows Server to allow ... Satellite - Cisco Firewall - Exchange Server ... So on the server side you would configure the port 80 to redirect to ...
    (microsoft.public.pocketpc.activesync)
  • Re: Activesync / Airsync - Alternative Ports
    ... "Chris De Herrera" wrote: ... Another idea is to use the PPTP capabilities of a Windows Server to allow ... Satellite - Cisco Firewall - Exchange Server ... So on the server side you would configure the port 80 to redirect to 8888 ...
    (microsoft.public.pocketpc.activesync)

Loading