Re: new domain existing LOB PCs attached to workgroup, how to leav

If you want the external NIC on the server to be in the 192.168.16.x subnet then you have to change the router to the same subnet. Change the router to 192.168.16.1. Turn off DHCP on the router. Set the external NIC IP in the server to 192.168.16.2 with a gateway of 192.168.16.1. Set the internal NIC IP to 192.168.1.2 and run the CEICW wizard again. It will pickup the router and make the correct DNS settings for that interface. It should also set the internal subnet to 192.168.1.x and setup all the DNS, WINS, DHCP etc.. You may have to setup DNS forwarding and reservations in DHCP for the two LOB computers but for a start just do the above and see what happens.

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca


"Magnetoram" <Magnetoram@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4AE9313B-6650-4848-A9E0-ABE47576E989@xxxxxxxxxxxxxxxx
during setup windows assigned 192.168.1.104 as internal NIC IP and gateway as
192.168.1.1 the ip of the router. Will I be able to change the router to
192.168.16.1 and the external card to 16.2 and have the computers and LOB
boxes setup after install completes and do the rest of the configuration? I
am new to all the dhcp exclusions and such and may need further help

"SuperGumby [SBS MVP]" wrote:

NO, having two NICs in the same subnet will cause problems.

Linksys 192.168.X.1 /24 (ie. mask 255.255.255.0)
|
|
SBS External 192.168.X.2 /24 DG 192.168.X.1 (DNS internal)
SBS Internal 192.168.Y.2 /24 (DNS self)
|
|
internal switch to workstations

Sounds like you need to keep Y=1, X should be anything but 1.

and I'd create MAC based DHCP reservations for your LOB servers and run them
as DHCP clients.

"Magnetoram" <Magnetoram@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AC89B986-485A-4124-B6F3-43AE58279197@xxxxxxxxxxxxxxxx
> thanks for the post... what I understand is this. The static is set on > the
> router, I will leave the router with 192.168.1.1 as starting IP > External
> SBS
> card to 192.168.1.2 and internal 192.168.1.3
>
> "Charlie Russel - MVP" wrote:
>
>> You use the CEICW and let IT do the settings. ;)
>>
>> The CEICW will set your internal card to point to .1.2 for DNS >> (itself)
>> and
>> no gateway.
>>
>> -- >> Charlie.
>> http://msmvps.com/blogs/xperts64
>>
>> "Magnetoram" <Magnetoram@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:9ED2CFE4-90EE-4784-BBBA-ED2769FFCF24@xxxxxxxxxxxxxxxx
>> > thanks for the post... Line Of Business One box is W2K and the other >> > is
>> > not
>> > windows. I am not sure what is on it. The LOB tech support said they
>> > did
>> > not
>> > have to be joined to the domain just need to be on the same IP >> > range.
>> > Right
>> > now every pc that needs to access them can and the way the tech >> > support
>> > guy
>> > said it there should be no problem. I can include exceptions for >> > 1.10
>> > qnd
>> > 1.11 and set to auto. When I set the internal card for gateway and >> > dns
>> > do
>> > I
>> > point it to the external card with 192.168.16.2
>> >
>> > "Claus" wrote:
>> >
>> >> And LOB stand for what? What OS is running on those 2 boxes?
>> >>
>> >> Your address schema will work fine. To make your life easier I >> >> would
>> >> change
>> >> the workstations to DHCP so you don't have to make manual entries >> >> for
>> >> Gateway, DNS and WINS. Don't forget to configure your DHCP server >> >> with
>> >> exceptions for 1.10 and 1.11.
>> >>
>> >> Your shortcuts will work pending on the right access rights on >> >> those
>> >> shares.
>> >> I'm not sure why you don't want to join them into the domain. What >> >> is
>> >> the
>> >> reason?
>> >>
>> >> -- >> >> Claus
>> >> "Magnetoram" <Magnetoram@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in >> >> message
>> >> news:0F17CB34-DBA5-473B-A9DB-C9FE4E7A50AE@xxxxxxxxxxxxxxxx
>> >> > New Domain. Static IP will be set on Linksys router. Want to use
>> >> > 192.168.16.1
>> >> > as starting IP and set the external NIC on the SBS box to
>> >> > 192.168.16.2.
>> >> > On
>> >> > the Internal NIC I want to have the IP range begin with >> >> > 192.168.1.1
>> >> > because
>> >> > the workgroup now has all machines with static IP in the >> >> > 192.168.1.x
>> >> > range.
>> >> > Reason I want to keep this is there are 2 LOB computers connected
>> >> > with
>> >> > IPs
>> >> > set at 192.168.1.10 and 1.11 that the existing computers have
>> >> > shortcuts
>> >> > pointing at. I will not join these 2 LOB machines to the domain.
>> >> > Will I
>> >> > be
>> >> > able to use these shortcuts that point to these LOB boxes if I do
>> >> > not
>> >> > join
>> >> > them to the domain?
>> >>
>> >>
>> >>
>>




.

Relevant Pages

  • Re: SBS 2003 Misconfigured?
    ... I've thrown quite a bit at them, and just have to disagree that they are inherently less secure than the netgear. ... setup DHCP and I have also gone in and manually created a new scope ... when I first used the Netgear router with SBS 2003, ... than one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... eth0 172.26.0.1/16 Extra none ... That would be the address you need a DNS record for. ... One question - if I reset the Thomson Router will that clear all the ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: NAT/RD install quirkiness. Server seems to work fine, but why
    ... DHCP is disabled and only a range of static IP addresses are ... One of which is the server. ... Although I don't have the DNS settings in front of me, ... router as the gateway. ...
    (microsoft.public.windows.server.networking)
  • Re: Connecting Remotely to Server/Desktop Files (Remote Access)
    ... The router will have two sets of DNS entries: ... Those it gives to DHCP clients. ... DNS servers it uses on it's external interface.) ... > I'll try it later this evening when I'm at the server and see if it works. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... No 10.0.0.138 is the address used to log onto Thomson's router to make the ... On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0 172.26.0.1/16 Extra none ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
Loading