Discussion Locked

Cannot Access Share in Different Domain

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Win95 user that logs-in to local Domain1. Then machine is re-started and user logs-in to Domain2 to map a network share in a server in Domain2. User re-starts the machine and logs-back into Domain1 and was prompted for a password for the share from Domain2. Eventhough the correct password is supplied, Win95 says "Invalid Password". I tried making both Username and Password in these 2 domains similar, still user cannot access. WINS is properly propagated w/ Domain2's DC IP and Domain Info and user also uses LMHOSTS but still no go. Win95 does not have the "Connect As" option in mapping to a network share unlike Win NT Wkstation. Is there any workaround w/out upgrading O.S. to Win NT Wkstation??? Thanks.

17 replies

by ishmael

domain trusts always confuse me, but i think unless you have domain 2 trusting domain 1 then when you log in to domain 1 in win95 you do not get access to domain 2. what are the domain trusts?

by spydergst1

I recently went through this. You do have to setup a trust relationship. But thats just the first part. You have to add the user to the backup operator group and restict permissions to the rest of the server for that group. Just assign permissions to the directory you want the backup group to have access to. trust mu I know this was my solution.

by aekland

Haven't used 95 in a while so I cannot confirm that a trust is the only way to connect but I will say that you do not have to add the user to the 'backup operator group.' You can create a group and add them to that and assign the group with permissions. Adding someone to the backup operator group is a security risk.

by gregory w. smith

If the username/password on the Win95 machine is identical to the username/password for Domain1 and also for Domain2, you do not require a trust relationship.

(That's what "Local user accounts" are for on a Domain)

So, you should setup a localuser in Domain2's user manager then do everything logged in to Domain1.

by junp14

This is exactly what I did, but still I get a message thqat says, "Invalid Password. Try Again". Anymore idea? Thanks.

by reillym_98

There is lots not explained here but if dom1 & dom2 are not fully trusted domains and you are connecting to a share on a server that is not the pdc\bdc in dom2 then add user name to local user on the server where resource (share) is. Then add permissions to share using the local user on that server not the domain user name in dom 2 .

by dheupel

In addition to Answers 4 & 5, give the user account on Domain #2 that you created the "Log on Locally" access right, but set appropriate restrictive persmissions for the user group the account is a member of.

Really, though, the best way to go about this is a trust relationship between Domain1 and Domain2, unless you are absolutely, positively, 110% certain that no-one else in your organization will ever need access to resources that are across domains.

Good luck.

by eltonsipes

Sounds like alot of logging back and forth. I recomend having the user log into only one domain. If that user needs to access resources on the other domain, then add that user's account name-his domain, to the share permissions for the resources on the other domain. I have setup this situation for some of my users in the past. Can't say if trusts are necessary for this as both my domain have always had full trusts both ways. But for best overall success, security and user's ease of operation go to a single NT4.0 domain with 1PDC,1BDC plus a standalone file server. NT4.0 workstation sells for about $38, and NT4.0 server is about $20 per client user, and service packs are all free, and NT is so much more fun for networking. Good luck.

by mike.crain

Create an indentical user account on both domains with matching passwords and also from a server end, make sure the domains are trusted.

This discussion is closed to new replies.