Re: Liteweight needs confirmation: SBS config of Mulitple NIC
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Mon, 30 Oct 2006 14:58:38 +1100
Your router is actually acting as a router, rather than a NAT router.
let's use 69.123.123.0/255.255.255.252 (for brevity I'll use /30 as
replacement for 255.255.255.252, 30 bit mask)
four IP's have significance:
69.123.123.0/30 is the network address.
69.123.123.3/30 is the broadcast address.
69.123.123.1&2/30 are usable IP addresses. The router sits on .1 and 'some
other device' sits on .2.
I say 'some other device' because this could be the WatchGuard box, or SBS,
or a simple NAT router.
SO, now I gotta ask about the WG box. Which model? They are very capable
systems. IF it is one of the more advanced WG boxes I'd reinstate it and run
a single NIC SBS. If a lower end unit it is not much more than a 'simple NAT
router' and I'd more likely keep it but also implement a 2NIC SBS. (NOTE:
even the low end WG devices beat most simple NAT routers)
SO, for 'some other device' to talk to the router it must be in the correct
subnet, yours ain't. If the router is .1/30 then whatever you connect to it
should be .2/30 and have .1/30 as the default gateway.
Being a Cisco box, it's also likely quite smart, and may be operating as
both a router and NAT device. You would need to find out what IP it is
NATing from.
I'm again interested in what model of WG box, and in what way you think
'DHCP enabled that was maxed out', even the most simple WG boxes will handle
DHCP for several hundred devices without sweating.
IF it's a low end WG box, reinstate it, learn to use it, in a 2 NIC SBS
scenario (your maxed out DHCP won't matter, not even the SBS itself will be
using DHCP, unless you want it to).
IF it's a more advanced WG box, do your client a favour and find someone who
knows how to run it. They are very capable devices. With anything smarter
than a FireBox III (now superseded) I'd probably run single NIC SBS. (the
current SOHO's can pretty well give a III a good run for the money, I won't
use them as single NIC though)
If the Cisco is ISP supplied I'd probably leave it alone, but it's quite
likely it could act as both router and NAT, possibly even firewall. You
might speak to the ISP about any NAT capability, whether it is enabled, and
if so how you should configure the 'some other device' connected to it.
<bulldog8@xxxxxxxxx> wrote in message
news:1162176839.103539.311760@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The WAN NIC on the SBS server is wrong. It needs to be on the same subnet
as
your Cisco's internal interface. Do you know what that is? From the Cisco
subnet I can see that you have 2 usable public IPs. Did your ISP assign
2?
Claus
Claus -
The ISP set up the router with 2 IP addresses - one for intranet
addressing (69.xx.xx.1, subnet 255.255.255.252) and the other for
internet (69.xx.xx.2, subnet ??)
In case my description was not clear, I have the following addresses
configured:
These 2 items are connected directly via RJ45 cable:
Cisco Router - IP 69.xx.xx.1, subnet 255.255.255.252
SBS NIC2 - IP 192.168.254.1, subnet 255.255.255.252
SBS NIC1 - IP 10.26.13.2, subnet 255.255.255.0
- connected to the intranet switch
Regards,
Jon
.
- Follow-Ups:
- References:
- Liteweight needs confirmation: SBS config of Mulitple NIC
- From: bulldog8
- Re: Liteweight needs confirmation: SBS config of Mulitple NIC
- From: cjobes
- Re: Liteweight needs confirmation: SBS config of Mulitple NIC
- From: bulldog8
- Liteweight needs confirmation: SBS config of Mulitple NIC
- Prev by Date: Re: Event ID 474, but is still working???
- Next by Date: Re: Liteweight needs confirmation: SBS config of Mulitple NIC
- Previous by thread: Re: Liteweight needs confirmation: SBS config of Mulitple NIC
- Next by thread: Re: Liteweight needs confirmation: SBS config of Mulitple NIC
- Index(es):
Relevant Pages
|
