Gaming Trying to build a home server

[Frederica Bernkastel]

Another method of streaming is through the DLNA UPnP protocol, for which you can use a server such as TwonkyMedia.

EDIT: I should point out that TwonkyMedia has a built-in webserver, which meets the "simple webpage" need.

 

[Rydian]

Ok, did that, now I need to forward the ports 22 and 80. But I have no idea how and portforward.com is not very helpful.

Just tell it you're forwarding for apache, it'll tell you ports 80 and 443, just use 22 and 80 instead when you put the info in.

 

[Frederica Bernkastel]

Why do you think he shouldn't port-forward for HTTPS?
and more importantly, why expose an unsecured sshd to the internet?

EDIT: The default TwonkyMedia port is 9000, so you'll want to port-forward that - but you can forward a different external port to 9000 if you want to secure it a little. Another webserver is unnecessary if you're only going to be streaming media (also, poor choice of webserver at that - apache is pretty bad from not only a resource usage standpoint, but also from a security standpoint.)

 

[Rydian]

Why do you think he shouldn't port-forward for HTTPS?If he's not using it there's no sense in opening the port.

QUOTE(Antoligy @ Mar 13 2011, 07:15 AM) and more importantly, why expose an unsecured sshd to the internet?

Isn't that what he's been trying to do from the beginning, make it accessible from outside his home? :\ I don't see why you wait until now to say it's a bad idea.

 

[Frederica Bernkastel]

Why do you think he shouldn't port-forward for HTTPS?If he's not using it there's no sense in opening the port.
QUOTE(Antoligy @ Mar 13 2011, 07:15 AM) and more importantly, why expose an unsecured sshd to the internet?

Isn't that what he's been trying to do from the beginning, make it accessible from outside his home? :\ I don't see why you wait until now to say it's a bad idea.

Nice contradiction there, he never expressively said that he would need to SSH in from the outside, yet for some reason there is the belief that he should forward that.



EDIT: SSH isn't as you probably might think a file-transfer protocol. It's a protocol for remote text based administration/usage of servers, and as such is a potential vulnerability on improperly (or un)secured servers. If a server can be controlled locally, there should be no need to expose the SSHd to the outside. Especially when the sysadmin has no prior experience with linux security.

SFTP is also less secure than FTPS, which is something I'd strongly recommend using. Although for filesharing over a local network, there really is nothing better than SAMBA.

Also, I'd recommend using GLFTPD or Pure-FTPd.

 

[olleb]

sorry, did not read the whole thread (don't have time right now) and i do not know whats answared/asked or not but i'll give you some easy linux server solutions.

File server: use a ftp server of your choice, you can access it from ftp clients, webbrowers and from computers trough the standard filebrowser window if you type ftp://your servers domain name or ip. i recomend ftp clients because they are made to access ftpservers.

Web server: use LAMPP it's an easy webserver all in one package. (following is from wikipedia "LAMP is an acronym for a solution stack of free, open source software, originally coined from the first letters of Linux (operating system), Apache HTTP Server, MySQL (database software) and Perl/PHP/Python, principal components to build a viable general purpose web server."


connect to your server:
connect to the terminal: from linux or mac, use an ssh client via terminal, from windows use putty. use openssh as a ssh server.
remote desktop. use any vnc server and a vnc client. an easy way of doing it, use teamviewer. i like tight vnc too.


IRC server: use unrealircd, it's not plug and play, you have to configure it yourself, but it works!^^

READ ABOUT myihome! think it's what you are searching for.
http://www.networkedmediatank.com/download/myihome.html
more to come, maybe

 

[Rydian]

Nice contradiction there, he never expressively said that he would need to SSH in from the outside, yet for some reason there is the belief that he should forward that.

He states in the first post he wants his server to be accessible from any computer with an internet connection. If SSHing from the outside was the bad point then I'd think you would have said so before I posted.

If you all want to walk him through setting up something that's more secure that's fine by me, if I was giving actual advice on the route I think he should take I wouldn't have him open his computer/network at all, rather just set up a file host somewhere... but everybody's got their own ideas on what he should be doing/using and since this is a small-scale thing and a learning experience for him I figure I'd just mostly stand back and toss in some advice when I can on whatever step he seems to be hung on that I know of.

 

[Pyrmon]

Well, I have set up a media server using Amahi for now and it does part of what I want. For the web site I'll look into that later. Thanks for your answers!

 

[Rydian]

For the website you only need to forward port 80, unless you intend to be able to add files to it from outside (which is partially what antoligy's latest post was aimed at).

 

[Pyrmon]

For the website you only need to forward port 80, unless you intend to be able to add files to it from outside (which is partially what antoligy's latest post was aimed at).

Yeah I know I have to do that. And I don't want to add files to it from outside yet.

 

[Dr.Aqua]

Eh Too bad Microsoft pulled drive extender

 

[Urza]

Eh Too bad Microsoft pulled drive extender

It is a shame.

That was the only legitimate reason I could see for using WHS.

 

[Dr.Aqua]

Eh Too bad Microsoft pulled drive extender

It is a shame.

That was the only legitimate reason I could see for using WHS.

ikr
I was even considering a whs server until Microsoft shitted everyone