password protected network share


  1. joshthegooglist
    Posts : 10
    7 Home premium
       New #1

    password protected network share


    i have a server at my business running windows server 2000 (yes i know i should upgrade, but im making use of equipment we have) with a network share that requires a user name and password to access the share. Within the building there are about 50 computers with OS's ranging from windows 2000 to windows 7. Ive tried logging on with all the machines, but the windows 7 machines will not accept my credentials. under the unsername and password fields it shows the domain as the local computer name. What we have is a workgroup based setup, so aside from upgrading the server OS, is there anything i can do to access this share from the windows 7 machines?

    Thanx
    -JP
      My Computer
    Quote Quote

  3. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #2

    joshthegooglist said:
    i have a server at my business running windows server 2000 (yes i know i should upgrade, but im making use of equipment we have) with a network share that requires a user name and password to access the share. Within the building there are about 50 computers with OS's ranging from windows 2000 to windows 7. Ive tried logging on with all the machines, but the windows 7 machines will not accept my credentials. under the unsername and password fields it shows the domain as the local computer name. What we have is a workgroup based setup, so aside from upgrading the server OS, is there anything i can do to access this share from the windows 7 machines?

    Thanx
    -JP

    Is it a full drive share ($C:\)?

    Are you using homegroup on the win 7 machine, or more importantly are you using IPv6?


    Ken J
      My Computer
    Quote Quote

  4. joshthegooglist
    Posts : 10
    7 Home premium
    Thread Starter
       New #3

    1) no
    2) no
    3) ipv6 is not disabled on the 7 machine if thats what u are asking
      My Computer
    Quote Quote

  6. chev65
    Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       New #4

    This requires that you change the lanman server parameters in order to get Windows 7 working with older servers. Do these adjustments on the Windows 7 machines that need to connect to the server.

    Control Panel - Administrative Tools - Local Security Policy

    Local Policies - Security Options

    Network security: LAN Manager authentication level
    Set to Send LM & NTLM responses only

    Set the Minimum session security for NTLM SSP
    Disable Require 128-bit encryption

    The screen shots below should be helpful.

    Reboot all machines after making the adjustment.

    This has nothing to do with IPv6.

    The Argument against Disabling IPv6
    It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
    From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
    Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

    Read more. http://technet.microsoft.com/en-us/m....cableguy.aspx
    Attached Thumbnails Attached Thumbnails password protected network share-lanman-server-adjustment.png   password protected network share-require-128-bit-encryption-unchecked.png  
    Last edited by chev65; 31 Aug 2013 at 10:25.
      My Computer
    Quote Quote

  7. joshthegooglist
    Posts : 10
    7 Home premium
    Thread Starter
       New #5

    thanks ill give that a try and let you know
      My Computer
    Quote Quote

  8. joshthegooglist
    Posts : 10
    7 Home premium
    Thread Starter
       New #6

    ##### RESOLVED. Thank you very much chev65
      My Computer
    Quote Quote

  10. WindowsStar
    Posts : 2,737
    Windows 7 Enterprise (x64); Windows Server 2008 R2 (x64)
       New #7

    chev65 said:

    The Argument against Disabling IPv6
    It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
    From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
    Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.
    +1
      My Computer
    Quote Quote

  11. chev65
    Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       New #8

    joshthegooglist said:
    ##### RESOLVED. Thank you very much chev65
    I'm glad that worked for you josh. Thanks for reporting back in. :)
      My Computer
    Quote Quote

  12. chev65
    Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       New #9

    WindowsStar said:
    chev65 said:

    The Argument against Disabling IPv6
    It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
    From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
    Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.
    +1
    It just had to be said, there is more to the IPv6 protocol than meets the eye.
      My Computer
    Quote Quote

  13. WindowsStar
    Posts : 2,737
    Windows 7 Enterprise (x64); Windows Server 2008 R2 (x64)
       New #10

    chev65 said:
    WindowsStar said:
    chev65 said:

    The Argument against Disabling IPv6
    It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
    From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
    Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.
    +1
    It just had to be said, there is more to the IPv6 protocol than meets the eye.
    Again I completely agree. Thanks for your great posts.
      My Computer
    Quote Quote

 

  Related Discussions
I want to share 3 folders to 3 computers. And I want to set different passwords to each folder so they can't see each other's files. I googled but I really can't find the working method. Here's what I tried so far: I Created a new user Ben, passworded. Computer Management > System Tools >...
Network share password problem?
in Network & Sharing

Hello all, I'm new to this forum and hoping to get a simple answer. I think I know the answer but I just want to double check. I'm having somewhat of a security issuse with shared folder. I have multiple computers setup on my LAN. On my personal computer I have a shared folder that I...
Hey there good people... I recently upgraded from windows XP to 7. The problem is I can no longer connect to my shares on the server. Windows prompts me for a username and password and once I input this info, the same prompt shows up again. I have realised the domain it uses in the prompt (for...
I want password protected sharing on because I like to log into my desktop computer and be able to access files as if I'm there. However I want to share one folder on that computer so that people who don't have username/password can still log in and share that one folder. Is this possible? My...
I can't seem to find a sleek easy way of doing this that works with windows 7. I haven't been successful with finding anything that pertains to windows 7 since most guides online are outdated. I just want to have a folder shared on my main desktop "DAN-PC" let's just give it the name...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 21:48.
Find Us