Unfortunately, this falls outside of FileCenter. Any errors and problems you see all come from Windows. But we can give you a few tips:. First, assuming that you're hosting the files on the newer machine, make sure the files aren't in your "Documents" folder. I ran into that exact problem yesterday trying to get a Windows XP Pro SP3 computer to map a drive letter to a share folder on a Windows 7 Home Premium computer so Microsoft hasn't fixed this yet.
As always make sure all computers have the same Workgroup name. It may seem like a trivial thing but a simple oversight on this will cause you big headaches so double check that each computer XP and Windows 7 all have the same Workgroup name. I've always run into a failure to see other computers in the network if the workgroup names are different so pick a Workgroup name and set it on all computers in your network.
On the computer you are sharing the hard drive you will need to add the user names and passwords to be able to auto log in from the other computer. In the Computer Management tool double click on the "Local Users and Groups" to expand it, then click on "Users" to get the current list of user names on the right.
From here you can right click on either the "Users" in the left column or right click in the empty white space on the right to get a menu that has the "Add User" choice at the top so you can create user names and passwords for them. When done don't forget to go into the "Groups" choice and add the new users to the appropriate group such as Administrators if that user needs full permissions.
If you are going to want to use the Windows 7 Home Premium computer as the server and have XP Pro workstations then you are going to be in for a rude awakening. Microsoft in their infinite wisdom This means there is no Group Policy Editor gpedit. It seams that Windows 7 should magically see the other XP Pro computers when you are "sharing" out a folder and adding the user names that are allowed access to it.
This is another "In theory this should work" issue that is causing me big problems such as not seeing the XP computer because nothing on it is being shared so the "NET VIEW" command doesn't list these computers and when typing in the username Windows 7 states that it can't find the user so it refuses to add it to the share list. That trick worked with XP Home but I don't have a computer running either of these versions of Windows 7 yet so I haven't tried it myself.
Normally after making sure the workgroup, user names, and passwords are all correct you should be able to go to "Network Places" and navigate down through "Entire Network", "Microsoft Windows Network".
You are indeed done and no hair pulling or gnashing of teeth is required. If you aren't one of the fortunate ones then network life just got a lot harder I 'm not a "fortunate one". I just went through this on when XP Pro always came back with a error even though I had everything set correctly on the Windows 7 Home Premium computer with the shared folder. Windows 7 did correctly see the XP Pro computer it had a shared printer so the XP user name was correctly added to the share list so all was good there but XP stubbornly refused to connect properly to the Windows 7 shared folder.
Again if you need help here ask and I'll provide details. One would think that after 5 versions of Windows 98, , XP, Vista, Windows 7 that this shouldn't be hard to do but the fact is that Windows has had so many programmers coding it and so many programmers have come and gone and Windows has been patched so many times that it's a wonder it works at all. To anyone reading this I'd love to hear if you have any easier and simpler ways to use Windows 7 Home Premium as a server and please no comments about why I shouldn't be using Home Premium at all as a server.
Saturday, November 28, PM. Hello Zorro, I found this after search the net for days it seemed like. I would like to ask you a few questions, which will be simple to you im sure of it :.
Is there anyway I could contact you? Sunday, January 10, PM. Thanks again, Rick. That combined with XP's new firewall and you have systems that do not see each other. Netbeui protocol was removed.
If you add it back thats part of the issue. Jbirk 3 Zinc. Well, SpeedStep is partially right but not completely correct in everything he said. Chances are you have no DHCP running on your network, but instead you likely have an ethernet switch. Chances are the XP computers are using a default Go to a Windows 98 computer and run winipcfg and look at your ethernet adapter. I am assuming you do not have DHCP and the IP address configureation is different; therefore, your computers are not seeing each other.
You probalby have a static IP on Widnows 98 computers. What you can do is match the same subnet mask and network and then set a unique host part of the IP. Do a search on subnetting. Essentially, you need to have all your computers on the same subnet, but they must have unique IP addresses. Once you set this up and can ping If you need too, you can always define teh NetBios computer names via lmhosts file.
Overall, you can share stuff without to many problems. They have taken no steps to prevent it. File Sharing doesn't work with the default firewall settings if hte firewall is enabled. If your company has more than 10 users or the company's automated resources are valuable and sensitive, you should examine the option of deploying a server running a NOS, which is our next topic. For resources to be available for a workgroup, such as folders and printers, each user must share the folders and the printers of the workgroup.
As just described, Windows makes it easy to set up workgroups. In addition, workgroups are easy to administer because each user manages the resources that they offer to the workgroup. However, they do pose problems in terms of protecting the shared resources. To date, it hasn't cornered the market and has met with increasing skeptics, including me.
0コメント