Re: Wanting to place my hosted web on my server

http://192.168.x.xx:80 does not work from outside or inside the server.
ftp://192.168.x.xx:80 does not work from outside (from my pc)or in the
server.(when logged in)

****Do I need the anonymopus box unchecked in all placesunder web. on IIS or
leave the default username ans PW in. I didn't think I needed any forwarding
stuff done.

I guess I am doing something wrong or do not have it set up right yet. I
hate to give up, I feel I'm so close. I'm sure I am confusing you,. Remember.
One server. I connect remote. Or My son is on that network where the server
is . One pc connected on the same workgroup. I log in via MSTSC and a 63.xx
number.

I think I read that I needed the :80.
"Mark" wrote:

> I sure Thank you is not enough, but Thank you. I'm traveling today so I will
> start again when i get home. I think the part I was missing for the test was
> the :80 or :90 like you said. I only have the one so I will key in on
> George... Thanks so much for your time.
>
> Mark
>
> "Charlie Tame" wrote:
>
> > Quick answer to a couple of points, sorry, not all of them :)
> >
> > Let's guess your router is 192.168.0.1 and your other machines are
> > 192.168.0.10 and 100 respectively. They are name Fred and George.
> >
> > From inside the local network you would likely type in 192.168.0.1 to get to
> > the router setup page. From outside the local network there may be some
> > specific things you have to do so I can;t help there because I don't have
> > one of those Linksys models.
> >
> > Now, if the FTP server is on Fred (10) you should be able to type in
> > ftp://192.168.0.10 or FTP://Fred but from outside the net it will have to be
> > ftp://xxx.xxx.xxx.xxx which is whatever your WAN IP address is. I think from
> > what you said earlier any of the 5 IP addresses your ISP allocated will do
> > that.
> >
> > NAT or network address translation is what the router does when that request
> > for FTP hits it - it looks to see if it has a port allocated for FTP on any
> > of the local machines and if it does it "Translates" the incoming WAN IP to
> > the local network IP. It's really more complex but I think that will do for
> > explanation.
> >
> > Now, if your webserver is on the same machine it will be http:// followed by
> > the same as before from inside or outside the local net, but if it's on
> > George then the local addresses will change to 192.168.0.100 and "George" as
> > above. From outside though the IP will stay just the same, because the
> > router will change the address to the local one which has been stored as the
> > one with port 80 open. This is what port forwarding does.
> >
> > Again this is vastly oversimplified but your ISP is doing roughly the same
> > thing in order to give you 5 IP addresses :)
> >
> > The "Proper" IP port addresses (21 and 80) are assumed by the use of ftp://
> > and http:// but you could run the webserver on a different port - say 90, in
> > which case the address to reach it would be http://xxx.xxx.xxx.xxx:90 and
> > you would then HAVE to type the colon 90 part. So you could run 5 webservers
> > on say xxx.xxx.xxx.xxx:80 (Default) :90, :100 etc if you wanted, or else you
> > could replace the last xxx with your 5 IP addresses and use port 80 for all
> > of them. It is as if the combination of address and port together make a
> > complete address.
> >
> > Obviously these are only examples, not suggestions, and for your purposes I
> > think simply using one IP with FTP webserver and mail might be the sensible
> > option. I would also think all will run on the one machine, but once the
> > domain is directed to your IP the router will sort out what goes to which
> > port on any machine you choose.
> >
> > Anyway have fun, it's late and I don't think I screwed up anything but if I
> > did I don't doubt it will be corrected :)
> >
> > Charlie
> >
> >
> >
> > "Mark" <Mark@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:DE3A90DA-AABF-48BF-81AE-AD5F18249DFA@xxxxxxxxxxxxxxxx
> > > 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: Still cant connect to RWW or OWA remotely
    ... No Phantom NICs as far as I can see. ... that it can not find the server. ... Configure your Router as an Eithernet Bridge. ... Once you have this then configure the Routers Firewall and Port ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... No Phantom NICs as far as I can see. ... that it can not find the server. ... Configure your Router as an Eithernet Bridge. ... Once you have this then configure the Routers Firewall and Port ...
    (microsoft.public.windows.server.sbs)
  • Re: changed IP address: cant receive email & need to make domain name match IP address
    ... Port Forwarding for 2Wire 1701HG ... SBS CDs, but it's always a good idea to keep them handy. ... As you are set up now, your SBS server is "bare to the Internet" (not ... need to buy at least another inexpensive router to put between the SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant connect to Mailserver
    ... domain's zone files on the dyndns server, ... I'm presuming it's a simple port forward from WAN to LAN on ... When I telnet to port 25 I should get a response from your ... Are the correct ports open in the router? ...
    (microsoft.public.windows.server.sbs)
  • Re: Can not access Web and FTP sites from Internet
    ... your IP Configuration on the Server is correctly. ... Connecting To 12.208.215.87...Could not open connection to the host, ... 1> From the result, we can see the telnet failed, which means the router ... does not forward Port 443 to SBS Server. ...
    (microsoft.public.windows.server.sbs)