locked
Can't connect Windows 7 Pro to Windows 2000 server Domain. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've been surfing for an answer a few days now on "How to connect windows 7 to windows 2000 server Domain.

    > I already added the Computer Name and User on the Server.
    > I already changed the "Network security: LAN Manager authenticaion level" and "Minimum session security for NTLM SSP based (including secure RPC) Clients  and Servers."
    > I disabled the Firewall on Windows 7.

    *** I'm just a Beginner on Networking ***

    ***The weird thing is, I can see the Computers on the Network and I can Open the Shared Folders on the 2000 server, but when I open the Sub-Folder it hangs (Using Quad-Core, Windows 7 Pro and not part of the Domain). But I have another computer running in Windows 7 Pro with Core 2 Duo processor and can easily open the Folders on the Server with no problem at all. I don't know why is that happening.***

    I hope you can help me.
    Thank you.

    Tuesday, December 1, 2009 11:59 PM

Answers

  • Question
    Sign in to vote
    2
    Sign in to vote

    I know you have add the computer name and user name on the server, but you did not join the computer to the domain. Therefore if you try to access the share on the server, actually it accesses with an account of the server system. If you log on with Administrator in Windows 7, you need to set the password the same as the Administrator's password of the Windows 2000 system.

    Also you need to change the NTLM authentication level in Windows 7.

    Network security: LAN Manager authentication level

    Please change the NTLM authentication level to “Send LM & NTLM - use NTLMv2 session security if negotiated”. Please refer the following article.

    Arthur Xie - MSFT
    • Marked as answer by Arthur Xie Monday, December 14, 2009 9:53 AM
    Thursday, December 10, 2009 9:28 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I've been surfing for an answer a few days now on "How to connect windows 7 to windows 2000 server Domain.

    > I already added the Computer Name and User on the Server.
    > I already changed the "Network security: LAN Manager authenticaion level" and "Minimum session security for NTLM SSP based (including secure RPC) Clients  and Servers."
    > I disabled the Firewall on Windows 7.

    *** I'm just a Beginner on Networking ***

    ***The weird thing is, I can see the Computers on the Network and I can Open the Shared Folders on the 2000 server, but when I open the Sub-Folder it hangs (Using Quad-Core, Windows 7 Pro and not part of the Domain). But I have another computer running in Windows 7 Pro with Core 2 Duo processor and can easily open the Folders on the Server with no problem at all. I don't know why is that happening.***

    I hope you can help me.
    Thank you.


    Hi - I am having a problem connecting my windows 7 pro laptop to my Win 2000 domain as well.  I am able to log on, access the printer and the internet, but unable to access my fileserver.  I am being asked for a username and password??? 

    I tried to change the Network Security:  LAN Manager Authentication level but it is greyed out at "Send LVTMv2 response only. Refuse LM & NTLM" -- Why is it greyed out and should it be?  If not, how do I change it?  Is this option unavailable because of some Computer Group Policy in my domain controller? 

    I to am a beginner on networking . . .

    Karin
    Wednesday, December 2, 2009 3:53 AM
  • Question
    Sign in to vote
    10
    Sign in to vote

    1. Run regedit.
    2. Navigate to:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

    3. Create a DWORD value under Lsa

    LmCompatibilityLevel

    4. Set the value to 1
    5. quit regedit
    5. from Start/Run type gpupdate /force


    On Windows 2000 Server: go to start, run, type gpedit.msc and click ok.
    Under computer comfiguration, windows settings, security setting, local policies, security options.
    Look for LAN Manager Authentication Level.  Set it to SEND LM & NTLM - use NTLMv2 session security if negociated.
    Click OK.
    Then run these commands :
    secedit /refreshpolicy user_policy
    secedit /refreshpolicy machine_policy

     

    MCSE, MCSA, MCDST
    Wednesday, December 2, 2009 5:47 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I've been surfing for an answer a few days now on "How to connect windows 7 to windows 2000 server Domain.

    > I already added the Computer Name and User on the Server.
    > I already changed the "Network security: LAN Manager authenticaion level" and "Minimum session security for NTLM SSP based (including secure RPC) Clients  and Servers."
    > I disabled the Firewall on Windows 7.

    *** I'm just a Beginner on Networking ***

    ***The weird thing is, I can see the Computers on the Network and I can Open the Shared Folders on the 2000 server, but when I open the Sub-Folder it hangs (Using Quad-Core, Windows 7 Pro and not part of the Domain). But I have another computer running in Windows 7 Pro with Core 2 Duo processor and can easily open the Folders on the Server with no problem at all. I don't know why is that happening.***

    I hope you can help me.
    Thank you.


    Which credential do you use when accessing the Windows 2000 computer? After you open the Windows 2000 computer from the Windows 7 computer, please go to the Windows 2000 computer, open cmd and enter "net sessions". Please let us know the Username. I just suspect that the user does not have permission to access the subfolders.

    Additionally please let us know how did you change the NTLM authentication level.

    Arthur Xie - MSFT
    Thursday, December 3, 2009 7:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi CDOBBS,

    I tried the procedures that you gave me, but it didn't work.

    • Proposed as answer by sahZam Tuesday, September 25, 2012 1:19 PM
    Thursday, December 3, 2009 11:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    What do you mean by credentials? If I'm right about credentials, I created a User that has administrative rights. I type Net sessions and the Username is "Administrator". When I type Net sessions I saw two names "Administrator". I have another computer who's name on the Net Session is Administrator and she can access the folder. She as the same credentials as the other one (that can't access the sub-folder). The error when I access the folder "The specified folder is not accessible".

    I accessed the  NTLM Authentication level on Windows 7 Pro by going to Local Policies > Security Rights Options > then changed "Network security: LAN Manager authenticaion level" and "Minimum session security for NTLM SSP based (including secure RPC) Clients  and Servers."
    Thursday, December 3, 2009 11:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi All:

    I just installed Win7 PRO on my laptop and I also am unable to Join my win2K Domain. Has anyone solved this issue? Any help/suggestions would be very much appreciated.

    =Dave=
    Sunday, December 6, 2009 9:22 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    I know you have add the computer name and user name on the server, but you did not join the computer to the domain. Therefore if you try to access the share on the server, actually it accesses with an account of the server system. If you log on with Administrator in Windows 7, you need to set the password the same as the Administrator's password of the Windows 2000 system.

    Also you need to change the NTLM authentication level in Windows 7.

    Network security: LAN Manager authentication level

    Please change the NTLM authentication level to “Send LM & NTLM - use NTLMv2 session security if negotiated”. Please refer the following article.

    Arthur Xie - MSFT
    • Marked as answer by Arthur Xie Monday, December 14, 2009 9:53 AM
    Thursday, December 10, 2009 9:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi All:

    I just installed Win7 PRO on my laptop and I also am unable to Join my win2K Domain. Has anyone solved this issue? Any help/suggestions would be very much appreciated.

    =Dave=

    Hi Dave,

    This is a different issue. In order to aviod confusion, please create a new thread and discuss there.
    Arthur Xie - MSFT
    Thursday, December 10, 2009 9:29 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This solution worked great for me.  I was getting the message saying my password or username were invalid when trying to connect to a Windows 2000 server from a Windows 7 Pro PC.  Once I modified the registry on the Windows 7 PC and modified the settings on the Windows 2000 Server everything is working great.  Thanks for the help, this has been driving me crazy.
    Wednesday, March 31, 2010 2:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for your help . I solved my windows 7 join problem

    Tural Sarikaya

    Ankara - Turkiye

     

     

    Thursday, May 20, 2010 11:02 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I know this has already beedn resolved but I wanted to add something hoping this would save somebody some time.

    I work in a small office that is running a 2K server mainly for file and print reasons and most clients are XP Pro.

    Since I'm IT and wanted the latest and greatest I had upgraded to Win7 Ultimate (64) and never joined the domain because: 1) I have a personal printer 2) I have another box connected to a separate Dedicated DSL Line running FTP Server that I use for file storage and backup as well.

    When I first upgraded to Win7 I attempted to attache to the domain and after the a couple failures I really didn't try to troubleshoot the problem because there was really no need other than to play with it.

    Ok.. so here we are today, I have just upgraded our sales team's laptops and loaded Win7 pro whom need to be attached to the Domain and now I was forced to figured this out.. I will say it wasnt hard and here is what I did.

    1) Setup a work location and turned on file and print sharing services on each client systems.

    2) Added each Computer names to the users profile on the server.

    3)Joined the domain on each laptop and mapped the network drives and printers using my credentials (Server Admin)

    4) Rebooted & logged in using the users credentials, tested file and printing.


    I hope this helps somebody else save time.

     

    ~Z

    Thursday, July 1, 2010 6:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    OMG THANK YOU!!!!!! cdobbs, I almost craped my pants to see your instruction worked on my 3 weeks old problem.

    my desktop W7 can now share files with my W2000 server. Thank you sir, my hats off to you.

    Friday, November 5, 2010 10:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We had a very similar problem until we upgraded the server to SP4.

     

    Thursday, November 11, 2010 2:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Arthur!

    When trying to map a shared network folder I kept getting an error telling me "The specified network password is incorrect." 

    For some reason Network security: LAN Manager authentication level wasn't set to any option. I was able to map the share after setting it to "Send LM & NTLM - use NT..."

    Wednesday, December 1, 2010 7:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ok I don’t know if this is the same problem or not but I can see my windows 2000 server and access it or maybe not.  I can’t see the shared folders that are on the server, when I click on the server thru the network it opens up but that’s it….. I don’t get error or anything asking for passwords I just can’t see folders.  Now we are in the same workgroup.

    I did change my network security levels on both server and pc too, is there anything I’m missing?

     

    Thursday, April 7, 2011 2:11 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I just want to pipe in because I was having a similar problem. I was setting up a new Windows 7 computer and could not connect to the domain no matter what credentials I tried (and believe me, I was using correct credentials). The failed connections were causing user accounts to get locked. This was frustrating because I'd never had this problem with connecting Windows 7 computers to our domain before (Windows 2000 Server).

    The solution turned out to be one of those smack-yourself-in-the-head things (boy do I feel stupid). While setting up the new computer, I forgot to change the time, so the new computer's clock was an hour off from all the other computers. Once I corrected the time on the new computer, it was able to connect normally to the server/domain.

    If anyone else runs into this problem, hopefully this will help, but I still feel terribly stupid. >.<

    Friday, June 17, 2011 4:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks a lot cdobbs. This worked a charm!
    Monday, July 11, 2011 12:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That's dumb, there is already a registry DWORD named LmCompatability level with a value of 1!  I get this all the time... none of you, and I mean none of you really knows why Win 7 cannot connect to Win server 2000!  It could be patches, updates, or maybe one day it just decides to work!   It's just like the other posts on how to set up VPN... ha!  They leave out the most important part... you have to call your ISP and get a static IP address issued!  For example, you have to call Charter or Comcast and get a static IP.  They go through all the nice stuff in the server side and show how to set up VPN but they never start out with, "First of all you need to get a static IP address otherwise it won't work, or you also should get a VPN router with firewall or you system will be wide open.... and etc....."

    I was fighting with my win7 to connect to my server 2003, and you know what?  I don't even know what I did!  It just started to connect after I loaded a bunch of updates!  ... and after I find out that also have to sign with the Admin password NOT just make up a name in Active Directory and try signing in with that one...doesn't work.... have to sign in with the Admin password...

    Anyone who has ever tried to sign in with Win 7 to an older server should know this stuff!  Most of you sound like you never even tried to connect win 7 to a server, but your taking a crack at answering the post in this thread anyways...!  #fail!

     

    Some of you people either are lousy teachers or you don't know, but you have the urge to give out erroneous info!!  What are you, 16?  8?

    Saturday, August 20, 2011 11:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Run regedit.
    2. Navigate to:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

    3. Create a DWORD value under Lsa

    LmCompatibilityLevel

    4. Set the value to 1
    5. quit regedit
    5. from Start/Run type gpupdate /force


    On Windows 2000 Server: go to start, run, type gpedit.msc and click ok.
    Under computer comfiguration, windows settings, security setting, local policies, security options.
    Look for LAN Manager Authentication Level.  Set it to SEND LM & NTLM - use NTLMv2 session security if negociated.
    Click OK.
    Then run these commands :
    secedit /refreshpolicy user_policy
    secedit /refreshpolicy machine_policy

     

    MCSE, MCSA, MCDST

    this is the RIGHT way to do it, thanks. Q_D.
    Monday, October 24, 2011 12:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

     

    3. Create a DWORD value under Lsa

    LmCompatibilityLevel


    what would happen if on step #3 u create the DWORD and dont use the name in this case LmCompatibilityLevel will it work the same
    Thursday, November 3, 2011 2:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Run regedit.
    2. Navigate to:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

    3. Create a DWORD value under Lsa

    LmCompatibilityLevel

    4. Set the value to 1
    5. quit regedit
    5. from Start/Run type gpupdate /force


    On Windows 2000 Server: go to start, run, type gpedit.msc and click ok.
    Under computer comfiguration, windows settings, security setting, local policies, security options.
    Look for LAN Manager Authentication Level.  Set it to SEND LM & NTLM - use NTLMv2 session security if negociated.
    Click OK.
    Then run these commands :
    secedit /refreshpolicy user_policy
    secedit /refreshpolicy machine_policy

     

    MCSE, MCSA, MCDST
    Its work, thanks alot, cdobbs
    Monday, December 12, 2011 4:33 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi CDobbs,

     

    Your fix worked the first time! Great!

    Then, later, I noticed that the two PC's were no longer copnnected. I tried re-booting both PC, but to no avail.

    Any suggestions?

    Bill



    • Edited by oneoleguy1 Thursday, December 22, 2011 9:58 PM
    Saturday, December 17, 2011 10:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I know this has already beedn resolved but I wanted to add something hoping this would save somebody some time.

    I work in a small office that is running a 2K server mainly for file and print reasons and most clients are XP Pro.

    Since I'm IT and wanted the latest and greatest I had upgraded to Win7 Ultimate (64) and never joined the domain because: 1) I have a personal printer 2) I have another box connected to a separate Dedicated DSL Line running FTP Server that I use for file storage and backup as well.

    When I first upgraded to Win7 I attempted to attache to the domain and after the a couple failures I really didn't try to troubleshoot the problem because there was really no need other than to play with it.

    Ok.. so here we are today, I have just upgraded our sales team's laptops and loaded Win7 pro whom need to be attached to the Domain and now I was forced to figured this out.. I will say it wasnt hard and here is what I did.

    1) Setup a work location and turned on file and print sharing services on each client systems.

    2) Added each Computer names to the users profile on the server.

    3)Joined the domain on each laptop and mapped the network drives and printers using my credentials (Server Admin)

    4) Rebooted & logged in using the users credentials, tested file and printing.


    I hope this helps somebody else save time.

     

    ~Z


    Its work, thanks alot :)
    Monday, January 16, 2012 9:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I'm very low on the networking totem pole, and I was having the windows 7 -> win2000 server connection issue like the OP. I found this thread, tried cdobbs' procedure, and I'm now connected. There's no other explanation... it wasn't working literally 30 seconds before I did this and now it's working, I can see the files. Thanks VERY much for posting this...

    dw

    Tuesday, February 28, 2012 5:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    "Your computer could not be joined to the domin because the following error: The account is not autorized to log in from this station"

    Briefly: I have workstation with Windows 7 Enterprise and i can't connect it to my 2k domain. I'm joining to the domain using administrator user on the workstation and filling the administrator user and password for the domain.

    All above was done but the problem is the same. Thank you.

    • Proposed as answer by sahZam Tuesday, September 25, 2012 1:20 PM
    Wednesday, March 7, 2012 11:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    hey its realy works... thanks a lot.. thankyou once again..
    Friday, August 24, 2012 12:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi there,

     Windows 7 Laptop CAN'T connect WIN 2K server... !!! My problem is same like MStaycheva. Used Server Administrator User Name & Password as a user in Win 7.

    I have tried the steps instructed by Cdobbs and others as well. All went successful but it has not Joined to the domain. 

    Even tried as Mr. Mohammed AliKhani said above. 

    Error occurred: The account is not authorized to log in from this station.

    Any solutions???

    Thanks!!


    • Edited by sahZam Tuesday, September 25, 2012 1:30 PM
    Tuesday, September 25, 2012 1:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Run regedit.
    2. Navigate to:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

    3. Create a DWORD value under Lsa

    LmCompatibilityLevel

    4. Set the value to 1
    5. quit regedit
    5. from Start/Run type gpupdate /force


    On Windows 2000 Server: go to start, run, type gpedit.msc and click ok.
    Under computer comfiguration, windows settings, security setting, local policies, security options.
    Look for LAN Manager Authentication Level.  Set it to SEND LM & NTLM - use NTLMv2 session security if negociated.
    Click OK.
    Then run these commands :
    secedit /refreshpolicy user_policy
    secedit /refreshpolicy machine_policy

    MCSE, MCSA, MCDST
     

    cdobbs thank u worked great

    Friday, October 19, 2012 1:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks a bunch.  this worked.  Problem similiar, but was workng great untill an overnight udate came down, Then is stopped, this fixed. Using win 7 pro (64) in a Workgroup (no domain) envirment with winxps and a couple of servor 2000 sp4
    Thursday, March 14, 2013 6:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You are the man, this worked despite my skepticism.

    Realkman

    Friday, January 31, 2014 10:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    So many years later, I faced the same problem and even now I couldn't find a solution online. 

    The solution is the following:

    1.Add DNS suffix manually (Internet connection->Properties->TCPIP IPv4->Properties->Advanced->DNS->Add).

    2.Disable the IPV6 Protocol (Internet connection->Properties:  Disable TCPIP IPv6 )

    3. Restart

    Just for others that may have the same problem..




    • Edited by yiotech Thursday, March 26, 2015 9:02 AM
    Thursday, March 26, 2015 8:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello all,

    I know this subject was last replied to many years ago but i wanted to see if anyone was still looking at this. I think this might be the solution to my problem.  We have many PC's on a network running XP talking to a server running Windows 2000 which works fine. (had to be XP because of the server program which can not be updated) Now i am running a computer with Windows 7 and it was working fine and then there must have been an update and now it asks for a password when i try to access folders on the Windows 2000 server.

    I want to try the above method of running REGEDIT to see if this will allow my Windows 7 computer to access the 2000 server. But i am afraid that when i make the changes on the 2000 server it will make it stop talking to the other XP computers. Can anyone confirm that this won't happen?

    thanks so much! It's driving me crazy!

    Wednesday, December 21, 2016 5:31 PM