If you see this message the following should be done on the computer containing the shared files: 

Download the following and install it 

Windows Server 2003 Resource Kit Tools 
http://go.microsoft.com/fwlink/?LinkId=4544 

after installation is complete, click on: Start, All Programs, Windows Resource Kit Tools, Command Shell 

Then enter the following commands. (Attention: they are case sensitive.) 

net user guest /active:yes 
ntrights +r SeNetworkLogonRight -u Guest 
ntrights -r SeDenyNetworkLogonRight -u Guest 

The first command enables network access for Guest, the two subsequent ones change two different policies to allow network access for Guest.

Posted by JohnWill on the techguy.org forums

If you have a hard drive which appears to be failing DO NOT allow Windows to attempt to repair it.  In two cases, that we are aware of, this has caused data to be deleted.  Connect the drive to another system and attempt to copy as much data as you can before attempting a repair of any type.

.Net on this workstation needs to be configured with full trust to the Intranet.  This can be done through the .Net v2.0 Control Panel.

The 2.0 Control panel is not installed by the framework installer as it was with the 1.1 framework. It is only installed by the .Net 2.0 SDK, which is installed when you load Visual Studio. You can set the LocalIntranet zone to FullTrust via caspol like this (caspol is in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 or similar):

Set Intranet Zone to FullTrust

caspol -machine -chggroup 1.2 FullTrust -quiet

Set Intranet Zone back to LocalIntranet (The default)

caspol -machine -chggroup 1.2 LocalIntranet -quiet

Note: This has security implications, so use at your own risk. But if you can trust the code that will be deployable on your intranet shares, this will let it run..

As predicted, there is a way to use Windows 8 with a traditional desktop – that is, without the Metro interface. So if you don’t like Metro, you can restore the more traditional desktop and start menu.

Launch the registry editor REGEDIT and navigate to:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer.

Double-click the key RPEnabled, and change its’ value from 1 to 0 which removes Metro, the new Task Manager, Start menu and more.

Alternatively, you can set RPEnabled to 2 to remove the Metro Start screen and restore the Start menu but keep most of the other improvements.

Option may not be available in final version.

From Allan J. Smithie - http://allanjsmithie.wordpress.com/2011/10/19/how-to-restore-the-start-menu-in-windows-8/

There are some spyware infections that patch the registry so that each time you run an executable it respawns the Spyware.  These are particularly hard to get rid of as when you run the anti spyware software the Apyware application blocks access to it.  If you use this registry patch it will return the .EXE registry entry to its proper setting.

Please find it in the download section of this site.

Standard users do not have write permission to the spool directory (c:\windows\system32\spool\printers). Once I gave the Users group write permissions to this directory, UNC printing started working.

From Alan LaMielle.  Original article here - http://alan.lamielle.net/2009/09/03/windows-7-nonpaged-pool-srv-error-2017

I’m using my Windows 7 machine as a file server in addition to it being my Media Center. I’m mounting a Samba (smb) share using CIFS from my Linux server so I can synchronize files using rsync.  However, I ran into a problem after using the mounted share for a small amount of time.  I found a simple solution after a bit of research.

After running rsync for a short amount of time, I discovered that I was getting memory allocation errors related to the Windows share.  After unmounting, I attempted to remount the share and received the error:

mount error(12): Cannot allocate memory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

After checking the Event Viewer System log, I found the following error:

Source: srv
Event ID: 2017
Level: Error
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

Some research led me to find this Google Groups discussion about the problem and thisMicrosoft Technet article discussing the solution (look at the bottom of the page).  Apparently you need to tell Windows that you want to use the machine as a file server and that it should allocate resources accordingly.  Set the following registry key to ’1′:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache

and set the following registry key to ’3′:

HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size

After making these changes and restarting, I haven’t seen this issue arise again.  Fixed!