new domain existing LOB PCs attached to workgroup, how to leave as

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?

 

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?

 

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

 

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.

 

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

 

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.

 

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

 

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

 

Thanks for the post.. I will after setup completes. I have DHCP disabled in
the router , setup required it. One thing happened when I previously changed
the router to 16.2, I could not access the setup page using 192.168.16.1 I
had to restore to factory defaults and set static ip and left 1.1

 

If you changed your router to 192.168.16.2 then you have to access the setup
page using the address 192.168.16.2. You will also have to access the
router setup from the server web browser I believe because your workstations
will be on a different subnet.

Jeff

 

thanks for the post, ipconfig /release /renew solved this little glitch