Windows 7 ask's "enter network password" when accessing Window XP Machine

""Finally I notices the 2 PCs running Windows 2000 that had the 'wrong' time on them were working (the time was 1 hour behind the Windows 7 PC).  The PC running Windows 2000 that DID NOT WORK had the time that matched the time on the Windows 7 PC.  I reset the PC (Windows 2000) to 1 hour behind the Windows 7 PC and now it connectes. ""

That's the real solution. Thanks

I had a similar problem with my home network, which included:

Huawei HG520b ADSL wireless router

NAS network storage drive (wired connection to the router)

Medion tower computer with Win XP (SP3) Home edition (wired connection to the router)

HP laptop computer with Win XP (SP3) Professional (wireless connection to the router).

Networking had worked perfectly for several years between the Win XP computers - and also to the SMB server on the NAS network drive.

Very recently, I purchased a Samsung laptop computer with Win 7 (SP1) 64-bit Professional.  I attempted to add the Samsung laptop to the network and discovered that I could access shared files on the Samsung computer from the XP computers

• but not vice versa.  The Win 7 computer asked repeatedly for a Network Password, every time I attempted to access files on NAS drive or on the Win XP machines.

I tried everything mentioned in the previous posts including:

a.  Turned on Network Discovery on the Win 7 computer

b.  Turned on file and printer sharing on all computers

c.  Turned on public folder sharing on the Win 7 computer

d.  Turned off password protected sharing on the Win 7 computer

e.   Disabled local account use of blank passwords to console login only (in local security policy/accounts)

f.    Set Sharing and security model for local accounts as classic (in local security policy/Network access)

g.   Synchronised that the system time and date on all machines

h.   Ran the networking wizard on the Win XP machines (again)

None of the previous posts has mentioned KB922120, which includes an important Hotfix.  The Hotfix enables Vista (and Win 7) computers to "discover" a Win XP machine.  See http://support.microsoft.com/kb/922120?wa=wsignin1.0. 

I installed the Hotfix on both of my Win XP machines.  This did enable the Win 7 computer to "discover" the Win XP machines - and included them in the network map.

Unfortunately, none of these steps provided a complete solution to the networking problem - and I never managed to access shared files on the HP Laptop or the NAS network drive - from the Win 7 computer. 

Eventually, I devised the following tortuous "workaround" on the Win 7 computer, which did allow me to access shared files on the Medion tower computer:

1.  Re-boot the Win 7 computer

2.  Disable Network Discovery on the Win 7 computer

3.  Enable Network Discovery on the Win 7 computer

4.  Open Windows Explorer, select "Network" in the list of folders, and click on View / Refresh

However, this was not a satisfactory solution.

As a last resort, I replaced the Huawei router with a TP-Link TD-W8961ND ADSL wireless router - and discovered to my amazement that networking works perfectly with the new router.  I cannot offer any a logical explanation, because I copied all of the network and firewall settings from the Huawei router to the TP-Link device.  Consequently, I would have expected the routers to operate in a similar manner.  Maybe, there are significant differences in the firmware.

However, a Google search shows that many people have experienced similar problems, with very few documented solutions.  For anyone who has been unable to establish networking between Win 7 and Win XP machines, it might  be worth experimenting with a different router.  (That is in addition to the installation of Hotfix KB922120 and the steps (a - h) mentioned above.)

This worked for my Windows8 PC as well.

Sorry, but this is just more of the (all so typical in these forums) good intentioned anecdotal information which is not based on documented information or fact.

Perhaps you get the same information because it IS fact, despite your choice to ignore it as such. You might also want to reconsider blasting non-Microsoft people who took the time to offer the responses, eh?

• Firstly, the reason I said "Sorry" to begin with is because it is not my intent to blast "non microsoft people who took the time to offer the responses" - it is Microsoft's poor response to these sorts of issues which results in all the "might work / might not work" solutions that waste all our time.   Secondly, "what is fact?".  It is simply NOT a fact that if I enter the access password of the machine which I am trying to access that I can get past this message - I have tried that.  It DOES NOT WORK.  It may have worked in your case - that's nice (in fact it's amazing) - but it is not a fact that it will neccessarily work for any one else.  (again sorry - I just get very annoyed that we all have to rely on the experience of users with specific experiences instead of getting the straight bill of goods from Microsoft.)

To my knowledge there was no documented definition by Microsoft of such a thing as a "Network Password" until Windows 7.

Because Windows 7 was a different structure with the advent of Homegroup.

• Duh.....I know that.  That's my whole point.  I don't believe that "Network Password" has any meaning outside of Windows 7, and in fact outside of homegroups, and yet many of us have been chasing our tails in pursuit of solutions which don't home in on the real source of the problem, which is Windows 7 and probably the implementation of homegroups (even if we don't use homegroups).

I can confirm that when I get the message "Enter Network Password" in a pop up window with "Network Security" showing in the ribbon banner, that no password on God's green earth (including any of the established userids and passwords for that device) will get me into the computer (or in my case a Linux based Network Attached Storage device) that I am attempting to browse.

Obviously everyone experience will be different based on the devices they are attempting to connect.  In my case, and from the information I garnered elsewhere, entering the username (and password, if applicable) from the device that one is attempting to connect to did the trick.

• Say what????

<snip>

The issue has nothing to do with a router wireless password/key <snip>

I didn't say it did.

• and I didn't say you said it did.  But others have frequently raised this red herring as the thing to check (including some support techs at Microsoft - believe it or not), so I raise it for the benefit of others to save them wasting their time chasing this wild goose.

There do seem to be a variety of "fiddling around" efforts (numerous of which are expounded upon in this and other forums) which seem to "make things work" - sometimes - on some computers - in some cases, for no logical reason.

The fiddling around often is the result of different devices with different customized adjustments being clobbered together.  Microsoft has their issues, but should we really expect them to have free answers for how every type of non-Microsoft product out there will work with their OS?

• Sorry (again) but this is absolute mumbo jumbo bologne.  What does "different devices with different customized adjustments being clobbered together" mean?  That's sort of like the mechanic telling me that the problem with my car is that the chrome muffler bearings need to be replaced.

<snip>

What prompted some programmer at Microsoft to create this pop up window occurrence, what "really" are the conditions which trigger it and what, if any, input is required to satisfy it (and possibly even - what was the programmer smoking when he coded this event).

Security, presumably.

Using the username/password allows access to our three household computers for all files, while leaving the Homegroup secure for sharing videos, shared pictures, and music with guests, without them being able to access our private documents.  So Homegroup for all household members and guests, but password protected access for just me and Hubs.

• No offense, but I wasn't posing a philosophical question.  I was suggesting that it would be useful to know what specific conditions cause this pop uup?  And of course neither you nor I know.  Only the programmer that coded it knows - maybe.

And lastly, ya know what?  I don't even care if I get an answer to what bright boy or girl created this monster - if I could only get someone to tell me what possible "password" would work I would say "OK screw it, who cares what genius thought up this nightmare - at least I can get past it".  HAS ANYONE EVER BEEN ABLE TO ENTER A PASSWORD AT THIS PROMPT WHICH IS ACCEPTED???  I have set up all the computers on my network and I (obviously) know all the passwords for all devices on the network and none of them satisfy this prompt.

Yes, which is why I spoke up in the first place to give you an answer.

To access my laptop from my desktop, I saved the laptop's login/username and password and now I can access all files in that direction.  To access my desktop files from the laptop, I saved the desktop's login/username and password and then I could access all files in that direction. I did the same in both directions for Hub's desktop as well.  Now all three computers can access any file with the other computers.

Security also works well since you can make it go in only one direction.  Say you want to screen your kid's computer, all files, but didn't want them to have access to all your files.  You'd only save the information in one direction, adding the kid's login/username and password on your computer's popup, and not give it to him/her for his/hers.

Even if this didn't help you, it might help someone else.  I was confused and kept trying to use the desktop's credentials on the desktop, when that's not what it wanted (it wants the computer's credentials you are accessing).

• I concede that what you are saying MIGHT help someone else - who knows.   However, I have set up all of my computers with my userid and password so that I can log on to any computer (or NAS) on my network with these credentials.  (Some users on my network do not have credentials on all of these computers, but I do.)  And I can confirm that I can log on to any computer (or my NAS) individually but when the "Enter Network Password" window pops up, my password is simply NOT accepted.
• The real issue is that this pop up window SHOULD NOT EVEN BE OCCURING - THERE IS NOT NEED FOR A NETWORK PASSWORD OUTSIDE OF WINDOWS 7 HOMEGROUPS!

Now off to find out why media streaming doesn't work on one device, when I've done all the steps I've been able to find everywhere.  Sigh.

• Yes, I feel your pain.  I remember the days when most of my time spent using computers was to do real work.  Now most of my time is spent simply trying to make the damn things work.