Dave Whyte wrote:
> Lanwench,
> Thanks for the replies by the way.
>
> There is those two schools of thought. One says do not have any
> extras on the DC i.e. Exchange, ISA etc. The other is the SBS route.
> I come down on the latter to be honest and there is quite a lively
> SBS support community out there. It has a fan base basically who are
> very loyal to the product. After years of semi-neglect on Microsoft's
> part, they are now fully behind SBS and the people who sell and
> support the product.
I just started getting my feet wet with SBS 2003 Standard after years of
abhoring SBS (very bad experiences with the 4.x version). It's all wizarded
to death, admittedly, but isn't too bad thus far...seems to be good value
for small offices/limited budgets. I still prefer not to rely on its ISA for
network protection, and use an external firewall appliance instead....I'm
fond of Sonicwalls.
I imagine you could use both at once....but I don't see much value in
turning a Windows server into a router, especially when it's your sole
server/DC/Exchange/DNS/file&print/whatnot box. Resource load, security
issues (I prefer to head things off before they get to the server/network at
all). There are so many other, affordable options out there nowadays I don't
see the point unless ISA is on a dedicated box.
Same wariness about running SQL and Exchange on the same server, oy....first
thing I did after installing SBS was to turn off everything I didn't need,
and could turn off...
>
> I am somehow stumped regarding the cable modem log webpage issue. I
> thought about port triggering/forwarding but I am not sure if that is
> the right way to go. I need to very rarely see the CM logs as and
> when there are speed issues with the connectin etc. This needs
> reported to the cable company who run a support newsgroup.
I guess my question there is, why can't the cable company techs get into
their modem themselves from the Internet? I don't see how you're going to
access the modem unless you connect a machine directly to it.
> I suppose I am being a bit belt and braces but once you get a tech
> problem in your head it is hard to shift until you fix it. Who was
> saying the word geek!! LOL :-)
Not me, nosiree. ;-)
>
> Dave
>
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) ahoo.com> wrote in
> message news:%(E-Mail Removed)...
>> Ah, sorry. I don't use ISA (it's not that I don't like it, I just
>> support mostly single-server shops and don't like using my DC as a
> router/firewall -
>> I'd happily run ISA on another server).
>>
>> Dave Whyte wrote:
>>> Because that is what you should do with ISA server and SBS. Remember
>>> ISA is on the SBS box so to service internal and external
>>> networking, you use two nic's one in the private range 192.168.x.x
>>> the other to the cable modem therefore seperating the two networks.
>>>
>>> Dave
>>>
>>>
>>>
>>> "Lanwench [MVP - Exchange]"
>>> <(E-Mail Removed) ahoo.com> wrote in
>>> message news:(E-Mail Removed)...
>>>> I don't think you can unless you connect directly to the cable
>>>> modem. What do you need to change? Your ISP may be able to do it
>>>> for you.
>>>>
>>>> May I ask why you have two NICs if you're using a router?
>>>>
>>>> Dave Whyte wrote:
>>>>> Hi all,
>>>>>
>>>>> I have an SBS2003 installation with a soho nat router in between
>>>>> ISA Server and my cable modem.
>>>>> SBS (with two nic's) - Nat Router - Cable Modem
>>>>>
>>>>> Question is, how do I connect to the cable modem config web page
>>>>> that sits beyond the nat router?
>>>>>
>>>>> Thanks for any help
>>>>>
>>>>> Dave
|