Can Windows Essentials 2012 co-exist on same network as Win 2000 SBS - different domains

Background:  I am replacing an old Windows 2000 SBS Server with a Windows Server 2012 Essentials R2.  Since we only have 10 active users we decided that rather than try and migrate from SBS 2000 we would just build the 2012 Essentials box from the ground up as a different domain.

We have a cable modem/router in front of a Cisco RV082. Our SBS 2000 network uses all static IP addresses and is behind the RV082. Both the Cable router and the RV082 have DHCP enabled.  The RV082 is our gateway and has a different subnet from the cable router.

For initial configuration I connected the 2012 server directly to the cable router and allowed it to get an IP via DHCP. This worked fine.  I added a single client to this network as a test using a static IP in the same range  as the server but outside the DHCP pool.  I was able to join the new domain and see the shares.   All is good,

I am close to being ready to start adding client PC's to the new domain.  I read here on Experts exchange that two SBS servers with different domains could exist on the same network segment so long as DHCP wasn't enabled. Since my current network is all static IP and by default Server 2012 Essentials does not have DHCP enabled I decided to give it a try.

First I disconnected Server 2012 from the network, then changed it's IP address to a static IP in the same segment as our SBS 2000 Server. I set the gateway IP to the RV082 and allowed the DNS to keep it's default localhost address.  Once this was done I connected Server 2012 to an open port on the R082.  It properly ID's the network as the new domain, but says No Internet under status.

On the client PC (Windows 8) I changed the IP to be on the same segment, the gateway to be the RV082 and the DNS to the static IP of Server 2012 then connected it to the RV082.  It does not recognize the network as the domain also has No Internet under status, It can't connect to the server shares.  I can't tell for sure if it is authenticating with the server because Win 8 will allow access using a domain login even if the network isn't connected.

Is what I am doing possible and I just missed a step somewhere?

My next step was to go back to connecting to the  Cable Router but still use the static IP (in the cable router's subnet) on the server and client to see if that works.
BRT-TechAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Sounds like DNS is misconfigured or blocked somewhere along the path between the 2012 server and the outside world. A bad subnet mask could also play a part.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Dirk MareSystems Engineer (Acting IT Manager)Commented:
The domain id you can force with dhcp from server 2012.

Is domain resolution working for both internal and external?
Ping servername
Ping www.google.com

Can you please confirm working internet on the rv082?

DirkMare
0
BRT-TechAuthor Commented:
@Cliff - I don't see anywhere in Essentials 2012 R2 to configure DNS.   The DNS Server Service is running.  I've done nothing to block the server from the outside world. The SBS 2000 Server is connected the same way and it can resolve outside addresses.

Subnet mask looks OK - set to 255.255.255.0
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

BRT-TechAuthor Commented:
@Dirk -  Not sure I understand your first comment.

I can ping the server by both IP and name.

I can not ping any outside address if the DNS setting on the client PC is set to the server IP.  However, if I allow DHCP to set the DNS I can then ping or connect to anything on the internet.

RV082 has good internet. I am using it to type this reply from a client of the old server.
0
Cliff GaliherCommented:
By default, the DNS server role is configured to use root hints for recursive lookups. If you are blocking DNS lookups to root hints at the network edge, such as only allowing DNS to your ISPs servers, that'll cause Essentials DNS server to fail to look up outside addresses.

There is *nothing* unique to Essentials in this.  You configure DNS Server settings just like you would on standard or datacenter. You can configure forwarders or keep root hints, but the DNS server has to be able to reach the outside servers you choose, which means your firewall and router have to properly route that traffic.
0
BRT-TechAuthor Commented:
Additional:  I can ping the server from the client and the client from the server from the server.  What I cant do is ping any external address from either when the client is set to use the server as DNS.  Appears to me that the server does no know how to reach external DNS.  I know the IP's it should have for my ISP's DNS, but don't know where to put them.

Assuming Essentials 2012 is set up similar to SBS 2000.  On SBS 2000 under IP 4 settings the DNS is set to the server IP on both the server and the clients.    Essentials 2012 defaulted to localhost 127.0.0.0 so I just left it that way.
0
Cliff GaliherCommented:
You configure forwarders in the DNS server console. Not on the IPv4 settings. Leave those alone. They are set to properly use the DC as a DNS server, which is critical to proper AD functionality.

This hasn't changed much since SBS 2000 either.  Also make sure your default gateway *is* configured properly in the NIC IPv4 settings for your router. As that is important and can cause issues. So don't change DNS there. But do change the default gateway if necessary.
0
BRT-TechAuthor Commented:
Cliff pointed me in the right direction.   I located DNS Manager and started looking around.  I found a bunch of entries from when I first started the server that had the wrong IP (10.1.10.x from the cable router).  I took a chance and deleted these entries leaving only the entries from the RV082 (10.1.1.x) and now all is well.

So yes, it was a DNS configuration issue.  Thank you.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.