Based on the nature of the problem it is most likely an improper setting on the XP computer. To do this, follow these steps:. I had the same problem like i cant access any folder or shared printer on a xp machine from any other pcs on the network. And in the work group when its asked put the exsisting work group name. I have tried something from what i saw in this thread but didnt get through.
So after some of my own trial I found the solution. Thinking like it will be good to share here so that it may be useful to others who face same issues. The question started off "I cannot access my XP workgroup from my windows 7". Pingboy provides an answer that works!!!
And since then we have had all sorts of "other" problems thrown in here including RC, all confusing us "simple" people who simply want an answer to the question that was asked in the first place. The answer provided by Pingboy to change the regedit on the XP machine worked for me whereas all the other stuff did not. And as for Bubbapcguy, if it was THAT easy then how comes what you posted didn't work for any of us either????? In first place, sorry for my English.
I know the post is quite old, but the last entry was a few months ago. I have readed carefully all the answers and finally, for my surprise, the problem has ended. In Xp this was the default value while in Windows 7 the value was in blank, not configured. And finally this is what has worked I started one service in the XP machine. The service is "Remote access conecction manager" which description is "Create a network conecction".
Afther 3 steps I could finally access my Xp share drives from Windows 7. I hope this be to help. Have you tried setting up a Username and Password that is the same on all the computers? This is "too easy" an answer, I know, but it worked for me. I could access and read the Win7 computer from the XP units but not the other way around. By simply adding a user from control panel on each computer, that is the same on each drive, with the same password, and same permissions, this did the trick!
If you have been able to see the folders but not open them you do not have permission Once this is done, you may have to adjust permissions on the files or folders, including adding rights for the new user, if some are restricted. After unsuccessful try to access xp shared folders, error message contains terms like "permissions", "contact administrator" and "Not enough server.
This was exactly the case for me. Networking was working fine for months and I couldnt figure out what changed. Acronis TrueImage was the culprit. Full uninstall and everything is perfect again. I've been going crazy and spent hours trying to figure this out and was about to give up.
How many wives have you got? I only have one "wife" and I use my wife's laptop occasionally. It took me a full week of trial and error to find this out. It works! If not, you have 'bigger' problems than just sharing. Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows 7 Networking.
Sign in to vote. Hi, I cannot access my XP workgroup pc from my windows 7 pc. Can anyone tell me how to allow open sharing between both of the PC'S? Or how to set the permission? I have everything set to share on the network, no passwords needed, and the PC's are on the same workgroup. Friday, May 15, PM.
Follow this link and perform the registry change on the XP machine. It fixed my problem immediately after a reboot of the XP. Thursday, February 4, PM.
I can, however gain access to and from my wives laptop running Vista. You might try removing the share and adding it back again making sure to open to all users. Same problem here. Can't access the printer on my XP machine with my Win7 machine. Says I don't have permission even though the printer is set to share. You might try removing the share and adding it back again making sure to open to all users I'll give it a shot, thanks! Still no luck. Me neither, and I still cannot find anywhere in XP to change permission settings.
Expand the Local Policies branch. Select Security Options. Double-click "Network access: Sharing and security model for local accounts. Close the snap-in. Reboot the system for the change to take effect. Proposed as answer by NTauthority T. Welch Wednesday, September 15, AM. I think thats only for XP Professional users. I have XP home, and cannot access local security whatsoever.
I think Im just going to have to live with only being able to access and change files from the XP side of things. Saturday, May 16, AM. Once I formatted and loaded RC1 that all changed I could no longer click on the machine name on the network and see the shares even though they are shares for everyone.
There is something odd with respect to how the beta worked and RC1 does not. Saturday, May 16, PM. EXE file you downloaded and extract the contents to a temporary location on your hard disk. Then open the folder you extracted the files to and locate the Setup. Right click Setup. After the installation is finished, reboot your computer. Disclaimer: I have tested this procedure on my XP Home installation, and it works. I cannot guarantee that it will work on your system.
Make sure you create a System Restore point before proceeding. Deny Permissions take precedence over Allow Permissions, regardless of your group membership.
Administrators are members of the User's group, by default. Uncheck Allow, rather than using Deny. Sunday, May 17, PM. Monday, May 18, PM.
Can you try accessing it through Windows XP mode? Thursday, June 18, PM. There definitely is something screwed up with the RC version of Windows 7. I've had a network setup for years with shared printers and drives that work on every other computer in the house 3 and was working fine with the beta version of Windows 7. There is nothing wrong with the permission levels on the share so the suggestions above will not help. I don't have a solution yet but noticed the following: 1.
I get a dialog for the shares I'm unable to access asking for authentication. OK, normally I would log in using either the guest or a valid user account on the machine providing the share. However, Windows 7 RC is forcing the use of a domain that is the same as the Windows 7 machine. This certainly would seem like the cause. Listing the machines in the network, the Windows machine shows up the network. However, another XP box on the network does not show in this list.
Funny enough, I can access the shares on that XP machine after typing the net use command above. I'm not sure what I did but that machine for a while was exhibiting the same behavior as the Windows server one. Conclusions: A. There is definitely a problem with Windows 7 RC with Network shares either intentionally of otherwise. I suspect the behavior is not intentional.
It seems to be related to whether or not the Windows 7 machine views the share machine as being in the same network or not. This one is a guess. Basically, a code path used for machines belonging to a domain is in some cases some how getting called for machines that are not in a networked domain but instead belong to the same workgroup. Funny, for an OS that was suppose to make network sharing easy, I've never had problems like this and have spent all day on it. Sunday, July 5, AM. I simply don't know what's going on.
I configured two machines exactly the same with the only exception being one was running Windows Server and the other Windows xp. There is no homegroup. The shares are configured with access permission to Everyone. The fact that every other machine in my network works fine, the only conclusion that can be drawn is sharing is at least partial broken in Windows 7 RC. I've found many threads to this extent with not a single solution unfortunately.
The bottom line is this is a showstopper issue for Windows 7 RC. No matter what other improvements exist I simiply cannot use an operating that won't allow me to use resources on the network that the user is authorized to.
Too bad Sunday, July 12, PM. I agree with Scott, and been having the same problem. Can't access Windows machines with RC build Thoughts anyone? Wednesday, July 15, AM. I had the same problem but I solved it and now I can access, view and copy files between either Win 7 or XP computers. Click on Share and Win 7 does the rest. Wednesday, July 15, PM. Set ip to 15 and problems went away I doubt seriously that this is a widespread solution but I thought I would at least mention it BW.
Thursday, July 16, PM. Wednesday, July 22, PM. If I try to connect I get "remote desktop cannot connect" ensure that remote access is enabled? When I try to print it allows me to choose the printer then tells me I cannot print? So I can only assume that it is not possible. But if that is so why don't they tell us? Awesome write up here.
All the other links and help forums make it sound so easy. Anyone else figure out how to get IE working? And, that for windows XP, you are best off downloading and installing Mozilla Firefox version It should automatically upgrade you to the latest compatible version?
I can track down links and provide copies of my personal files. Just send me a message. The best way to obtain them from me is honestly probably. This site uses Akismet to reduce spam.
Learn how your comment data is processed. Related Posts Sorry, no posts were found. I could not get the driver to work but I found an easier solution, just use the bridged adapter Reply.
Best Wishes Reply. Umm… Up to step 4…. Thnks for the link Christopher. Preferable to downloading from a dodgy site: Reply. Working… thank you so much???????????????? This can result in costly security compromises, such as a worm that spreads rapidly through an internal network or a sophisticated attacker who steals confidential data across the network. Windows Firewall can filter incoming and outgoing traffic, using complex criteria to distinguish between legitimate and potentially malicious communications.
NAP requires computers to complete a health check before allowing unrestricted access to your network and facilitates resolving problems with computers that do not meet health requirements. To complete the lessons in this chapter, you should be familiar with Windows networking and be comfortable with the following tasks:.
A computer named Dcsrv1 that is a domain controller in the Nwtraders. This computer must have at least one network interface that you can connect to either the Internet or a private network.
0コメント