I added a new computer (Windows 7) to my home network. The existing network name was "MSHome". The new computer shows up, but under the name "Workgroup". How can I change it to the old name?1 person got this answerI do too

HiLook at Windows 7 Control Panel, System.Right to Computer name. click on Change setting, Choose Change and change the Network name.http://www.ezlan.net/Win7/net_name.jpgReboot the computer. Jack-MVP Windows Networking. WWW.EZLAN.NET

Thanks, that turned out to be easy. Now the computers see each other on the network, but now I can't get it to share its hard drive. If I go to Computer, right-click on the HD, and click properties, it will not go to the Sharing tab (it will go to all other tabs). If I right-click on the HD and pick "share with" and "advanced settings", nothing happens. How can I get it to share the HD?

The computers see each other, but they can't access each other. On the new W7 computer, if I go to the HD properties and click on the Share tab, nothing happens and eventually it says "Windows Explorer not responding".The XP computer trying to access the W7 computer gets: ... is not accessible ... Access is denied. The W7 computer trying to access the XP computer gets : ... is not accessible ... not enough server storage is available to process this command I looked that up and I changed the IPStackSize to the max of 12, rebooted both, it didn't help. So any ideas of how to fix this?

HiMaybe this can Help.---------------------Win7 when configured on peer-to-peer Network has three types of Sharing configurations.HomeGroup Network = Works only between Win 7 computers. This type of configuration makes it very easy to Entry Level Users to start Network sharing. Work Network = Basically similar to the previous methods of sharing that let you control what, how, and to whom folders would be shared with. Public Sharing = Public Network (like Internet cafe) to reduce security risks. For best results log to each computer's System Screen and set all the computers to be on a Network with the same name while each computer has its own unique name.http://www.ezlan.net/Win7/net_name.jpgMake sure that the Software Firewall on each computer allows free local traffic. If you use 3rd party Firewall On, Vista/XP Native Firewall should be Off, and the active Firewall has to adjusted to your Network IP numbers on what is some time called the Trusted Zone (consult your 3rd Party Firewall instructionsGeneral example, http://www.ezlan.net/faq.html#trustedPlease Note that some 3rd party Software Firewalls keep blocking aspects of Local Traffic even it they are turned Off (disabled). If possible configure the Firewall correctly, or totally uninstall it to allow clean flow of local network traffic. If the 3rd party software is uninstalled or disables, make sure that Windows native Firewall is On .-----------------------------Networking Win 7 with other version of Windows as Work Network.In the Network Center, clicking on the Network type opens the window to the right.Choose your type of Network. Notice the check mark at the bottom, and check/uncheck it according to your needs.http://www.ezlan.net/Win7/net_type.jpgWin 7 - http://windows.microsoft.com/en-us/windows7/Networking-home-computers-running-different-versions-of-WindowsWin 7 Work Network specific folder sharing - http://www.onecomputerguy.com/windows7/windows7_sharing.htm Vista File and Printer Sharing- http://technet.microsoft.com/en-us/library/bb727037.aspx Windows XP File Sharing - http://support.microsoft.com/default.aspx?scid=kb;en-us;304040Printer Sharing XP - http://www.microsoft.com/windowsxp/using/networking/expert/honeycutt_july2.mspxWindows Native Firewall setting for Sharing XP - http://support.microsoft.com/kb/875357Windows XP patch for Sharing with Vista (Not need for XP-SP3) - http://support.microsoft.com/kb/922120 When finished with the setting of the system it is advisable to Reboot all the hardware including the Router and all computers involved.-------------If you have Permission and Security issues, check the following settings.Point to the a Folder that meant to to be share. Right click and choose properties.In the propertiesClick on the Security tab shown in the pic bellow to the right) and check that the users and their permission (shown in the pic bellow center and left) are correctly configured. Then do the same to the Permission tab.This screen shot is from Win 7, Vista's menus are similar.http://www.ezlan.net/Win7/Permission-Security.jpgIn both the Security panel, and the Permission panel you have to highlight each User/Group and examine that the Permission Controls are checked correctly.When everything is OK, Reboot the Network (Router, and computer).* Note . The Groups and Users shown in the screen-shoot are just an example. Your list will look the way your system is configured.**Note . You have to establish specific users. Everyone means all of the users that already have an account and been established as users. It does not mean Everyone that feel that they would like to login.---------------------***Note. Some of the processes described above are done Not for Windows sake but to compensate for different Routers and the way their firmware works and stores the info about the computers that are Networked. Jack-MVP Windows Networking. WWW.EZLAN.NET

I called Microsoft about this " is not accessible ... not enough server storage is available to process this command" problem. After about 5 hours on the phone (and about as many phone calls over a three-day period), talking to four support people (at least one "level 2", a manager, and then a researcher, the researcher finally determined that - contrary to the (old) online documentation - ISPStackSize in the registry can be increased to more than 12. Increasing it to 15 solved the problem. I had increased it to 12, wich the docs said was the max. If I had guess to try a higher number, I could have saved myself over 15 hours of work on the problem.I paid MS $59 up front for the support, but the manager called back and reversed it because it took so long to fix (and maybe because it was their documentation error). Most (or all) of the support people also looked at that doc too.