RemoteAPP

I’ve found this link that explains how to make RemoteApp working over Windows XP, Vista or 7.

Thanks to Aaron Parker

Connecting to a W2008 shared folder from W2000 or XP clients

Recently I've tried to connect to a W2008 shared folder from a W2000 server without success, however I've found this information at http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm and now it's working fine. This applies to windows XP clients too.

How to Disable SMB 2.0 on Windows Vista/2008

Server Message Blocks Protocol (SMB) is the file sharing protocol used by default on Windows-based computers. SMB 1.0 was designed for early Windows network operating systems such as Microsoft LAN Manager and Windows for Workgroups, but until Windows Server 2008 and Vista, all Microsoft-based operating systems continued to use it more or less in its original format.
SMB 2.0 was introduced in Windows Vista and Windows Server 2008. SMB 2.0 is designed for the needs of the next generation of file servers. Windows Server 2008 and Windows Vista support both SMB 1.0 and SMB 2.0 in order to preserve backward compatibility.
Some of the enhancements in SMB 2.0, include:

• Sending multiple SMB commands in the same packet which reduces the number of packets sent between a client and server
• Larger buffer sizes
• Increased scalability, including an increase in the number of concurrent open file handles on the server and the number of shares that a server can share out
• Support for Durable Handles that can withstand short network problems
• Support of Symbolic Links

Testing done with copying large files between Windows Vista and Windows Server 2008, and then Vista to Windows 2003, have shown that by using SMB 2.0 the file copying was, in average, 2 times faster than with older operating systems.
However, while SMB 2.0 seems to do a good job if BOTH client and server OSs support it, in some cases it will slow things down. The reason for this is that the version of SMB used for file sharing is determined during the SMB session negotiation. If both the client and server support SMB 2.0, then SMB 2.0 is selected during the initial negotiation. However, if they don't both support it, SMB 1.0 will be used to in order to preserve backwards compatibility.
The SMB protocol version to be used for file operations is decided during the negotiation phase. During the negotiation phase, a Windows Vista client advertises to the server that it can understand the new SMB 2.0 protocol. If the server (Windows Server 2008 or otherwise) understands SMB 2.0, then SMB 2.0 is chosen for subsequent communication. Otherwise the client and server use SMB 1.0.
When using the terms "client" and "server" in case of file and print sharing, it does not necessarily mean that a client-type OS such as Vista "always" connects to a server-type Os such as Windows Server 2008. Sometimes, a Vista computer will connect to another Vista computer, and in that case, the computer that is "serving" the shares is considered to be the "server".
Here's how SMB is used when related to SMB versions:

• When a Windows Server 2008/Vista "client" connects to a Windows Server 2008/Vista "server", SMB 2.0 is used.
• When a Windows Server 2008/Vista "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.
• When a Windows 2000/XP/2003 "client" connects to a Windows Server 2008/Vista "server", SMB 1.0 is used.
• When a Windows 2000/XP/2003 "client" connects to a Windows 2000/XP/2003 "server", SMB 1.0 is used.

So, for troubleshooting purposes, mostly in an environment that has mixes operating systems, you might want to consider disabling SMB 2.0. So you need to do on both the "client" and the "server" operating systems. To disable SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the "client" systems run the following commands:

sc config lanmanworkstation depend= bowser/mrxsmb10/nsi

sc config mrxsmb20 start= disabled

Note there's an extra " " (space) after the "=" sign.
To enable back SMB 2.0 for Windows Vista or Windows Server 2008 systems that are the "client" systems run the following commands:

sc config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi

sc config mrxsmb20 start= auto

Again, note there's an extra " " (space) after the "=" sign.
In order to disable SMB 2.0 on the server-side computer, follow these steps:
Warning!
This document contains instructions for editing the registry. If you make any error while editing the registry, you can potentially cause Windows to fail or be unable to boot, requiring you to reinstall Windows. Edit the registry at your own risk. Always back up the registry before making any changes. If you do not feel comfortable editing the registry, please do not attempt these instructions. Instead, seek the help of a trained computer specialist.

1. Run "regedit" on Windows Server 2008 based computer.
2. Expand and locate the sub tree as follows.
   HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters
3. Add a new REG_DWORD key with the name of "Smb2" (without quotation mark)
   Value name: Smb2
   Value type: REG_DWORD
   0 = disabled
   1 = enabled
4. Set the value to 0 to disable SMB 2.0, or set it to 1 to re-enable SMB 2.0.
5. Reboot the server.

Error connecting to 127.0.0.2 in XP SP2

Symptoms

With Windows XP SP2 some applications which connect to the loop back address range may not function as expected.

Cause
Windows XP SP2 prevents connections to the loop back address range for any address other than 127.0.0.1.

Resolution
Microsoft support has an update available which addresses this issue and is available for downloading at: KB884020

The fix contains the following file info:
13-Aug-2004 22:50 5.1.2600.2505 359,040 Tcpip.sys

This update helps resolve an issue on computers running Windows XP Service Pack 2. Programs that connect to IP addresses in the loopback address range may not work as expected and you may receive an error message indicating you cannot establish a connection. After you install this item, you may have to restart your computer.

No aparece "enviar a:" desde documentos de Office.

Para corregir este error hay que editar el archivo win.ini y si falta alguna de las siguientes líneas, entonces añadirla.

[Mail]
MAPI=1
CMC=1
CMCDLLNAME=mapi.dll
CMCDLLNAME32=mapi32.dll
MAPIX=1
MAPIXVER=1.0.0.1
OLEMessaging=1