two subnets on one nic

hi,
I have one existing subnet scope 192.168.100.0/24 configured on DHCP on
SBS2003 in domain. I want to add 4 computers on subnet scope
192.168.101.x/24 which will not be in domain, they will exist in workgroup.
server address is 192.168.100.100, and router 192.169.100.1.
what I have to do in RRAS so that computers in workgroup can access
internet?

thanks

There is no relationship between IP#s and Domains.
You can have a million Domains on one IP Segment.
You can have a million IP Segments with one Domain.

Just have all of the machines on the same IP Segment and forget it.

The only reason to add a new segment is when you get more than 250
hosts,...then you buy a LAN Router and branch a new segment off of it. If a
company has that many hosts,..then the have the money for a LAN router.


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------



"Tomo" <zastita@spama.od> wrote in message
news:h98hd8$vlb$1@localhost.localdomain...
> hi,
> I have one existing subnet scope 192.168.100.0/24 configured on DHCP on
> SBS2003 in domain. I want to add 4 computers on subnet scope
> 192.168.101.x/24 which will not be in domain, they will exist in
> workgroup.
> server address is 192.168.100.100, and router 192.169.100.1.
> what I have to do in RRAS so that computers in workgroup can access
> internet?
>
> thanks

> The only reason to add a new segment is when you get more than 250
> hosts,...then you buy a LAN Router and branch a new segment off of it.

No, that's one of MANY reasons to consider using a subnet, but it's
certainly not the only one.

> I have one existing subnet scope 192.168.100.0/24 configured on DHCP on
> SBS2003 in domain. I want to add 4 computers on subnet scope
> 192.168.101.x/24 which will not be in domain, they will exist in
> workgroup.
> server address is 192.168.100.100, and router 192.169.100.1.
> what I have to do in RRAS so that computers in workgroup can access
> internet?

There are plenty of good reasons to use subnets, segrating traffic is one.

You need to better explain how you're currently connected to the internet.
Is it through a router? What make/model? How will the segrated hosts be
physically connected? To the router, or through a PC server? SBS
complicates things a bit as it does have limits on what can or can't be
configured. Trying to mix a domain controller with dual network interfaces
is never simple.

-Bill Kearney

"Bill Kearney" <wkearney99@hotmail.com> wrote in message
news:9tCdnSCDvd42iyfXnZ2dnUVZ_o2dnZ2d@speakeasy.net...
>
>> The only reason to add a new segment is when you get more than 250
>> hosts,...then you buy a LAN Router and branch a new segment off of it.
>
> No, that's one of MANY reasons to consider using a subnet, but it's
> certainly not the only one.

It's the primary reason,...traffic separation at L3 and L4 is the 2nd most
reason,...neither of which really apply here that I can see.
I'm not trying to be "exhaustive" and write a huge document on why someone
might want a new subnet. I know all the reasons why they might exist. My
post is "close enough" for this thread. Adding 4 Pcs that are members of a
different domain?,....no that is not a decent reason for creating a subnet.

The 4 PCs probably don't even justify having a new Domain either for that
matter. That is even more so with this being an SBS situation,...the last
"useful" thing a person needs in an SBS environment is another domain.

I always prefer to prevent a bad network environment from being created in
the first place when I sense a person going in that direction,...rather then
just let them do it, then deal with the grief of solving the problems they
created for themselves by doing it the way they did it. So I try to talk
them out of the bad design before they do it.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Bill Kearney wrote:
> There are plenty of good reasons to use subnets, segrating traffic is one.
>
> You need to better explain how you're currently connected to the
> internet. Is it through a router? What make/model? How will the
> segrated hosts be physically connected? To the router, or through a PC
> server? SBS complicates things a bit as it does have limits on what can
> or can't be configured. Trying to mix a domain controller with dual
> network interfaces is never simple.
>
> -Bill Kearney
>

there are sbs2003 as DC, DNS and DHCP server and server standard 2003
with isa 2006 in domain
isa is connected to adsl router
all clients are on same switch
i think it would be less complicated with another nic on sbs and two
static routes in rras?

"Tomo" <zastita@spama.od> wrote in message
news:h9fu41$6n3$1@localhost.localdomain...

> there are sbs2003 as DC, DNS and DHCP server and server standard 2003 with
> isa 2006 in domain isa is connected to adsl router

ISA makes what you want do easier and you won't have to monkey with the SBS
box at all. You don't know how lucky you are that you chose to run ISA2006
on a separate box rather than use ISA2004 on the SBS box.

1. You add an additional Nic to the ISA box. That is a simple task and Nics
are cheap.
2. Give the Nic an IP config that is consistant with a new subnet
3. Go into the ISA MMC and create a "new" Network Defintion. When asked by
the Wizard for the Type choose "internal".
4. Also in the ISA MMC create a new Network Rule. Source-Internal,
Desitnation-<new created network>,....Relationship = "routed" (not NATed)
5. Also in the ISA MMC, create the proper Access Rule to allow traffic
between the new created network and whatever it is expected to communicate
with.
6. Buy a new Switch and plug it into the new nic on the ISA,...plug the new
PCs into this switch that you expect to be using this new segment.

See the ISA's built in Help for details. The built in Help in ISA was done
reasonably well for being a built in help.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Technet Library
ISA2004
http://technet.microsoft.com/en-us/l...chNet.10).aspx
ISA2006
http://technet.microsoft.com/en-us/l...chNet.10).aspx

Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/downlo...7/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/p...s/default.mspx

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/e...epartners.mspx
-----------------------------------------------------

Phillip Windell wrote:
> "Tomo" <zastita@spama.od> wrote in message
> news:h9fu41$6n3$1@localhost.localdomain...
>
>> there are sbs2003 as DC, DNS and DHCP server and server standard 2003 with
>> isa 2006 in domain isa is connected to adsl router
>
> ISA makes what you want do easier and you won't have to monkey with the SBS
> box at all. You don't know how lucky you are that you chose to run ISA2006
> on a separate box rather than use ISA2004 on the SBS box.
>
> 1. You add an additional Nic to the ISA box. That is a simple task and Nics
> are cheap.
> 2. Give the Nic an IP config that is consistant with a new subnet
> 3. Go into the ISA MMC and create a "new" Network Defintion. When asked by
> the Wizard for the Type choose "internal".
> 4. Also in the ISA MMC create a new Network Rule. Source-Internal,
> Desitnation-<new created network>,....Relationship = "routed" (not NATed)
> 5. Also in the ISA MMC, create the proper Access Rule to allow traffic
> between the new created network and whatever it is expected to communicate
> with.
> 6. Buy a new Switch and plug it into the new nic on the ISA,...plug the new
> PCs into this switch that you expect to be using this new segment.
>
> See the ISA's built in Help for details. The built in Help in ISA was done
> reasonably well for being a built in help.
>

than You, this would be much more easy