Thread: Just setup a server, now what?
March 17th, 2006, 03:45 AM #1
March 17th, 2006, 03:48 AM #2I miss Dimebag Darrell
March 17th, 2006, 03:54 AM #3
Is IIS actually setup? or did you just install it.
By Default I believe anoymous access is disabled. You may also need to define the root web directory on your machine. This can all be done through the Computer Management/Administration panel (expand services and find IIS).
If you're behind a router/firewall/software firewall you'll have to look into port forwarding/allows inbound access for IIS.
March 17th, 2006, 03:55 AM #4
- Join Date
- Dec 2001
- BrisVegas, Australia
- Blog Entries
Is it serving any pages yet? Also, remember you probably won't be able to connect on your own LAN via the external (internet) IP from behind a NAT firewall (like a router one). You'd need to use the internal LAN IP of the server to see the pages from there.
MickI don't like sigs on forums like this.
March 17th, 2006, 04:07 AM #5
yeah, i got it all set up. when i type in "http://localhost" i get a page similar to this http://distro.ibiblio.org/pub/linux/...ons/damnsmall/. which means the server is running. i'm connected to the net by broadband with router. i already configured the router to port forward to the pc's ip, also configured firewall to accept incoming connections. now how do i know if i can access it from somewhere else?
March 17th, 2006, 09:26 AM #6
- Join Date
- Nov 2005
You dont type in localhost, you type in your IP.
And make an index pageYou know you're in love, when you can scream her name off the top of the mountain, and dont care who hears you
March 17th, 2006, 01:52 PM #7
You might also want to look into a service like http://www.no-ip.com/
You run a small program on your computer that checks your external IP periodically, and then sends that updated information to their server. The net result is that your URL (Http://whatever.no-ip.com) will always be mapped to your IP, even if it changes periodically (dynamic),
Its also easier to remember a URL than it is to remember an IP address IMO.
March 17th, 2006, 07:55 PM #8
well, i tried to access the server today from work and couldn't. maybe i just overlooked something. i'm behind a linksys nr041-wm router. i disabled "Block WAN Request" today for the router, which i didn't do last night, maybe that had something to do with it. also set ms firewall to allow incoming router request and checked ftp server and http server for firewall. is there anything else i might need to disable or allow? also running avast av.
March 17th, 2006, 08:58 PM #9
March 17th, 2006, 09:12 PM #10
March 18th, 2006, 01:54 AM #11
Make sure your server is on a static IP on your local network, make sure port 80 TCP is forwarded to that IP.
If you can access the server from another machine on the local network then your software firewall settings should be good. If the only thing that doesnt work is remote access, then its almost definately something with your router.
March 18th, 2006, 02:04 AM #12
March 18th, 2006, 02:29 AM #13
Technically any port would work.... you might want to avoid popular ports like 20,21,22,25,135-139.... the list goes on. Generally "non-reserved" ports are anything above 10k.
Just switch it to 81 if you want to test that it works.
Then you'd have to connect to your server via
March 18th, 2006, 03:00 AM #14
Remember to open the port you are using on the router/firewall... so it can be accessed from the outside.someone is more skilled than you!
March 18th, 2006, 03:29 AM #15
- Join Date
- Jul 2005
- Austin, tx
more than likely cox is blocking port 80. cox is very inconsistant about what ports it blocks in certain markets versus others, but their TOS does EXPLICITLY forbid you from hosting a web, e mail or ftp server.
now, chances are the only implimentation they provide is port blocking and not protocol blocking, but it is definitely a bum deal that they are doing this kind of junk when there is no real reason to forbid all of their customers from doing it, since they would only have a few problem customers exploiting it (which should be easy to figure out who those ones are when they use 10 times the bandwidth of anyone else on their node).
you may have to resport serving the page on a non-standard port, possibly above a certain number as well.
March 18th, 2006, 04:52 AM #16
It worked on 81, so evidentally its just port blocking.
March 18th, 2006, 08:49 PM #17
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
By petlover3 in forum Applications and Operating SystemsReplies: 3Last Post: March 23rd, 2005, 12:40 PM
By rp in forum Technical SupportReplies: 4Last Post: November 16th, 2004, 11:03 AM
By chad427 in forum Webmastering and ProgrammingReplies: 4Last Post: August 25th, 2004, 12:49 PM
By mingyu01 in forum Networking and InternetReplies: 8Last Post: June 30th, 2004, 11:53 AM
By Bizkitkid2001 in forum Networking and InternetReplies: 11Last Post: May 24th, 2003, 10:44 AM