Question Locked

3P Confused Work Group vs Domain

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Dearest Folks,

I have what most must consider an easy fix, but I am confused and have not had to do something like this is way too long.

The details are as follows:

Objective - allow users to access a share on 3 different pcs with out allowing the pcs to be part of Old Domain B. Old Domain B will only allow a one way trust.

Ideas:

1. I could set up a New Domain A that would communicate with the Old Domain B. I could set up a one way trust with Old Domain B. This would allow their users to access shares on New Domain A without allowing New Domain A access to Old Domain B. I would only allow a one way trust so that Old Domain B can access shares on New Domain A. This seems an extreme way to reach their objective.

2. I thought about setting up a Work Group. Creating a share on the 3 pcs with security and permissions set for everyone full control. However, if I am a user in Old Domain B, how would I be able to access the shares on the 3 pcs that are in the Work Group and not part of Old Domain B.

Again, Old Domain B does not want my pcs on their network. They will only allow a one way trust. I believe setting up a New Domain A is over kill.

Can someone please help me, as I require a solution by Sunday 7/29/07

3 replies

by churdoo

To make your Option 2 Workgroup option work, and assuming that the 3 workgroup computers have name resolution to Domain B and are W2K Pro or Server or higher (will even work with NT 4.0),

1. Create a dummy local user account on the 3 workgroup peers, call it domain.access for example. Make the same username/password on all 3 peers.
2. Create the shares on the peers, giving the local domain.access account whatever permissions it needs (Full Control presumably)
3. To access the share(s), if all users need access, then I would add to the Domain B login script, for example
"net use X: \\peer1\share1 /user:domain.access "
"net use Y: \\peer2\share2 /user:domain.access "
"net use z: \\peer3\share3 /user:domain.access "

where above is the password that you assigned to the domain.access user account.

If you don't have access to the domain B login script, or don't use one, create a batch file(s) that you can either put in the STARTUP group on domain B workstations, or in a central location that users can click when they need access

If you would rather have users browse the peers (ugh! I hate letting users browse my networks), then they will be challenged when they try to access the peers, and you will have to circulate the domain.access user/pass for the users to provide in the "Connect as" dialogue when challenged.

Or you may put commands like this in a login script or STARTUP program group

"net use \\peer1\ipc$ /user:domain.access "
"net use \\peer2\ipc$ /user:domain.access "
"net use \\peer3\ipc$ /user:domain.access "

The above will set up a connection to a common hidden share on each of the peers for the purpose of providing the common domain.access user credentials, and the users can now browse the peers and those credentials will be used without challenging the users.

dammit I typed too long again! Sorry, just trying to be thorough (and get thumbs up). :-)

by shadee3p

You are really good and I greatly appreciate your response to my conundrum. I cannot thank you enough. Thank you and a great big thumbs up.

This discussion is closed to new replies.