Hi everyone, I've tried to explain this as simply as I can, so probably given you all too much info as usual, but here goes. I have a W2k3 AD Domain called xxx.yyy.com (real name withheld) xxx.yyy.com is NOT used or registered for public DNS use. It is ONLY used internally. I have two DCs (W2k3) using AD Integrated for the main AD zone (xxx.yyy.com) So far, only one of these (AD1)

Your reaction to not using DHCP is a little strong and not the Gospel you present it as. Most banks don't use DHCP and many small banks or branches use Small Business Server. There is more than One Good way to do things, depending on the circumstanes. A static IP host environment does not need a dynamic addressing system. DNS forward lookup records are updated by clients with or without

one SBS, two AD sites, no problem. If that SBS is R2 you would do well to implement a 2nd server at the remote site, and maybe 2nd Exchange which R2 would require a 2nd Exchange Server license for but no additional CALs. SBS 2003 SP1 does not get 'extended CAL rights'. 20 users at each of 2 sites does not put you into 'I need two AD's' territory'. Of these '20 users in each company'

I haven't played with the DHCP 'class id' scenario but 1. Dont' use DHCP is WRONG, _bad_ advice, my main reason for responding to this thread. MS AD (ie. it's not really an 'SBS' question) integration betwen DHCP/DNS and AD makes this a bad method of address. 2. Use DHCP reservations Can work, but it takes management. moreover, if the total network environment does not exceed SBS