Re: Wanting to place my hosted web on my server

All I can say is WOW again. You experts on servers are very kind. NOW, That
answer leaves me with a couple more(7 or 8) questions(go figure).

My server, with business ADSL(I guess) came with 5 static IP's.

1.The server stands alone. (couple pc's on that nework)but the server, is
not the ISP. Bellsouth is.
2.The server connects to a modem and there is a Linksys wireless Router
involved.
3.I have logged into the router from here (remote) and opened port 21, when
I set up the FTP. I used the 192.. address on the router page,. FTP works
fine.
4. While reading directions for setting up a web. I created the new
web(create new) from IIS, and it configs automatically on the IIS at port 80,
with all assigned IP's.
5.I logged into the router and set app. web port 80, and assigned my
192....(IS that what you mean forward to the correct IP?)
6.NOW....What do you mean...(.NATed) and what do I look for to make sure
that is taken care of?(Yep, make sure that the router/NAT (and firewall if it
is built in)
> point port 80 to the correct server in your business. ). Welp. I think I did that, doesn't it sound that way??
7.You can test locally: from one machine try to open your 'new' web
> page. Use an IP address, or the server's local name. It shoudl open up
> if the server is configureed correctly.
OK... Not sure.. this should be simple. If I type in the 192...,that says
no.. if I type in one of the 5 static ip's that says no. That tells me I'm
either doing that wrong, or I'm not getting the clue. How do I test locally?
Ya see, I can log into the server, go to the directory, where the web is,
browse the index file and Voila' it works. But, I can't get the web to just
open up, from remote or the pc that is inline(same workgroup.)

OK, I'm NOT doing the local thing right. What did I miss? What should I be
doing to check it locally. Are you saying when logged in and I type the
192...the web should just flop open. or one of the 5 static..63.xx.xx.. Well
I'm a failure. crap.

I know I should get this. I can just tear into a PC, but, this one last
thing is just killin me.

Thanks for listening to this sob story. Feel free to give up, cause someday
I'll figure out what's wrong.

Thanks again

Mark


"PeterD" wrote:

> On Thu, 13 Oct 2005 11:36:16 -0700, "Mark"
> <Mark@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> >Nope, It is a business web site, that very very few, would log into, It is a
> >stand alone server with no games. Just Quickbooks. I want my business website
> >to be on it. It is hosted by another company. I am afraid to have them
>
> Your ISP? Or the inhouse IT people (that's you, right? <g>)
>
> >transfer it to my 192....,
>
> Let's say you are talking your ISP. Your IP with them is what they
> will use. Let's say you have a ADSL line. Your modem connects to them
> (the ISP) through the phone line. The modem probably contains a basic
> router, and this is assigned the IP address for your Internet IP. The
> output of the router is typically NAT'ed to your 192 range. There's a
> firewall in there, too.
>
> >because I am not sure I have done everything
> >needed.
>
> I know what you mean, you're sure something won't work, but don't know
> what! <g> No magic here, take a quiet time and do it.
>
> >Like I said. from IIS I made a new site,
>
> On a local server wiht a 192 IP? That is then going through your NATed
> Router? If yes, then the router/NAT box must forward port 80 to the
> correct IP address--the address of your web server.
>
> >opened port 80, chose all
> >assigned IP's, now is there something else needed, before I have my host
> >point this at my IP?
>
> Yep, make sure that the router/NAT (and firewall if it is built in)
> point port 80 to the correct server in your business. Make sure that
> if that server has a firewall running (such as the one in
> Windows/Windows Server, or a third party software firewall) then also
> open port 80 in that one.
>
> You can test locally: from one machine try to open your 'new' web
> page. Use an IP address, or the server's local name. It shoudl open up
> if the server is configureed correctly.
>
> >Could it be that simple. There will not be more then 1
> >or 2 hits a day. Thats why I see no need for hosting outside. I do not need
> >to reboot. If I do, I'm right there. AM I done????
>
> Probaably not... <g> but sometimes you have to just jump in and find
> the problems. Test the system locally first. If it doesn't work
> locally then it cannot work from outside. <g> (basic logic...) Get the
> local server setup to provide web pages locally first. Then have the
> ISP point things to your IP. Set your router/NAT/firewall to pass port
> 80 to the correct server, adn you should be working.
>
> At least it works well for me. <g>
>
> >
>
.

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: Cost of setting up a network
    ... A router capable of acting as a VPN endpoint for more than one user simultaneously with four Ethernet ports or a switch to suit. ... The rationale for using a server here is basically that the router doesn't need to be able to decide which PC to route the connection to. ... If you are using a router which supports it, you can set up a port-forwarding inbound rule which also _translates_ the port supplied to the receiving port. ... You can use several of these connections to different machines simultaneously. ...
    (uk.comp.homebuilt)
  • Re: Directory Service Event 1311
    ... I checked the router ACL and indeed all traffic from the subnet was ... Once I permitted in the ACL, all port queries worked fine. ... I just wanted a little confirmation, that it was the firewall blocking it, ... Run it from the server that you cannot join ...
    (microsoft.public.windows.server.active_directory)
  • 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)
Loading