waltb123
asked on
Problem Mapping Drives on a PC from another Domain
I have a user that visits our office frequently. He has a laptop that is a member of another Win2k3 domain. He needs to access our files which are on a shared folder on our Win2K3 domain. The shared folder has the "everyone group" having read permission and his username has acl access to the folder.
I gave this user a username on our domain, so I could map a network drive on his laptop from the other domain, using his credentials on ours, but I get invalid username or password.
Some other notes:
- I know the username and password are correct
- The username is not the same as his actual domains username.
- He has a valid I.P. and can ping the server to which the folder is located.
- The command I'm trying to use us "net use T: \\10.0.0.18\corp /user:username"
- The same command works fine on other computers that are part of our domain.
Let the race begin for the answer and thanks in advance EE community!
I gave this user a username on our domain, so I could map a network drive on his laptop from the other domain, using his credentials on ours, but I get invalid username or password.
Some other notes:
- I know the username and password are correct
- The username is not the same as his actual domains username.
- He has a valid I.P. and can ping the server to which the folder is located.
- The command I'm trying to use us "net use T: \\10.0.0.18\corp /user:username"
- The same command works fine on other computers that are part of our domain.
Let the race begin for the answer and thanks in advance EE community!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi waltb123,
just make sure you can view the share to start
\\servername and see if it find the share
just make sure you can view the share to start
\\servername and see if it find the share
ASKER
I'll give it another try as soon as this person returns with his laptop, usually within a week or two. I'll be back in touch. Thanks for the input.
unless that person;s domain has a trust to yours you will have to put the domain name infront of the username as described above.
ASKER
Ok I tried adding the domain name so that the complete command entered is:
net use t: \\10.0.0.18\corp /user:ourdomain\username
Still getting response of:
System Error 53 has occured. The network path was not found.
The share does not seem to be visible to computers that are not members of the domain, because the same command typed in on a computer that is a member of the domain works immediately.
Any more suggestions?
net use t: \\10.0.0.18\corp /user:ourdomain\username
Still getting response of:
System Error 53 has occured. The network path was not found.
The share does not seem to be visible to computers that are not members of the domain, because the same command typed in on a computer that is a member of the domain works immediately.
Any more suggestions?
ASKER
PS- Cannot view the share as suggested by Jay_Jay by doing \\servername.
One other note, this is a Small Business Server 2003 environment, not sure if that should matter or not. Our old server system that we just upgraded from SBS on NT4, had this type of mapping and it worked fine exactly as stated above.
I'm thinking there maybe a security policy setting I'm unaware of that may be preventing mapped drives from non-domain computers.
One other note, this is a Small Business Server 2003 environment, not sure if that should matter or not. Our old server system that we just upgraded from SBS on NT4, had this type of mapping and it worked fine exactly as stated above.
I'm thinking there maybe a security policy setting I'm unaware of that may be preventing mapped drives from non-domain computers.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'll give that a try as soon as he comes back again! Thanks.
Can you at least check the permissions on the server end to make sure they are like that?
ASKER
Of course!
Share perms are Everyone- Full
NTFS perms are Everyone - Full
The underlying folders beneath the share folder, do not have Everyone group at all, instead, a security group called "Interna" which consists of all persons located at this office who should have access theirin, have READ permissions, sub-folders within that upper level folder have Change permissions.
Although the group "domain users" has no set permissions on any of the folders/files, the group "Internal" does. Instead I rely on the group I made, because all domain users are not authorized for access to those folders. And no one else has a problem accessing the folders, only those computers that are not part of the domain.
Share perms are Everyone- Full
NTFS perms are Everyone - Full
The underlying folders beneath the share folder, do not have Everyone group at all, instead, a security group called "Interna" which consists of all persons located at this office who should have access theirin, have READ permissions, sub-folders within that upper level folder have Change permissions.
Although the group "domain users" has no set permissions on any of the folders/files, the group "Internal" does. Instead I rely on the group I made, because all domain users are not authorized for access to those folders. And no one else has a problem accessing the folders, only those computers that are not part of the domain.
i wouldnt set everyone with full ntfs permissions. i'd utitlize the domain users security group.
ASKER
I only did that in attempt to isolate the problem. I dont typically use the Everyone group at all, other than on share permissions.
do you know his username/pw? try logging him onto a computer that's on the domain
ASKER
He has been resorting to using the desktop PC in the office he borrows since he cant use his laptop. He logs in with no problem, as the domain user account i set him up with (which is different than his username at his real domain).
When he was trying to map the network share on his laptop, he removes the network cable from the desktop PC, plugs iit nto his laptop, boots, and verifies he can connect to the internet from it and then attempts the mapping. So not a connection/cable or username problem as well. Uggghhhh.
When he was trying to map the network share on his laptop, he removes the network cable from the desktop PC, plugs iit nto his laptop, boots, and verifies he can connect to the internet from it and then attempts the mapping. So not a connection/cable or username problem as well. Uggghhhh.
also try this, when he comes in try logging in with your username and password.
ASKER
I tried that too and I'm of the administrators group.
did it work?
ASKER
No it didnt, same System Error 53.
Don't know the full "net use" syntax, if you try to create the drive through Windows Explorer - Tools - Map Network drive - Browse ...
im assuming net use x: \\servername\sharename doesnt' work?
ASKER
Towards the top of this post, I mentioned that this doesnt work.
i'd like to see an ipconfig /all from a client on the domain, the domain controller, and this person's laptop.
michael
myfootsmells
michael
myfootsmells
ASKER
I'll have to wait until this person returns once again to our office.
alright let us know
ASKER
Ok, the gentlemen came back in and I tried to map the network drive from Windows Explorer again and this time it mapped the networked drive! The only thing I did different this time was to drop the suffix of our domain. I guess your not supposed to use the FQDN???
For example, when I right "my computer" and look at the Computer name tab, my computer name is listed as:
ComputerName.OurDomainName
So for all the examples given above where it was suggested to include the domain name in the login name for authentication to the domain, I was using (for example): OurDomainName.Local\JohnDo
This time, I tried dropping the .local as such: OurDomainName\JohnDoe
And it worked! So I learned something today. Thanks a lot everyone who took a stab at the problem. =) Till we meet again!
For example, when I right "my computer" and look at the Computer name tab, my computer name is listed as:
ComputerName.OurDomainName
So for all the examples given above where it was suggested to include the domain name in the login name for authentication to the domain, I was using (for example): OurDomainName.Local\JohnDo
This time, I tried dropping the .local as such: OurDomainName\JohnDoe
And it worked! So I learned something today. Thanks a lot everyone who took a stab at the problem. =) Till we meet again!
ASKER