RDP is very slow...

[theprofessional]

I am currently using RDP 3.10. It runs pretty fast on the same segment but when I try to use it on a different segment it is extremely slow. IP-helper is setup, DHCP scope is configured correctly, but when I try to build a blade server BL25p separated by router it takes 10 minutes to TFTP the RAM WinPE image or LinuxPXE. The build completes but 5 times slower than on the local segment. I already checked, bandwidth is not an issue, negotiation is not an issue, PortFast and STP is set etc. What else could it be?

One additional thing, I notice is that on the PXE boot when DHCP gets negotiated it discovers two default gateways the x.x.x.1 virtual IP and the physical x.x.x.3 IP. Any info would be great.

[Eric van Straten]

something we've found with very slow RDP is: speed/duplex. Anytime we have it hardcoded it is slow...set it to Auto/Auto and it screams!

[Dickie Smart]

I have been happily using RDP for a few years and have moved up through the various versions using the DOS based PXE boot. I have just built a new v3.10 deployment server (which happens to be in a virtual environment but so have all the previous versions) and I cannot believe how long the WinPE boot process as it takes about 10 minutes per task each time there is a reboot.

With v2.20 (and earlier) it would take around 5 minutes for the three reboots required before the OS files are copied, it now takes the best part of an hour.

Nothing has been changed with regard to the deployment hardware, switches etc and so I am not impressed with the "upgrade" so far. The main reason for the move is to deploy x64 OS's, at the moment I think will stick with the v2.20 version for 32 bit builds.

Can anyone explain why it needs to download a "full" WinPE environment just to run a tiny script to set the h/w config / raid settings etc? I know the old 16 bit commands won't run on the new Intel G5 Proliants although fortunately the P400 controller is intelligent enough to set up a suitable raid configuration.

Or am I missing something?

[Paul_627]

Disable logging under \tools\pxe configuration\data logs and see if that helps.

You can configure the DOS boot in 3.1, search the Alteris kb for details.

[Gordon Leonard]

Is this a VM? Are you using a â bridgedâ network when you created the VM? Two GW tend to be a bad thing.

[OmarM]

Eric van Straten you are the best, setting NIC Auto/Auto and Voilà!, RDP 3.70 fast again.

[nicholas_adrian]

I am a newbie to RDP.
I have two test environments. One is using an actual physical hardware and the other is VMware workstation environment. For the actual hardware speed is not a problem but for the VMware, it takes forever, > 25 minutes, just to boot winpe.

Any trick to expedite winpe boot for VM?

Note:
- I set the network to a local subnet (VM2) only (there is no other network on it.)
- I have dual processors (Dempsey 5050 3.0Ghz 667FSB 4Mb) and 8GB RAM
- RDP was set to 2GB RAM and the target set to 1GB RAM

-Nicholas-