Home Workgroup with Windows 2000 Pro
Windows 7, Build 7100 with home workgroup. XP computers browse and files no problem both ways. To Windows 2000 Pro, failure with Username and Password required and nothing accepted. Facts: Can ping the 2000 computer; can see and browse to the 7 computer; workgroup name is the same on all computers; username and password is the same on all computers. Something not right on the Windows 7 computer or the Windows 2000 computer?
June 8th, 2009 10:16pm

I gave up after too many hours. But in going back to Vista Home Premium 64-bit, I struggled with some of the same issues. I am going to try again with some new understandings.For XP computers to be "seen" in the network, LLTD must be installed on the XP computer, even if you have SP3 installed (LLTD was not included - big mistake). With Vista 64-bit, once LLTD was installed, everything worked well. For Windows 2000 computers, there is no LLTD. But at the suggestion of one blog, turning off the Norton firewall and turning on the Windows firewall was the trick. For both OS's, you have to make the network private, share and not require a password. One thing remains very wierd: I tried several times to set the workgroup name to something other than WORKGROUP. Didn't work. Once all the computers were set to WORKGROUP, computers appeared on the Vista 64-bit computer and access was granted to the other computers. I am hoping these tricks will work on Windows 7.
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2009 7:28pm

I'm back. Windows Vista Home Premium 64-bit installed and running perfectly. Home network with XP-Pro and Windows 2000 Pro all connected and seeing and sharing in all directions. Printers installed (on one of the Windows 2000 machines -- I know, dump the 2000). 2nd hard drive has 7 RC 7100. Home network computers with XP-Pro work perfectly, sharing and seeing without trouble after LLTD installed on XP computers. Windows 2000 computers "appear" in the lower map of network computers correctly named. But if you try to connect to either of them, you get asked for a UN and PW, and there is no way of getting around this demand. None. I have tried all the permutations believe me. From the Windows 2000 computers, the Windows 7 computer appears and the shared resources are accessible. Yes, it is a workgroup, yes sharing is set with no passwords and permissions on the 2000 computers are set to Full, Everyone. Any ideas why Windows 7 keeps insisting on a Username and Password?
June 10th, 2009 4:08am

I wouldn't be surprised if the combination of Windows 7 and Windows 2000 is simply not possible for sharing and home networking. I haven't seen anyone have success with it to date.
Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2009 6:20pm

I have the exact same problem, and I now believe Adam M MCP is correct......it's just not possible. I've spent many hours trying to get it to work but nothing does. I think it's just another way Microsoft is trying to eliminate older OS's, just like they do with device drivers on older peripherals. Go Figure.
October 11th, 2009 6:27am

Networking between 2000 Pro and win 7 works fine both ways.I have VBox 2000 pro sp4 running and win 7 on a netbook both see each other with issue.
Free Windows Admin Tool Kit Click here and download it now
October 11th, 2009 6:21pm

Hi Guys. I nearly tore my hair out over this, too. But When I got it working, it was dead simple. I'll get back to you in a few hours... got to run right now.Roger
October 13th, 2009 1:27pm

I'm assuming that you're getting the "unknown user name or bad password" message in response to a logon prompt.OK, I can't find the thread where I was posting while chasing this, but I do remember a couple of the important points:1. All the usual things, which I believe you've already covered. One thing that happened to me during my troubleshooting was that W7, for some unknown reason, reset the workgroup name back from my actual workgroup name (which is, of course, the same across all computers) to its default 'WORKGROUP'. It only happened once, but it made me paranoid about re-confirming it often.2. The date on my win2k system was off by ~ a week from the date of the W7 system (I'd been doing some other tests and forgotten to reset it). Correcting that made a subtle difference to the "unknown user name or bad password" error, and I didn't notice it at first. But I assume that your dates/times are synchronized. I have sice seen a statement that the times have to be within ~24 hours, but I don't know the truth or otherwise of that.3. IIRC, the clincher was that it is necessary, but not sufficient, to have the same usernames with the same passwords on both the w2k and W7 systems. I had to be logged in to both systems with the same username/passwords at the same time. Then when I tried to access the w2k system from the W7 (or was it the other way around? I forget.) I was once again asked for a username and password which I supplied (for what seemed like the 1000th time!), and lo and behold, it was accepted. And I have never been asked again!I have 2 win2k systems and a W7 wired to a Linksys router which also connects a Vista laptop and two XP laptops by wireless. Everyone can see and access the other without problems. Virtual machines (in VirtualBox on the W7 system) also show up and can be accessed.But it drove me crazy in the beginning.Good luck.Roger
Free Windows Admin Tool Kit Click here and download it now
October 13th, 2009 5:34pm

Thanks for the Fix this was Driving me nuts. It was the Date being off 1 day.
April 29th, 2011 12:34pm

Thanks for the Fix this was Driving me nuts. It was the Date being off 1 day. I discovered the time between my two machines was off by 25 minutes - set the time the same and viola! I can now see all the 2000 files AND map a network drive
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2011 3:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics