tamashii wrote:I was wondering how to get your own server up so i can host my own amvs and not have to pay for a host. I have cable ( broadban, whatever you wanna call it, anyway constant connection as long as my computer is running ). I could leave my computer on almost all day not 24/7 bout 10 a.m to 10 p.m. So if anyone knows how to set up a server please tell me how in detail cuz i tried it once but it was way to confusing. Also how do I know how much bandwith I have???
Well PLeaze reply someone
This really didn't fit in any other forum catagory so I put it here???

A number of problems that you must get around before you even think of using a cable connection for serving data:
- Cable upstream throughout is usually VERY low, unless you have it uncapped by legal (or illegal) means. Maximum theoretical bandwidth for a capped connection is 128 kilobits per second, which means that you can except to see 8-10 kilobytes/second upstream on a good day. (You will, of course, never achieve the full 16, due to shared bandwidth, line conditions, laws of physics, and so on.)
- Most cable ISPs do not assign true static IP addresses to their clients. They usually use DHCP with long lease times, or they configure their DHCP servers to assign IPs based on MAC addresses. Regardless, neither of those situations result in truly static IP addresses.
- Some cable ISPs _do_ give true static IPs, but they assign IPs in private IP address spaces (e.g. 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 are the most prevalent, see RFC 1597 for the authoritative list). These are NOT routable to the rest of the Internet, and therefore cannot be used for external servers. You can, if you have the necessary software, use network address translation on your router to pass traffic on a certain port to an internal address. However, that assumes that (1) your router is capable of such a thing, and...
- ...some cable ISPs have become paranoid, so they do the following: In their customer IP pool, they disallow any TCP connections that have not been previously established. Since server software is responsible for establishing TCP connections, this effectively disallows a lot of server software from operating, even if you meet all of the requirements listed above. Some are less restrictive, and only block certain public service ports from accepting non-previously-established connections (e.g. HTTP port 80, FTP port 21, TELNET port 23, and a few other old-but-for-some-reason-still-in-use services like CHARGEN, DAYTIME, and ECHO). These kinds of blocks are fairly easy to get around.
You'll know if your ISP blocks non-previously-established connections if you (1) meet all the qualifications listed above and (2) people cannot connect.
---
Now, if you CAN serve, you have a number of options. You can use a Web server, as some people have mentioned. You can use FTP servers; for Windows, look up WarFTPD. ProFTPD also works, if you are willing to use Cygwin.