Windows 7 share - accessed from windows 10

[Joel]

I am hitting my head against a brick wall with this.

Scenario: a new windows 10 pro computer was bought and we wish to connect to a simple file share on a long standing existing Windows 7 Pro computer in the same network.

The Windows 7 pc belongs to a workgroup and it's IP is 192.168.53.10 with hostname (dgserver)
I can ping this IP and the hostname from the windows 10 computer but when I try to browse it tells me I do not have permissions.

Note: when browsing it doesnt even give me an option to authenticate with a username and passowrd.
Sharing a folder on the Windows 10 pc and connecting from the Windows 7 pc works no problem but i want it working the other way!

I have checked the folders security and sharing permissions and EVERYONE has full control to it.
Network and sharing settings look good.
Tested with firewall off and disabled AV - no joy!

Any ideas? im missing a trick somewhere here!!!
HELP!

[scottalanmiller]

I think that you have to disable a security requirement on Windows 10, but without Windows in front of me, I have no idea what it is

[gjacobse]

@scottalanmiller said in Windows 7 share - accessed from windows 10:

I think that you have to disable a security requirement on Windows 10, but without Windows in front of me, I have no idea what it is

Is this a case of Linux for the fail?

Sadly I don't have a Windows 7 system here either, But I am pretty certain it is a simple security item. Let me check on what I do have available and let you know.

[Dashrender]

a post I just read says that you have to give computername\username not just username, but you said you aren't even getting a prompt.

[gjacobse]

Created a share on c:\ called Test Share.
Shared the folder via Advance Sharing and set allow to all

Using the IP for the computer, found a Win10 box, and was able to open the share and create folder in it.

[Joel]

Thanks all for the response so far. I have tried creating a brand new share with everyone with full control but yet, i cannot browse to that share.

When I browse to the hostname, I get the following error: !

When i browse to the IP of the windows 7 pc, i get the following error:

i'm also sure something simple but cant quite pin point what!

[Joel]

OK this is now working.
The user account I was logged into the Windows 10 PC with didn't exist on the host server.
Once i created the same user and password on the Windows 7 PC it was working!!!

[dafyre]

@Joel said in Windows 7 share - accessed from windows 10:

OK this is now working.
The user account I was logged into the Windows 10 PC with didn't exist on the host server.
Once i created the same user and password on the Windows 7 PC it was working!!!

We like easy fixes!

[Dashrender]

Thanks for posting your resolution.

[wirestyle22]

@Joel I've run into weird issues with Windows in the past. I'd always use the IP address of the file server (Example: \\192.168.53.10\public). Also, when you attempt to map a network drive it gives you the option to connect using different credentials.

[Dashrender]

Sure, but you shouldn't need to map a drive to make a connection.

His weirdness is that that
\server ip\sharename never gives him the option to give a username and password like we are accustomed to.

I'm sure it's an updated security thing in Windows 10, for example a newer version of kerberos, etc.

[wirestyle22]

@Dashrender said in Windows 7 share - accessed from windows 10:

Sure, but you shouldn't need to map a drive to make a connection.

His weirdness is that that
\server ip\sharename never gives him the option to give a username and password like we are accustomed to.

I'm sure it's an updated security thing in Windows 10, for example a newer version of kerberos, etc.

I wonder what net use z: \\server\share /user:server\user would kick back

I think if you add /persistent:no to it, you will always get a prompt if I remember correctly

[Dashrender]

@wirestyle22 said in Windows 7 share - accessed from windows 10:

@Dashrender said in Windows 7 share - accessed from windows 10:

Sure, but you shouldn't need to map a drive to make a connection.

His weirdness is that that
\server ip\sharename never gives him the option to give a username and password like we are accustomed to.

I'm sure it's an updated security thing in Windows 10, for example a newer version of kerberos, etc.

I wonder what net use z: \\server\share /user:server\user would kick back

I think if you add /persistent:no to it, you will always get a prompt if I remember correctly

Net use does the same thing your GUI pictures above does.