Re: sbs 2008 - no Internet access possible to 2nd server
- From: "Cliff Galiher" <cgaliher@xxxxxxxxx>
- Date: Sun, 4 Jan 2009 10:59:18 -0700
First, you really want a good firewall device at your network's edge. If you are a big enough business to use SBS then that means you have outgrown the "home office" of the SOHO acronym and, as such, should be treating your network with just as much security as you would a cash register with money in it. Almost all business class gateways (cable or DSL) can be configured as in a 'bridge' mode which means the firewall will handle all of the IP-level traffic, and almost all business-class firewalls can handle multiple IP's in a drop-in NAT configuration.
Whether the Thomson does or not I couldn't really tell you. I haven't tried to configure one of those as just a bridge. But if it was provided to you by your ISP when you got your account (I assume you got a business class account since you are running VoIP as well) then it likely will work. You just need to hook up a good firewall that can handle the NAT services (as well as provide other security services.) Which, BTW, you should have even if you *don't* decide to go the multi-IP route.
Hope that helps,
-Cliff
"Eric Visser" <evisser@xxxxxxxxxxx> wrote in message news:36B5A051-D949-4A83-AF02-E633786B5D1D@xxxxxxxxxxxxxxxx
Seems like a practical solution... however I am not sure that the router in my SOHO setup allows multiple IP@ on the WAN side..
I just checked my modem/router GUI and does not seem to provide this function.
This is new for me, is this a standard function for a routers or do you need specific (professional) routers?
I use the Thomson 780 for data and phone.
-Eric
"Cliff Galiher" <cgaliher@xxxxxxxxx> wrote in message news:euuS34cbJHA.1916@xxxxxxxxxxxxxxxxxxxxxxxThe simplest solution is to request two IP's from your ISP. Then you set up the router to forward traffic from IP #1 to SBS and IP #2 to server #2. Create an A record for the second server and, voila, you've got immediate access. This is the best setup for many reasons. No munging with scanning headers, no trickery with HTTP redirects, and non-HTTP traffic can be supported if needed for future growth. It is also immensely more easy to maintain because you don't have to 'remember' (or document) any bizarre ad-hoc configurations you may have made to get an alternative solution to work.
As long as you are paying for a business-class connection from your ISP, adding a second IP is usually a minimal cost.
-Cliff
"RickV" <RickV@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B3F4C95C-5803-46BE-B647-32EE49790274@xxxxxxxxxxxxxxxxHi,
SBS 2008 set up as two virtual servers with Hyper-V.
Server1 has SBS 2008 and server2 WS2008 with application server roles and SQL.
Router forwards Internet traffic to server1.
Q: How do I reach a web application on server2?
I tried everything - web application on server1 that redirects to server2,
no luck.
I made a small test application on server1 with a hyperlink to server2.
I can access my test application from the Internet without problems. When I
click the hyperlink, nothing.
For internal users there is no problem. OWA and mobile device access
communicate fine over the Internet. For this reason I routed all traffic to
server1.
Any advice is appreciated. -Eric
- References:
- sbs 2008 - no Internet access possible to 2nd server
- From: RickV
- Re: sbs 2008 - no Internet access possible to 2nd server
- From: Cliff Galiher
- Re: sbs 2008 - no Internet access possible to 2nd server
- From: Eric Visser
- sbs 2008 - no Internet access possible to 2nd server
- Prev by Date: Re: Terminal Server - alternatives
- Next by Date: Re: Migrating sbs 2003 to sbs 2008
- Previous by thread: Re: sbs 2008 - no Internet access possible to 2nd server
- Next by thread: RE: sbs 2008 - no Internet access possible to 2nd server
- Index(es):
Relevant Pages
|