Connecting to a server OUTSIDE the user's domain

[Chris Benton]

Situation: I have a number of clients who are on different subnets/domains
who need a resource in my subnet/domain. (Ex: The server is in the 128.82.174
subnet; the users are in the 128.82.224 subnet, and they authenticate to a
different domain.) These users all have login accounts prepared on my server.
What I want to do for these clients is map them a drive letter to a network
share on my server, but I'm having difficulty setting up the connection.

I've tried to set up the server as a trusted site via Internet Explorer, but
when I go to map the drive, I get an error that says the path cannot be
found. The users are able to ping the server. Suggestions?

 

[Lanwench [MVP - Exchange]]

Situation: I have a number of clients who are on different
subnets/domains who need a resource in my subnet/domain. (Ex: The
server is in the 128.82.174 subnet; the users are in the 128.82.224
subnet, and they authenticate to a different domain.) These users all
have login accounts prepared on my server. What I want to do for
these clients is map them a drive letter to a network share on my
server, but I'm having difficulty setting up the connection.

I've tried to set up the server as a trusted site via Internet
Explorer, but when I go to map the drive, I get an error that says
the path cannot be found. The users are able to ping the server.
Suggestions?

This isn't something you'd do in IE - and the subnets have nothing to do
with it. The issue is, how are they connected (rather, what separates them).

Make sure they can ping your server by name.

If you don't want to set up trusts, but just want the occasional user on
domain A to access a shared resource on domain B, then I'd setup a little
batch file for them to put on their desktops...something like this.

net use x: \\server\sharename /user:OTHERDOMAIN\username /persistent:no


They'll be prompted for their password on OTHERDOMAIN when they try to
connect. I *think* you can put the /persistent:no switch at the end of the
/user switch.... if it doesn't work, reverse them. This switch is important
to use or their computers will constantly try to connect to the drive even
when they don't want to, and will nag for passwords.

 

[John B]

Please clarify if OTHERDOMAIN is Domain A, or Domain B.
Thanks.

"Lanwench [MVP - Exchange]"

 

[Leythos]

Situation: I have a number of clients who are on different subnets/domains
who need a resource in my subnet/domain. (Ex: The server is in the 128.82.174
subnet; the users are in the 128.82.224 subnet, and they authenticate to a
different domain.) These users all have login accounts prepared on my server.
What I want to do for these clients is map them a drive letter to a network
share on my server, but I'm having difficulty setting up the connection.

I've tried to set up the server as a trusted site via Internet Explorer, but
when I go to map the drive, I get an error that says the path cannot be
found. The users are able to ping the server. Suggestions?

Bad move unless you setup VPN connections.

Try reading about FTP, it's the way this has been done across the
internet for decades.

--

Leythos
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
(e-mail address removed) (remove 999 for proper email address)

 

[Shenan Stanley]

Lanwench [MVP - Exchange]

net use x: \\server\sharename /user:OTHERDOMAIN\username
/persistent:no

Please clarify if OTHERDOMAIN is Domain A, or Domain B.
Thanks.

....

Your user logs into their computer.
It does not matter if they logon to a domain or local. It doesn't matter
what domain they are in. None of that matters...

The command Lanwench gave you:

net use x: \\server\sharename /user:OTHERDOMAIN\username /persistent:no

Could be written like so:

net use x: \\server-to-connect-to\sharename-on-said-server
/userOMAIN-said-server-is-in\username-for-user-in-the-domain-the-server-being-connected-to-is-in
/persistent:no

It should ask for the password.

Depending on DNS, Firewall, routes essentially - how you get to that server
and if you can map said share even with the proper credentials varies.