"The network path was not found" error on Win XP sp2

The problem
You are unable to connect to any network resource (network shares, printer, etc) on a Windows XP machine, from a Win XP client.

A solution (there could be several causes)

• On the target machine (the one you're trying to connect to) open up Services, under Administrative Tools in the Start Menu.
  
• Scroll down to the Computer Browser service.
  
• If it is Disabled or set to Manual, set it to Automatic.
  
• Then start it. It may stop immediately again, but this is OK.
• At this point try to connect to the target machine.
  

If it still doesn't work, you can try the following:

• open up Network Connections, under Control Panel.
• Right click on your network adapter and click on Properties.
• Click on Internet Protocol (TCP/IP), then click on Properties.
• Click on Advanced, and click on the WINS tab.
• Even if it is set to Default, set the radio button to Enable NetBIOS over TCP/IP.
• Press OK on each screen until everything's closed.
• Go back to the client machine and try again.
• You should be able to connect!

If it still doesn't work:

• Go back to the Services window and find the service named Routing and Remote Access.
• Double-click on it, set it to Manual, and stop it.
  
• Close Services and try to connect from your client machine again.

For further info on this issue, you may like to consult the following recommended books: Home Networking For Dummies (For Dummies (Computer/Tech)), Microsoft Windows XP Networking Inside Out, or Windows XP Home Networking.

If this helped you, or if you found another solution to this common and frustrating problem, please leave a comment to help others!

p.s. See here for a possible Windows 2000 solution.

Error while installing .NET Framework 3.5 Beta 1

It seems that on Windows XP SP2, if you already have .NET Framework 3.0 installed, you will get an error while trying to install the pre-release .NET 3.5 beta 1.

The installed will complain about dependencies, one of such is:

Microsoft .NET Framework 3.0SP1 WCF

You will not find this to download anywhere!

The fix!
Uninstall .NET Framework 3.0, then start the 3.5 installation process. The 3.5 installer will grab the bits of 3.0 that it needs. This will fail again BUT it will have installed the necessary prerequisites. You'll get similar DepCheck errors again.

Then, install the: Visual Studio 2005 extensions for .NET Framework 3.0 (Windows Workflow Foundation)

Now, start the 3.5 installation one more time. This time it should complete.
Restart the PC and you're done.

If you're tearing your hair out with the SSIS 'Failed to acquire connection...' error...

.. try setting the TransactionOption property on the package to NotSupported.
Your problem could be that MSDTC is either not running, incorrectly configured, or being blocked by a firewall.

This problem is common when migrating a package, which you've been working on a local dev machine, to a staging or production server. Servers commonly have tighter security restrictions than desktops or perhaps the admin hasn't even enabled MSDTC.

If you really need transactions then you'll have to delve into this issue deeper!

Here's some links to help you:
http://blogs.conchango.com/jamiethomson/archive/2005/11/02/2339.aspx
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=146&messageid=266032

etc..