Solved

Windows Domain Across 2 Subnets

Posted on 2013-11-05
1
320 Views
Last Modified: 2013-11-26
For a while our entire company has been in a single location.  We have two Windows 2003 domain controllers and about 30 computers running either XP or Windows 7.  We've recently moved 4 of those computers across town to an office about 1/4 of a mile away.  Both sites have a high speed internet connections and are connected via VPN. We feel that the speed of the connection through the VPN is fine.  The computers at the remote site can ping the DC and can UNC into it via\\serveraneme\sharename and can copy and move files back and forth.  It works great from that standpoint.

But they can't log in to the domain with their regular usernames and passwords.  When they connect to the DC via\\servername\sharename they are prompted for credentials the first time they connect.  They enter them and then after that they have access to the share without any more credential requests until they reboot.

But I want them to log on to the domain when they start their computers just like they did when they were at the main location. At the remote location they are in a different subnet.  I've read that in order to do what I want to do I have to go into AD Sites and Services and create a new site. Our existing site is FIRST DEFAULT SITE so I would have to create a second site called DOWNTOWN.  Then I would have to create a subnet object, the subnet of our existing site, and associate it with FIRST DEFAULT SITE.  Then I would have to create a second subnet object and associate it the the DOWNTOWN site. Then I would need to put another DC in the DOWNTOWN site and then create a SITE LINK object to connect the two sites.

Do I really have to go through all this?  It's only four computers.  The budget really isn't there to put a DC downtown.  We could do it if we had to but I'd rather not.

Any advise would be greatly appreciated regarding an easier way and regarding whether or not I have the procedure correct.  Thanks.
0
Comment
Question by:sswmoore
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 15

Accepted Solution

by:
Skyler Kincaid earned 500 total points
ID: 39626286
Why don't you just setup routing between the two subnets? This can be done on your router.

You should still have the other computers setup with their DNS server being your servers.

As long as your are able to route between the subnets, which it sounds like you are able to you should not have any problems leaving the computers on the domain at the other site. You just need to make sure they have the proper default gateway and that gateway has a route to your office.

That way when they send request for the subnet at your main office they have no problem reaching it. You need to make sure that the DNS servers are set correctly so when they query the domain controller they are able to access it. You also need to make sure that the VPN and firewall are setup correctly to allow all the required traffic between the two subnets.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin Within the dynamic life of an IT administrator, we hold many information in our minds like user names, passwords, IDs, phone numbers, incomes, service tags, bills and the order from our wives to buy milk when coming back to home.…
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question