| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 31618 | 2003-03-27 08:58:00 | Network Setup Query | Erin Salmon (626) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 131362 | 2003-03-27 08:58:00 | Hi all, I've got a little home network to set up in the near future. Here's the picture... There is a wireless broadband connection supplied via an antenna and "e-box". The ebox connects to the network via 10Mbps ethernet link. We had a static IP address. There is a server on the network which I've setup running NT Server 4.0 to host ASP pages. This needs to be visible for ASP and FTP by the rest of the world. Am I right in thinking that the ebox will be visible to the www with the static IP address assigned to us? If this is the case, how do people on the www see the server? I'm keen (for the purpose of extending my understanding) to get the server to do as many things as possible. I'm anticpating using it as a DHCP server, Webserver, FTP Server, Terminal Server and anything else interesting I can run on it. There strike me as thus being two ways of setting up the network. One, all nodes, ebox included, are connected through a central switch. Two, the ebox connects to the server via network card one in the server. All hosts (including network card two on the server) connect to a central hub, which gets net access via the server, which operates two independent networks via two independent network cards. In real-world terms, the only advantage to the latter is that it means less cabling, given the layout of our house. Any thoughts? My main concern at this point is that by burying the server within the network, it doesn't have an IP address for the internet, and thus can't serve pages. Is this true? How do I get around it? Cheers, Erin |
Erin Salmon (626) | ||
| 131363 | 2003-03-27 09:19:00 | so long as you can port forward on every jump between the net and your webserver, you should be ok: http://overclockersnz.no-ip.org:81 to get to that you are going through the no-ip service which tells you the ip of the account "overclockersnz" (which is my current ip), from there you hit my dsl router which has the port 81 forwarded to my smoothwall (http://www.smoothwall.org) box, which in turn forwards port 81 requests to my DMZ (demilitiarised zone), where my Direct Connect Hub sits, i have apache running on the direct connect hub and its listening on port81. your request goes through all of that and badabing you get a response :) |
whetu (237) | ||
| 131364 | 2003-03-27 09:21:00 | i forgot to add that that applies for basically anything.. obviously i have the ports required for Direct Connect pointing to the server, as well as a couple of other handy services... | whetu (237) | ||
| 131365 | 2003-03-27 09:24:00 | Ahh yes... Port forwarding. I'm sure I've been told about that before. Just a matter of setting it up. As for the network topology, the former is easier to set up, but it's less creative (yes, that's a disadvantage where I come from), and the latter means about 50m less network cable, so easily displaces the cost of a network card. I'm going to be back with a big load of questions about how to get the server seen outside my network, but to quell my queries, does anyone know of a useful resource on this operation? Many thanks, Erin |
Erin Salmon (626) | ||
| 1 | |||||