• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How to best arrange network for new internet media server home computer?

legocitytruck

Senior member
I’m building a new computer that will be used as an HTPC, and a media server providing documents to me through the internet while I’m at work.

To avoid IP conflicts with my ISP, is it possible/beneficial, to utilize a dual NIC motherboard where one NIC is connected directly to the modem and the other is connected to a router that connects multiple computers/ printers through the main computer to the internet? Will this create any sort of data bottlenecks?

Is there a more efficient way to connect these computers so that all have internet access and the new machine is easily accessible through the internet?
 
No. The router "handles" the ip conflict (IE there is none expect in very special cases that I doubt cover you). Most windows machine really don't know how to operate properly on a multihomed network and can take some command line configuration to get operating correctly. Just attach it to the same switch with the other devices and leave the second port alone.

Without knowing how you have the media PC configured, it is incredibly dangerous to leave a windows machine (of the home os variety) directly on the internet. Even servers should be filtered. I would expect your machine to be "pwned" pretty quickly sitting there naked.
 
Last edited:
Modem > WAN port on router and all the PCs/printers/etc to the LAN ports on the router. That's the easiest, safest and simplest way of doing it.
 
Quote: "To avoid IP conflicts with my ISP".

What exactly you think can happen?

Thanks for your help everyone, it's clear I was headed in the wrong direction.

JackMDS - I believe there are issues with your ISP if you have data forwarded to an ftp machine on your home network though a router. Currently, I'm haven't had success getting this to work using FileZilla on my laptop as a trial. I thought maybe having a dual NIC motherboard would allow you to circumvent this issue.
 
The OP might be referring to ISP port-specific service blocks. Some ISPs will block incoming traffic to those ports to prevent customers from running mail/web/ftp servers, etc.

If that is the case, I'm not sure circumventing those blocks is something that should be encouraged.
 
Thanks for your help everyone, it's clear I was headed in the wrong direction.

JackMDS - I believe there are issues with your ISP if you have data forwarded to an ftp machine on your home network though a router. Currently, I'm haven't had success getting this to work using FileZilla on my laptop as a trial. I thought maybe having a dual NIC motherboard would allow you to circumvent this issue.

Some ISPs block the common ftp ports but it has nothing to do with a Router.

If it is blocked it is blocked, the Router is under your control not the ISP's control.
 
Thanks for your help everyone, it's clear I was headed in the wrong direction.

JackMDS - I believe there are issues with your ISP if you have data forwarded to an ftp machine on your home network though a router. Currently, I'm haven't had success getting this to work using FileZilla on my laptop as a trial. I thought maybe having a dual NIC motherboard would allow you to circumvent this issue.

Also FTP is a "pita" to get working properly. There is some special configs you need to enter in to the FTP daemon to make it work behind a firewall.
 
Also FTP is a "pita" to get working properly. There is some special configs you need to enter in to the FTP daemon to make it work behind a firewall.

A colleague of mine has a NAS at his home that he is able to log into from his work computer and retrieve files. How does this work? Is it possible to set up the computer to operate in the same way? Does it require purchasing a domain name?
 
A colleague of mine has a NAS at his home that he is able to log into from his work computer and retrieve files. How does this work? Is it possible to set up the computer to operate in the same way? Does it require purchasing a domain name?

Not a direct answer but the principle cabn be inferred.

Home Server IP on the Internet: http://www.ezlan.net/myip.html

Setting VNC: : http://www.ezlan.net/vnc.html

P.S. There something wrong with the time it takes to load the pages be patient.


😎
 
A colleague of mine has a NAS at his home that he is able to log into from his work computer and retrieve files. How does this work? Is it possible to set up the computer to operate in the same way? Does it require purchasing a domain name?

FTP is not the most "nat aware" protocol. Typically you configure the daemon to look up the outside internet address (via domain name / static / myip whatever) then configure a range of ports for the control session and data sessions, tell that range to the daemon etc. once you have all the port forwards and the FTP daemon configured it will start working like it is supposed to.
 
"TO THE CLOUD!"

Seriously, that's probably the best option for you. I don't know exactly what type of files you need to retrieve, but if FTP is blocked you'll either need a port workaround (which is probably against your ISP's TOS) or off-site data storage. Plenty of 3rd party options out there, but may make a difference depending on what you actually need.
 
You can use a service such as TeamViewer, this will work over Port 80 with SSL and has a built in FTP server. just a suggestion..
 
Google "FTP nat". There are very specific things you need to do on the ftp server, the router and the client to get it to work properly. As mentioned FTP is not NAT friendly at all.
 
Or use an active FTP connection and you can get by with just port 21 forwarded.

FTP uses 2 ports in both active and passive. Also FTP active mode is (sometimes) NAT incompatible because the server generates the connection, and the NAT device may not allow it to pass. This was the main reason passive was developed.
 
I have never had any trouble using FTP in active mode either when I or the server is behind a NAT. Additionally, I have not had trouble using it in active mode when only port 21 is open.

The only time I have needed to forward more than one port is to accomodate passive mode.
 
How i set mine up is with a router connected to a gigabit switch. ALL other devices go through the switch. In this way the router is relieved of all switching duties. I feel it has reduced router restarts.
 
Back
Top