 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How can I divide a network in two segments?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/</link>
	<description></description>
	<lastBuildDate>Sun, 19 May 2013 03:14:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: layer9</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40383</link>
		<dc:creator>layer9</dc:creator>
		<pubDate>Mon, 03 Apr 2006 11:40:32 +0000</pubDate>
		<guid isPermaLink="false">#comment-40383</guid>
		<description><![CDATA[No a DMZ does not mean little or no protection. A DMZ is a halfway point between a trusted and untrusted interface. 

A DMZ uses all the same security features as the inside trusted network. Traffic from the DMZ to the inside is blocked by default, and only traffic you allow through will be permitted. A DMZ uses NAT, PAT and ACL&#039;s, just like your external interface. 

BTW, I have to disagree with the previous comments on Linksys. Linksys makes really good SOHO equipment for the cost. And they are only owned by one company. 

That company is Cisco Systems.

Chris Weber
Layer9corp.com
]]></description>
		<content:encoded><![CDATA[<p>No a DMZ does not mean little or no protection. A DMZ is a halfway point between a trusted and untrusted interface. </p>
<p>A DMZ uses all the same security features as the inside trusted network. Traffic from the DMZ to the inside is blocked by default, and only traffic you allow through will be permitted. A DMZ uses NAT, PAT and ACL&#8217;s, just like your external interface. </p>
<p>BTW, I have to disagree with the previous comments on Linksys. Linksys makes really good SOHO equipment for the cost. And they are only owned by one company. </p>
<p>That company is Cisco Systems.</p>
<p>Chris Weber<br />
Layer9corp.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nikjdk</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40384</link>
		<dc:creator>nikjdk</dc:creator>
		<pubDate>Mon, 03 Apr 2006 10:59:32 +0000</pubDate>
		<guid isPermaLink="false">#comment-40384</guid>
		<description><![CDATA[OK, so two networks are possible with two routers.

Router two is connected to the DMZ port on the router connected to the WAN?

I understand that DMZ means less or no protection, but does that mean no NAT and no port filtering?

Regards,]]></description>
		<content:encoded><![CDATA[<p>OK, so two networks are possible with two routers.</p>
<p>Router two is connected to the DMZ port on the router connected to the WAN?</p>
<p>I understand that DMZ means less or no protection, but does that mean no NAT and no port filtering?</p>
<p>Regards,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mortree</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40385</link>
		<dc:creator>mortree</dc:creator>
		<pubDate>Mon, 03 Apr 2006 07:58:25 +0000</pubDate>
		<guid isPermaLink="false">#comment-40385</guid>
		<description><![CDATA[One problem is the Linksys brand. They used to be OK but since they got acquired by various companies....

Well I have your specific router with updated firmare and features still don&#039;t work as advertised after 2.5 years. I suggest that would complicate debugging and configuring. Netgear brand is still cheap but also reliable. And yes whoever you hang off the DMZ will have decreased protection. That is what DMZ generally means and the low end firewalls tend to take that to heart. But a second firewall would fix that. 

Yes I&#039;ve hooked the WAN port of one cheap firewall to another. No problems IF you careful track port forwarding and NAT effect forwards and backwards. Bookkeeping and flow diagrams are everything.


I&#039;d tend to avoid exposing the SBS server to the Internet as a normal port 80 HTTP webserver myself. All the important business stuff is likely on the SBS and all the worse breaches tend to involve webservers.  Forwarded SMTP ports are fairly safe with good AV and SPAM software for Exchange. Unfortuantely that means you don&#039;t get webmail off Exchange if its web port isn&#039;t exposed. Of course I&#039;ve also seen port forwarding, offbeat HTTP ports and mandatory HTTPS used to advantage there as well.

So if you have separate webserver(s) I&#039;d put it on the first firewall DMZ in case it gets infected. That does mean you&#039;d need a switch or hub to connect the second firewall as well to that DMZ port. Those webserver can also be a hunk of junk workstation if it doesn&#039;t get many hits and doesn&#039;t pass out big files. Also depends some on how critical the webserver going down is (hardware reliability).

That was good advice on the gateway SMTP box to forward mail. There is lots of fair quality freeware as well. You can run AV or SPAM protection on it if it has enougn spare horse. But maybe as importantly you can run a simple web page to redirect webserver traffic. 

You could even page redirect HTTP requests to offbeat webserver ports like 81 instead of 80 on two other webservers. But you risk some clients having company proxies that don&#039;t allow offbeat ports. Or that webserver could pull pages from the two companies webservers -- but I suggest that is too complex. 

Offsite hosting still sounds best for one company. If it doesn&#039;t have many pages and doesn&#039;t get too many hits offsite hosting might even be free for a while. Ask your ISP and search the Internet. There are plenty of places wanting to train you to like their hosting while your company grows. They hope eventually you will grow until you must and can pay.]]></description>
		<content:encoded><![CDATA[<p>One problem is the Linksys brand. They used to be OK but since they got acquired by various companies&#8230;.</p>
<p>Well I have your specific router with updated firmare and features still don&#8217;t work as advertised after 2.5 years. I suggest that would complicate debugging and configuring. Netgear brand is still cheap but also reliable. And yes whoever you hang off the DMZ will have decreased protection. That is what DMZ generally means and the low end firewalls tend to take that to heart. But a second firewall would fix that. </p>
<p>Yes I&#8217;ve hooked the WAN port of one cheap firewall to another. No problems IF you careful track port forwarding and NAT effect forwards and backwards. Bookkeeping and flow diagrams are everything.</p>
<p>I&#8217;d tend to avoid exposing the SBS server to the Internet as a normal port 80 HTTP webserver myself. All the important business stuff is likely on the SBS and all the worse breaches tend to involve webservers.  Forwarded SMTP ports are fairly safe with good AV and SPAM software for Exchange. Unfortuantely that means you don&#8217;t get webmail off Exchange if its web port isn&#8217;t exposed. Of course I&#8217;ve also seen port forwarding, offbeat HTTP ports and mandatory HTTPS used to advantage there as well.</p>
<p>So if you have separate webserver(s) I&#8217;d put it on the first firewall DMZ in case it gets infected. That does mean you&#8217;d need a switch or hub to connect the second firewall as well to that DMZ port. Those webserver can also be a hunk of junk workstation if it doesn&#8217;t get many hits and doesn&#8217;t pass out big files. Also depends some on how critical the webserver going down is (hardware reliability).</p>
<p>That was good advice on the gateway SMTP box to forward mail. There is lots of fair quality freeware as well. You can run AV or SPAM protection on it if it has enougn spare horse. But maybe as importantly you can run a simple web page to redirect webserver traffic. </p>
<p>You could even page redirect HTTP requests to offbeat webserver ports like 81 instead of 80 on two other webservers. But you risk some clients having company proxies that don&#8217;t allow offbeat ports. Or that webserver could pull pages from the two companies webservers &#8212; but I suggest that is too complex. </p>
<p>Offsite hosting still sounds best for one company. If it doesn&#8217;t have many pages and doesn&#8217;t get too many hits offsite hosting might even be free for a while. Ask your ISP and search the Internet. There are plenty of places wanting to train you to like their hosting while your company grows. They hope eventually you will grow until you must and can pay.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sonyfreek</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40386</link>
		<dc:creator>sonyfreek</dc:creator>
		<pubDate>Thu, 30 Mar 2006 21:14:13 +0000</pubDate>
		<guid isPermaLink="false">#comment-40386</guid>
		<description><![CDATA[And as far as the webserver goes, you would simply use host headers.  You could have one web server serving out both sites, but when it comes to www.domaina.com for example, it would serve out domaina&#039;s website.  When it asked for www.domainb.com, it would serve out domainb&#039;s website.  I don&#039;t know if the Linksys is smart enough to handle the host headers to send it to different webservers, although I doubt it is.

Here&#039;s a link to help you out on IIS6.0.:
http://technet2.microsoft.com/WindowsServer/en/Library/b5999267-fc46-4430-a6af-e0b483886c8a1033.mspx
Here&#039;s the apache link:
http://httpd.apache.org/docs/2.0/vhosts/examples.html

You could probably also host them on different servers, but you need intelligent hardware to route the requests to the proper server, such as a load balancer.

Wayne


]]></description>
		<content:encoded><![CDATA[<p>And as far as the webserver goes, you would simply use host headers.  You could have one web server serving out both sites, but when it comes to <a href="http://www.domaina.com" rel="nofollow">http://www.domaina.com</a> for example, it would serve out domaina&#8217;s website.  When it asked for <a href="http://www.domainb.com" rel="nofollow">http://www.domainb.com</a>, it would serve out domainb&#8217;s website.  I don&#8217;t know if the Linksys is smart enough to handle the host headers to send it to different webservers, although I doubt it is.</p>
<p>Here&#8217;s a link to help you out on IIS6.0.:<br />
<a href="http://technet2.microsoft.com/WindowsServer/en/Library/b5999267-fc46-4430-a6af-e0b483886c8a1033.mspx" rel="nofollow">http://technet2.microsoft.com/WindowsServer/en/Library/b5999267-fc46-4430-a6af-e0b483886c8a1033.mspx</a><br />
Here&#8217;s the apache link:<br />
<a href="http://httpd.apache.org/docs/2.0/vhosts/examples.html" rel="nofollow">http://httpd.apache.org/docs/2.0/vhosts/examples.html</a></p>
<p>You could probably also host them on different servers, but you need intelligent hardware to route the requests to the proper server, such as a load balancer.</p>
<p>Wayne</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: layer9</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40387</link>
		<dc:creator>layer9</dc:creator>
		<pubDate>Wed, 29 Mar 2006 23:37:19 +0000</pubDate>
		<guid isPermaLink="false">#comment-40387</guid>
		<description><![CDATA[Just by note on the Mail Server if you map your MX records for both companies to the same mail server, then you can both share the mail server. Exchange is perfectly capable of handling multiple mail domains.

Another option would be to use an SMTP mail gateway with 2 mail servers,(a good idea anyway). The gateway would act as a single entry point to your network for SMTP traffic. 

The gateway will hand off mail to both your mail servers.You&#039;d need a server (can install server on an old PC if you want) for the gateway and you need some SMTP gateway software. Symantec makes a good product for small companies. A company your size could purchase the software for around 200 dollars.

Chris Weber
Layer9corp.com]]></description>
		<content:encoded><![CDATA[<p>Just by note on the Mail Server if you map your MX records for both companies to the same mail server, then you can both share the mail server. Exchange is perfectly capable of handling multiple mail domains.</p>
<p>Another option would be to use an SMTP mail gateway with 2 mail servers,(a good idea anyway). The gateway would act as a single entry point to your network for SMTP traffic. </p>
<p>The gateway will hand off mail to both your mail servers.You&#8217;d need a server (can install server on an old PC if you want) for the gateway and you need some SMTP gateway software. Symantec makes a good product for small companies. A company your size could purchase the software for around 200 dollars.</p>
<p>Chris Weber<br />
Layer9corp.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bigshybear</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40388</link>
		<dc:creator>bigshybear</dc:creator>
		<pubDate>Wed, 29 Mar 2006 23:08:31 +0000</pubDate>
		<guid isPermaLink="false">#comment-40388</guid>
		<description><![CDATA[We&#039;ve got a problem here.
With only 1 IP address, you can have only 1 mail server and 1 web server visible from the internet.  So, with 2 companies, one of them can have their mail server local, the other will have to have their mail hosted elsewhere, and only one can have their webserver local, the other has to have someone else host their web site.

Mail needs to come in via &#039;SMTP&#039;, at the firewall you would configure port forwarding for any traffic coming to the firewall on port 25 to be sent to the mail server.  To do a second email server, you need a second IP address.  Same with web traffic, you would port forward port 80 to the web server.  Both of those servers could be the Small Business Server.  

According to the documentation at Linksys the BEFSX41 has one jack that can be configured to be a DMZ port.  I don&#039;t know how restricted they are on traffic through that port to the internet, and to the other network. port.   ]]></description>
		<content:encoded><![CDATA[<p>We&#8217;ve got a problem here.<br />
With only 1 IP address, you can have only 1 mail server and 1 web server visible from the internet.  So, with 2 companies, one of them can have their mail server local, the other will have to have their mail hosted elsewhere, and only one can have their webserver local, the other has to have someone else host their web site.</p>
<p>Mail needs to come in via &#8216;SMTP&#8217;, at the firewall you would configure port forwarding for any traffic coming to the firewall on port 25 to be sent to the mail server.  To do a second email server, you need a second IP address.  Same with web traffic, you would port forward port 80 to the web server.  Both of those servers could be the Small Business Server.  </p>
<p>According to the documentation at Linksys the BEFSX41 has one jack that can be configured to be a DMZ port.  I don&#8217;t know how restricted they are on traffic through that port to the internet, and to the other network. port.   </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nikjdk</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40389</link>
		<dc:creator>nikjdk</dc:creator>
		<pubDate>Wed, 29 Mar 2006 01:14:12 +0000</pubDate>
		<guid isPermaLink="false">#comment-40389</guid>
		<description><![CDATA[It&#039;s ADSL 2 Mbps/512 Kbps. Static webpages.

Yes, I&#039;m no network expert, but I have to improve - or know my limits.

Thanks to all of you for all the advice, I&#039;m truely gratefull.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s ADSL 2 Mbps/512 Kbps. Static webpages.</p>
<p>Yes, I&#8217;m no network expert, but I have to improve &#8211; or know my limits.</p>
<p>Thanks to all of you for all the advice, I&#8217;m truely gratefull.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sonyfreek</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40390</link>
		<dc:creator>sonyfreek</dc:creator>
		<pubDate>Tue, 28 Mar 2006 19:48:17 +0000</pubDate>
		<guid isPermaLink="false">#comment-40390</guid>
		<description><![CDATA[Nikdjk:

Equipment aside, as you&#039;ve had a lot of good advice on what to purchase, what type of DSL line is it; ADSL or SDSL?  What are your up/down speeds if it&#039;s ADSL? 

You mentioned hosting a website and email servers on the connection.  The email server should be fine unless you&#039;re getting a ton of email in, but the webserver could run slow if you have a slow up speed on ADSL.  Considering the sizes of these companies, it&#039;s probably not going to be a problem right now, but if they have considerable growth, an ADSL with 7.1MBps down/768Kbps up won&#039;t cut it if that&#039;s what you have.

Just food for thought.

Wayne]]></description>
		<content:encoded><![CDATA[<p>Nikdjk:</p>
<p>Equipment aside, as you&#8217;ve had a lot of good advice on what to purchase, what type of DSL line is it; ADSL or SDSL?  What are your up/down speeds if it&#8217;s ADSL? </p>
<p>You mentioned hosting a website and email servers on the connection.  The email server should be fine unless you&#8217;re getting a ton of email in, but the webserver could run slow if you have a slow up speed on ADSL.  Considering the sizes of these companies, it&#8217;s probably not going to be a problem right now, but if they have considerable growth, an ADSL with 7.1MBps down/768Kbps up won&#8217;t cut it if that&#8217;s what you have.</p>
<p>Just food for thought.</p>
<p>Wayne</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: layer9</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40391</link>
		<dc:creator>layer9</dc:creator>
		<pubDate>Tue, 28 Mar 2006 18:08:18 +0000</pubDate>
		<guid isPermaLink="false">#comment-40391</guid>
		<description><![CDATA[In answer to your question about the difference between Layer 2 and Layer 3, thats really a book. If you want a good one I&#039;d recommend INTERCONNECTIONS by Radia Perlman, but its a little heady. 

In a very simplistic explanation, Layer 2 is your local connections, LAN connections that is. Now this is not true for Telco services like ATM and Frame, but for your purposes think of it as MAC&#039;s talking.

Layer 3 is your Routable Layer. Thats where your IP&#039;s come in, what you need to get out to the WWW. Your switch can&#039;t tell you how to get there. Only the router can.

As for the VLAN&#039;s, your really getting out of your realm here, since you don&#039;t have a working knowledge of Layer 2 or 3, but suffice it to say you need to route your VLAN&#039;s. You can&#039;t get out of your VLANS without a Layer 3 interface sitting on them. On all of them, in your case thats two. 

So you need to have 2 Linksys routers, or you MIGHT be able to route the DMZ interface on the Linksys router for one of the VLANS, although I can honestly say I&#039;ve never had to try that. 

Best case scenario for your budget is 2 Linksys routers, route the subnets at layer 3, buy a another cheap switch if you need it or use the 4 ports on the back of the Linksys if thats all the hosts you have, and just route the subnets at Layer 3. 

In other words, forget routing VLAN&#039;s, as thats more complicated than you need. If you need to buy another cheep switch at CompUSA.  

Chris Weber
Layer9corp.com]]></description>
		<content:encoded><![CDATA[<p>In answer to your question about the difference between Layer 2 and Layer 3, thats really a book. If you want a good one I&#8217;d recommend INTERCONNECTIONS by Radia Perlman, but its a little heady. </p>
<p>In a very simplistic explanation, Layer 2 is your local connections, LAN connections that is. Now this is not true for Telco services like ATM and Frame, but for your purposes think of it as MAC&#8217;s talking.</p>
<p>Layer 3 is your Routable Layer. Thats where your IP&#8217;s come in, what you need to get out to the WWW. Your switch can&#8217;t tell you how to get there. Only the router can.</p>
<p>As for the VLAN&#8217;s, your really getting out of your realm here, since you don&#8217;t have a working knowledge of Layer 2 or 3, but suffice it to say you need to route your VLAN&#8217;s. You can&#8217;t get out of your VLANS without a Layer 3 interface sitting on them. On all of them, in your case thats two. </p>
<p>So you need to have 2 Linksys routers, or you MIGHT be able to route the DMZ interface on the Linksys router for one of the VLANS, although I can honestly say I&#8217;ve never had to try that. </p>
<p>Best case scenario for your budget is 2 Linksys routers, route the subnets at layer 3, buy a another cheap switch if you need it or use the 4 ports on the back of the Linksys if thats all the hosts you have, and just route the subnets at Layer 3. </p>
<p>In other words, forget routing VLAN&#8217;s, as thats more complicated than you need. If you need to buy another cheep switch at CompUSA.  </p>
<p>Chris Weber<br />
Layer9corp.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nikjdk</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-divide-a-network-in-two-segments/#comment-40392</link>
		<dc:creator>nikjdk</dc:creator>
		<pubDate>Tue, 28 Mar 2006 16:14:05 +0000</pubDate>
		<guid isPermaLink="false">#comment-40392</guid>
		<description><![CDATA[1. Five clients/persons in each company.
2. One fixed ip address.
3. Linksys BEFSX41 router/FW, 3 unmanaged switches, one Dell PowerConnect 2708 layer 2 managed switch (currently not in use) and a MS Small Business Server 2003 Standard edition.
4. The SBS only has to go to one company.
5. The companys need to host their own mail and webservers.

Need more info?

Is the DMZ like an open hole through the router/FW? Can a second router be connected to the DMZ?

Then maybe the SBS can be connected to the DMZ and work as a FW (NAT)?

I&#039;d like to use the Dell PowerConnect, but have no experience with VLANS.

Regards,]]></description>
		<content:encoded><![CDATA[<p>1. Five clients/persons in each company.<br />
2. One fixed ip address.<br />
3. Linksys BEFSX41 router/FW, 3 unmanaged switches, one Dell PowerConnect 2708 layer 2 managed switch (currently not in use) and a MS Small Business Server 2003 Standard edition.<br />
4. The SBS only has to go to one company.<br />
5. The companys need to host their own mail and webservers.</p>
<p>Need more info?</p>
<p>Is the DMZ like an open hole through the router/FW? Can a second router be connected to the DMZ?</p>
<p>Then maybe the SBS can be connected to the DMZ and work as a FW (NAT)?</p>
<p>I&#8217;d like to use the Dell PowerConnect, but have no experience with VLANS.</p>
<p>Regards,</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.013 seconds using memcached
Object Caching 394/397 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-19 15:10:16 -->