Re: Out grown sbs2003

Tech-Archive recommends: Fix windows errors by optimizing your registry



BrianMultiLanguage wrote:
Well I do have the SBS set up as:
172.16.x.x to ROUTER.
10.0.0.2 to SWITCH.

So drop 172.16.x.x, remove the nic, change the sbs to gateway to the
router, w/s gateway to the router, and change LAN ips of the router
to match 10.0.0.x

Thank you

Yes, but it's very important that there be a *firewall* between your router
and the switch!!! There's a lot of bad guys out there!

Also, you use CEICW wizard to reconfigure SBS after dropping the second NIC
so that all network pieces are properly updated.


"kj [SBS MVP]" wrote:

BrianMultiLanguage wrote:
I wish all these threads added up to easier reading but here's my
recap.
1. you can have multiple DCs in multiple AD sites in multiple
locations but SBS must be the PDC.
2. there's nothing stopping you from having an additional DC in the
SBS domain.
(BDC) including off site.
3. But you *can* have DC redundancy w/an SBS domain. You can have
multiple DNS servers, multiple WINS servers, use DFS, whatnot.
4. The only thing you can't do is 'break out' stuff like
Exchange/SQL/etc to other boxes. But remember, with Exchange, you
can't have full mailbox replication between servers anyway. That is
a key.
5. I think you could add a standard 2003 server to locations 2 and 3
and make them domain controllers so that logon time would be short
at those locations. SBS will replicate the logon database to
locations 2 and 3 from your SBS server.


You're pretty much on course above.

So I need to figure out how I can have a redundant for
Email (different server of course)

You can purchase additional Exchange Server licenses and upgrade to
SBS2003 R2 where your SBS USER CAL's will cover user access to the
additional Exchange servers. This *may* help your remote users, but
it will certainly multiply your admin complexity. Exchange 2003
doesn't really have any provision for full redundancy. You can build
Clustered servers and get redundant servers, but not redundant
Information stores (where the actual emails are kept). Your best
investment is making the Exchange server as reliable as possible,
doing good backups, and practicing restoration methods so your
prepared for unexpected disruptions.

Internet (how to regateway w/s to an alternate)
vpn/rdp. (how to get in teh network if SBS is down.)

Not using ISA, I'd recommend putting a good hardware firewall /VPN/
appliance in places for Internet access and configuring SBS as a
single NIC. This will help you going forward to the next versions of
SBS or Windows Server 2008 as well. Users access to the Internet is
then no dependant upon the SBS server alone (Still need second DNS &
DC servers though).

??





"Kevin Weilbacher" wrote:

RWW was designed for SBS, you don't get it as designed in a std
W2K3 server environment.

What was the specifics of your downtime? Until you address the
cause and result, simply throwing more hardware will not solve the
problem, but rather triple your potential problems.

Then, as with any other down time scenario, once has to weight the
various cost of redundancy, backups, and equipment with the ROI.

And have you considered that simply throwing more servers into the
mix with "DC redundancy" doesn't mean squat in keeping the
Internet/email up if the problem is with your ISP service? My
Internet at work went down last thursday morning. My ISP was not
aware of a problem til I called them, and they're supposed to be
monitoring this all the time.

--
Kevin Weilbacher [SBS MVP]
"The days pass by so quickly now, the nights are seldom long"
"BrianMultiLanguage" <BrianMultiLanguage@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:2986F91A-E6D4-4866-9A34-2C5B081DB549@xxxxxxxxxxxxxxxx
We have out grown SBS I am afraid.
We are going to need three different locations, and multiple sbs
servers won't do. When our went out, we were dead in the water.
Does RWW work on std Server?
I know'll I have to buy:
Server Std 2003 or ?
ExchangeStd 2003 or ?
What else I am not sure off.
Any one else migrated up?

--
/kj

--
/kj


.



Relevant Pages

  • Re: Why not POP
    ... Also handy to use if you are using an ISP that is not fond of servers being ... More people are going to SBS as a server for their ... I'm not sure I agree with him that Exchange ... >> Are there any major reason why I should not you the POP connector on ...
    (microsoft.public.windows.server.sbs)
  • Re: "Must Have" tools for SBS
    ... ISA - other than a router. ... I have little problems, now and then, with SBS. ... I was troubleshooting an Exchange ... recurring problem with inbound Exchange email; I get a Winsock error ...
    (microsoft.public.windows.server.sbs)
  • Re: "Must Have" tools for SBS
    ... Well, you might be right, but I got the configuration info from an article ... router, dynamic IP, DDNS service from dyndns.org. ... I have little problems, now and then, with SBS. ... However, I was troubleshooting an Exchange problem, the ...
    (microsoft.public.windows.server.sbs)
  • Re: Fehler DHCP beim Assitent =?ISO-8859-15?Q?f=FCr_Internetzu?= =?ISO-8859-15?Q?gan
    ... an einem SBS 2003 ist kein DHCP-Server aktiviert. ... Der DHCP Dienst wird vom Router übernommen, der SBS dient aber als DNS-Server. ... Mittlerweile habe ich aber einen DNS-Eintrag und einen MX-Record für den Server (feste IP am Router) bekommen. ... Auerdem habe ich gerade im Exchange System Manager festgestellt das der Exchange Standartdienst "Microsoft Exchange MTA-Stacks" beendet ist, was eine Fehlermeldung "Schwerwiegender Fehler" ausgelöst hat. ...
    (microsoft.public.de.exchange)
  • Re: "Must Have" tools for SBS
    ... non-profit and my tech budget is low), and have nothing in front of ISA - ... router, dynamic IP, DDNS service from dyndns.org. ... I have little problems, now and then, with SBS. ... However, I was troubleshooting an Exchange problem, the ...
    (microsoft.public.windows.server.sbs)