A little something about everything

This problem can occur two way, one is cause by the server not updateing your gateway routers arp tables. You can solve this problem by logging into your router and clearing the arp tables. for instace, on a cisco router your would do the following:

using serial or hyperterminal if available

• connect to your router
• password: (enter password)
• router> enable
• password: (enter password)
• router# clear arp
• router# write mem
• router# exit

done.

The other problem is caused when using Network Load Balancing (NLB) on windows 2008 / 2008 R2 Server

For more information on this issue use these links:

http://support.microsoft.com/kb/960916

http://blogs.technet.com/b/networking/archive/2009/01/15/unable-to-connect-to-windows-server-2008-nlb-virtual-ip-address-from-hosts-in-different-subnets-when-nlb-is-in-multicast-mode.aspx

solution:

add the following to you web.config file:

<system.webServer>

    <security>

            <requestFiltering allowDoubleEscaping="true" />

    </security>

</system.webServer>

App Pool setting:

• LoadUserProfile = true

File permissions:

• use "IIS AppPool\DefaultAppPool"

Install Xrdp on CentOS 5.4

• yum install make.x86_64
• yum install gcc.x86_64
• yum install pam-devel.x86_64
• yum install openssl-devel.x86_64
• Download Xrdp
  • xrdp-0.4.1
• Install Xrdp
  • go to /xrdp directory in terminal
  • make
  • make install
• Start Service
  • cd /usr/local/xrdp
  • ./xrdp_control.sh start

Install the old version of Microsoft RDP on a windows XP system or just search and copy from any pre SP3 windows xp install these two files and place them in a folder.

• mstsc.exe
• mstscax.dll

launch mstsc.exe and connect to your Xrdp server.

There seems to be a problem when installing SQL server 2008 on a windows 2008 RC2 platform.  Generally it will get stuck, hangs at "Install_sql_is_Cpu65_Action:Write_NativeImage_64" or another place about 3/4 the way through the install process. In some cases this may be a permissions issue and others media read/write issue.

Best solution for this is to copy the entire contents of the install media directly to the HDD and run the installer directly from the hard drive as the administrator directly from console and not from RDP. This seems to solve the problem in all cases so far.