Connect to mapped network drive not on domain

Darrensen · 4 Nov 2015 at 11:37

Hi,

Is it possible for a computer that is connected to a domain to connect to a share point that is not on the domain?

I was under the impression you could, simply by....

(name of server)\username
password

Thanks

agnes · 4 Nov 2015 at 11:40

Can you discover the drive? As in see it and try to connect to it?

If so, should be fine.

Darrensen · 4 Nov 2015 at 11:44

Thanks Angnes for the reply.

What do you mean by Discover the drive?

agnes · 4 Nov 2015 at 11:48

So, if I am on my home network, I can see other network devices, such as my girlfriends PC. If she has a share enabled, I should be able to double click on her computer to reveal the share. Then if I try to open the share, it states I need credentials.

At this point, I would put as you say:

HerPC\Username
Password

As for discovering inside a domain for anything external. Not 100% sure, never tried it. I doubt it will be as simple as above for a home network.

thenewoc · 4 Nov 2015 at 12:01

This happened to me the other day trying to shift something between a W10 Pro PC and a W8.1 Pro laptop. To solve it quickly I went down the path of setting up Home Group on both and then went in to the share tab on the folder where I wanted to put stuff and selected the user name I use on the desktop and changed the drop down to allow read and write access. Then I could navigate to that folder from the Network tree in Windows Explorer from the desktop.

Darrensen · 4 Nov 2015 at 12:02

Got it. That's basically what i'm doing.

As the drive needs to be accessed from outside the network it needs to be a mapped volume.

Darrensen · 4 Nov 2015 at 12:04

Just to add, if the computer is not connected to a domain, the login works perfectly.

swain90 · 4 Nov 2015 at 12:30

Maybe try using

.\Username

instead of

Computername\Username

agnes · 4 Nov 2015 at 13:04

swain90 said:
Maybe try using

.\Username

instead of

Computername\Username

Thats local only.

Darrensen · 4 Nov 2015 at 13:28

I can see the problem in the logs now.

Machines that work connect using ntlmv2, this one is using ntlmv1.

Is there a way to force it to connect over ntlmv2?

Darrensen · 4 Nov 2015 at 13:49

FIXED!

Need to go into regedit and change HKLM\System\CurrentControlSet\Control\lsa from "1" to "3".

Now uses ntlmv2!

gpuerrilla · 4 Nov 2015 at 18:39

Darrensen said:
FIXED!

Need to go into regedit and change HKLM\System\CurrentControlSet\Control\lsa from "1" to "3".

Now uses ntlmv2!

Nice. Glad you have it sorted Darren!