tdog2k4
asked on
Jobsite Standalone Server
I have a need for a standalone server on a remote jobsite. The jobsite will be totally self-sufficient. The problem is being able to connect to the standalone win 2k server with a laptop that is part of the win 2k domain back in the main office. Users in the main office will be moving to this jobsite for several months with thier laptops, and will need to be able to access the applications on the server there. There are several PC's on the jobsite that will be built specifically for the job, so they will not be part of the domain in the main office. I have not set the jobsite server up yet, so I'm pretty much free to do whatever I need. How can I make this functional for both types of users?
ASKER
Thanks for your reply. So in order to go with your first suggestion, I would first have to create the jobsite server here in the office and join it to the domain, correct? Does it have to use AD and be a controller, or just be part of the domain? Then when I move it to the remote site, let's say I am able to get a high speed connection. How do I then connect it back to the network here in the office?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Or, you can have only the connection to the domain, and join the standalone server to the domain. They will be authenticated by the domain controller(s).
Or, if you don't have any connection to the domain, you must declare local users on the standalone server and lose the domain users, since thy cannot be authenticated. These local users will be declared as local users on theyr computer too. I think is necessary to disjoin the computers from the domain and include them in the workgroup which include the standalone server.
The first solution is the best since you can create a dialup connection (or better than dialup) between the new site and the old one, and schedule a replication to occur once a day.