SpencerSteel
asked on
Map Network Drive across domain ... script & help needed
Guys ...
I am migrating a load of users into a new domain - but they need access to a share called 'cv' on a WORKGROUP called 'Domain' !
I would ultimately like a network drive to be mapped to this location and I assume I would script it ...
But i'm useless at these scripts and not even sure if it's possible ... if someone could write me the script (net use?) I would be appreciated ...
Let's say the users are on 'MyDomain' and need drive 'V:' mapped to a share on ..
'\\domain\fileserver1\cv' with creditials '\\domain\Administrator' and password of 'pw' ...
I hope this makes sense ...
S.S.
I am migrating a load of users into a new domain - but they need access to a share called 'cv' on a WORKGROUP called 'Domain' !
I would ultimately like a network drive to be mapped to this location and I assume I would script it ...
But i'm useless at these scripts and not even sure if it's possible ... if someone could write me the script (net use?) I would be appreciated ...
Let's say the users are on 'MyDomain' and need drive 'V:' mapped to a share on ..
'\\domain\fileserver1\cv' with creditials '\\domain\Administrator' and password of 'pw' ...
I hope this makes sense ...
S.S.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you dont need a domain in thew path as long as the PC can see server by itts name of <server1>
if not
net use v: \\123.123.123.123\share <password> /user:username@the_other_d omain_name .com
where 123.123.123.123 is the IP address of server1
if not
net use v: \\123.123.123.123\share <password> /user:username@the_other_d
where 123.123.123.123 is the IP address of server1
ASKER
OK ... I can hear everyone muttering 'idiot' under their breath ... and I'm with you ... this all makes sense ... but I think the problem is no longer in the script ...
First of all, the error i'm getting back is basically 'The network name cannot be found' - which is true - it can't ... read on ...
1. As a Administrator from MyNewDomain, using Windows Explorer, I can browse to DOMAIN\Server1 ... but there it stops (no shares can be seen) and asks for Credentials, which I can provide as '\\DOMAIN\Administrator' & 'thepassword' ... then I can see all the shares I might like to connect to - as you would expect.
2. A 'normal' user from my domain does not get challenged at the DOMAIN level ... thus they will never 'see' the share.
So, my problem now isn't really one of scripting/mapping the drive ... it's showing the share from the old domain, so users on the new one can 'see' it.
I think.
I thinking that if the users could 'browse' to the CV folder, the mapping thing will be easy - as your scripts are bang on ... I'm just trying to wrap my head around what "Server1\cv" needs for it's shares to be browseable by users on the NewDomain ...
*cries*
S.S.
First of all, the error i'm getting back is basically 'The network name cannot be found' - which is true - it can't ... read on ...
1. As a Administrator from MyNewDomain, using Windows Explorer, I can browse to DOMAIN\Server1 ... but there it stops (no shares can be seen) and asks for Credentials, which I can provide as '\\DOMAIN\Administrator' & 'thepassword' ... then I can see all the shares I might like to connect to - as you would expect.
2. A 'normal' user from my domain does not get challenged at the DOMAIN level ... thus they will never 'see' the share.
So, my problem now isn't really one of scripting/mapping the drive ... it's showing the share from the old domain, so users on the new one can 'see' it.
I think.
I thinking that if the users could 'browse' to the CV folder, the mapping thing will be easy - as your scripts are bang on ... I'm just trying to wrap my head around what "Server1\cv" needs for it's shares to be browseable by users on the NewDomain ...
*cries*
S.S.
>> I can hear everyone muttering 'idiot' under their breath
No one thinks that we are here to help :)
your on two domains that dont trust each other - that being said a computer on domain a cant see a computer on domainb (cause the domains use different DNS - DONT confuse internet DNS with NT Domain DNS - they just look similar :)
still assuming server1 is at 123.123.123.123
from the pc on the OTHER domain can you
ping 123.123.123.123
and get a response, if so
net use v: \\123.123.123.123\share <password> /user:username@the_other_d omain_name .com
should get you on
No one thinks that we are here to help :)
your on two domains that dont trust each other - that being said a computer on domain a cant see a computer on domainb (cause the domains use different DNS - DONT confuse internet DNS with NT Domain DNS - they just look similar :)
still assuming server1 is at 123.123.123.123
from the pc on the OTHER domain can you
ping 123.123.123.123
and get a response, if so
net use v: \\123.123.123.123\share <password> /user:username@the_other_d
should get you on
Ive just tried it on my home domain from a workgrouped PC and it worked?
ASKER
I am an idiot ... and you are helping ... my statement above (2) was incorrect ... i *can* map - via windows XP - to the share from any user.
Therefore, my scripting must be wrong.
I will hand out points now - as you've all been helpful and get to work on this now !
Thanks so much,
S.S.
(facing manual mapping task, he fears.)
Therefore, my scripting must be wrong.
I will hand out points now - as you've all been helpful and get to work on this now !
Thanks so much,
S.S.
(facing manual mapping task, he fears.)
<grin> It never stops it dont matter how much tech you know - theres allways something more complicated and more freaking scary LOL - thats why the experts here dont thing of posters as idiots (well there are a few but thats the eception to the rule mate)
keep us posted
keep us posted
ASKER
ARGH !
NOTE THE SPACE BETWEEN THE DRIVE (z:) AND THE '\\'
*runs screaming*
OK - we are there - solved.
So sorry !!!!!!!
S.S.
NOTE THE SPACE BETWEEN THE DRIVE (z:) AND THE '\\'
*runs screaming*
OK - we are there - solved.
So sorry !!!!!!!
S.S.
ThanQ - I'll stay subscribed in case it all explodes in balls of flames <grin>
>>So sorry !!!!!!!
I can remember doing the same myself in the past - I'll lay good money you never make that mistake again - glad you are fixed, and thanks again
Pete
I can remember doing the same myself in the past - I'll lay good money you never make that mistake again - glad you are fixed, and thanks again
Pete
ASKER
\\domain\server1\sharename
and DOMAIN itself wants a password - I don't think it likes anyone coming in from my domain ... if this server was on the same domain and I could browse to it easily, your method would be spot on ...
... the machine itself is an NT4 box with EVERYONE allowed (Share/Permissions) ... can't think what is obvious that I'm doing wrong.
I wonder if DFS would be better to provide credentials ?
S.S.