I am setting up a new win7 pro machine (machine name: daffy). It is on a home network (workgroup called WORKGROUP) with an XP machine and two win2kPro machines. (One of the win2k machines is called bugs; it's sitting right here, so it's convenient for experiments.) I can see the XP machine (called lenovo) with no problems, but I cannot connect to the win2k machines. Specifically, under the network tab, I can see the names of the machines. When I select the XP machine called lenovo, I'm in. But when I select bugs or the other win2k machine, I get a pop-up asking for credentials. Ok, that's fine, just what I would expect. However, it seems to want a domain. I try bugs\userid, which does not work. I try workgroup\userid, which does not work. I try \userid (which by the display actually does remove the domain), and that doesn't work either. What's interesting is that from bugs and the other win2k machine, I can connect to the shared files on this win7 machine daffy with no problem. I have network discovery and sharing and all of those things turned on (they were turned on by default already). I tried enabling 40/56 bit encryption rather than 128, just in case, but it didn't make any difference. I turned off password protected sharing, which also seems like a feature that points in the wrong direction (problem is that I can't see them, not that they can't see me). I have re-booted all these machines several times, reset the router to re-establish IP addresses. Any wisdom?

There is no centralized user database in a workgroup, so workgroup\username is meaningless (but it will work in a domain which does have a centralized user database). In a workgroup you must specify the workstation name then enter a username and password which is valid for that workstation. When you used the bugs\user option, are you sure that you specified a username and password which is valid on the machine bugs? Bill

Hi 86dave, I haven't worked with Win2k in while. I found this word document, that shows the sharing configuration method for W2k. You may have to add daffy (network, computer name) to the permissions in the sharing on bugs. Hope that helps.

I did, Bill, and more than once, just to be sure. I'll print out and study the word document from nano warp (can't print it at home: the printer is on a machine I can't connect to!). Thanks, Dave

Hi, Please also try the following on the Windows 7 computer: 1. Click the Start Button, type "gpedit.msc" (without quotation marks) and click OK. 2. In the "Group Policy" window, double click on "Windows Settings" under "Computer Configuration". 3. Double click on "Security Settings"-> "Local Policies"-> "Security Options" 4. In the right panel, double click on the "Network Security: LAN Manager authentication level", please select "Send LM & NTLM Responses". 5. Click Apply and OK. Then reboot the computer and see if you can access the share folder on the Windows 2000 computer from the Windows 7 computer with UNC UNC (\\computer\folder or \\IP Address\folder). Hope this helps. Thanks. Nicholas Li - MSFT

Thank you, Nicholas Li ! That seems to be the secret: everything looks great now. Dave

Hi Dave, Thank you for your update. I am glad to know it works. Your time and efforts are highly appreciated. In the future, if you experience any issues regarding our products, you are welcome to post a new thread in our forum. It is always our pleasure to be of assistance. Thanks again. Have a nice day!Nicholas Li - MSFT

I have this same problem "hand shaking" between Win7 and Win2k. The difference with the problem that I'm experiencing is that I'm using Win7 HOME edition and it doesn't have gpedit.ms. Is there another way to get into the Security Options on this version of Windows 7?

I have this same problem "hand shaking" between Win7 and Win2k. The difference with the problem that I'm experiencing is that I'm using Win7 HOME edition and it doesn't have gpedit.ms. Is there another way to get into the Security Options on this version of Windows 7? are you typing .msc? gpedit.msc in the search box. try typing \\computer name\ does it find the W2K computer?

Thank You for your quick reply! Yes, I am typing in .msc....that was a typo on my original question. I am not where I can get on the Windows 7 computer right now, but I could see the Win2k computer on the Network Places. When I try to access it, I get the prompt for the user-id (which is filled in with the Win7 User-Id <??>) with a blank password bar. As with others who have indicated this problem, no known passwords are accepted. I think I mentioned that I am working with Windows 7 Home Edition. I have seen other "resolutions" such as the one provided here that says that you need the Premium edition or the Ultimate edition to have access to the GPEDIT.MSC program and the SECPOL.MSC program I wonder if REGEDIT is included with the Home Edition and if so, if I could find the correct registry entries through it? I found this in Windows XP registery. One of those two entries might work, but better yet, if I can get down to that level with regedit on Win7, I might see exactly corresponding entries as options as given in the resolution above. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SeCEdit\Reg Values\MACHINE/System/CurrentControlSet/Control/Lsa/LmCompatibilityLevel 0|Send LM & NTLM responses 1|Send LM & NTLM - use NTLMv2 session security if negotiated 2|Send NTLM response only 3|Send NTLMv2 response only 4|Send NTLMv2 response only\refuse LM 5|Send NTLMv2 response only\refuse LM & NTLM

Hi Mike, Type in your user name and password for the W2K computer or target computer that you are trying to access when you get that prompt. It seems to be working ok if you get that prompt and see it in network. It is just configured for password protected access\sharing. From one of my earlier posts, this Word .doc may assist you in configuring the sharing on the W2K computer, not as friendly as XP, Vista, or Win7. http://www.microsoft.com/downloads/details.aspx?FamilyID=87c0a6db-aef8-4bef-925e-7ac9be791028&DisplayLang=en Work your way from the W2K, than XP and so on.

I have the same problem with Windows7 Home edition. I added the following to the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa new DoubleWord(32-bit value) LmCompatibilityLevel 0 Make sure your Win2K machine has this value set too. I am now able to access windows 2000 Pro shares from my windows7 Home machine. The Microsoft "GEEKS" have a way of changing things unannounced, causing grief to their customers. I have spent many hours trying to resolve this problem. Apparently Microsoft would rather have you buy Windows7 Pro or Ultimate just to fix this problem which they have caused.