ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Windows 7 share - accessed from windows 10

    Scheduled Pinned Locked Moved IT Discussion
    13 Posts 6 Posters 3.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • gjacobseG
      gjacobse @scottalanmiller
      last edited by

      @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.

      1 Reply Last reply Reply Quote 0
      • DashrenderD
        Dashrender
        last edited by

        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.

        1 Reply Last reply Reply Quote 0
        • gjacobseG
          gjacobse
          last edited by

          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.

          0_1481676796419_2016-12-13 19_52_10-PAL2016-SHOP2 - NTG - Connected.png

          1 Reply Last reply Reply Quote 0
          • JoelJ
            Joel
            last edited by

            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: !0_1481707858198_FM.JPG

            When i browse to the IP of the windows 7 pc, i get the following error: 0_1481707907058_FM2.JPG

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

            1 Reply Last reply Reply Quote 0
            • JoelJ
              Joel
              last edited by

              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!!!

              dafyreD wirestyle22W 2 Replies Last reply Reply Quote 3
              • dafyreD
                dafyre @Joel
                last edited by

                @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!

                1 Reply Last reply Reply Quote 0
                • DashrenderD
                  Dashrender
                  last edited by

                  Thanks for posting your resolution.

                  1 Reply Last reply Reply Quote 2
                  • wirestyle22W
                    wirestyle22 @Joel
                    last edited by 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.

                    0_1481721880705_names.jpg

                    1 Reply Last reply Reply Quote 0
                    • DashrenderD
                      Dashrender
                      last edited by

                      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.

                      wirestyle22W 1 Reply Last reply Reply Quote 0
                      • wirestyle22W
                        wirestyle22 @Dashrender
                        last edited by 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

                        DashrenderD 1 Reply Last reply Reply Quote 0
                        • DashrenderD
                          Dashrender @wirestyle22
                          last edited by

                          @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.

                          1 Reply Last reply Reply Quote 0
                          • 1 / 1
                          • First post
                            Last post