Tuesday, 18 February 2014

Unable to record RPD protocol on Windows Server 2008 R2

Unable to record RPD protocol on Windows Server 2008 R2


Problem Details:- I am trying to record a RDP script on a Windows Server 2008 R2 machine. It connects to the box but nothing records expect the following error message in the Recordng log.

[Network Analyzer (1088:14c4)] ------------------------------------------------------------------------------------------
[Network Analyzer (1088:14c4)] Load Network Traffic Analyzers:
[Network Analyzer (1088:14c4)] Analyzer Module: WPLUS (value=)
[Network Analyzer (1088:14c4)] Analyzer Module: RDP (value=GetRdpProtocolAnalyzer:MicRdp.dll)
[Network Analyzer (1088:14c4)] + Network Analyzer: MicRdp.dll @ GetRdpProtocolAnalyzer Loaded!
[Network Analyzer (1088:14c4)] Analyzer Module: local_server (value=)
[Network Analyzer (1088:14c4)] ------------------------------------------------------------------------------------------
[Network Analyzer (1088:1064)] Address lookup for CMF-5K8JZK1 = 3.61.128.89
[Network Analyzer (1088:14c4)] Address lookup for CMF-5K8JZK1 = 3.61.128.89
[Net An. Warning (1088:14c4)] Request Connection: Remote Server @ 0.0.0.0:3389 (Service=?) Failed attempt #1. Unable to connect to remote server: rc = -1 , le = 0)
[Net An. Warning (1088:14c4)] Request Connection: Remote Server @ 0.0.0.0:3389 (Service=?) Failed attempt #2. Unable to connect to remote server: rc = -1 , le = 0)
[Net An. Warning (1088:14c4)] Request Connection: Remote Server @ 0.0.0.0:3389 (Service=?) Failed attempt #3. Unable to connect to remote server: rc = -1 , le = 0)
[Net An. Error (1088:14c4)] Request Connection: Remote Server @ 0.0.0.0:3389 (Service=?) NOT PROXIED! (REASON: Unable to connect to remote server: rc = -1 , le = 0)

Generation log has the following:

New event: wplus_gethostbyname
New event: wplus_gethostbyname


We have no issues recording RDP against our windows 2003 servers. This is an issue since all our machines will be upgraded to Windows Sever 2008 R2.
Problem Solution:-  The first thing to be clear on this incident is that LoadRunner is not supported on Windows 2008 R2, that means that LR 11
will fail if it has been installed on the specified operative system.

The recording operation of a script in Microsoft Remote Desktop Protocol (RDP) uses the client provided by Microsoft and not all versions are supported.
Response
VuGen's recording of Microsoft Remote Desktop Protocol (RDP) uses the RDP client provided by Microsoft. The following table lists the combination of RDP client and server that are supported by VuGen up and including VuGen 11 patch 2:

Windows 2000 Server (RDP 5.0) Windows XP (RDP 5.1) Windows Server 2003 (RDP 5.2) Windows Vista (RDP 6.0) Windows Server 2008 (RDP 6.1) (*) Windows Server 2008 R2 (*) Windows 7
RDP Client 4.0 Supported Supported Supported Supported Supported Not supported (by MS) Not supported (by MS)
RDP Client 5.1 Supported Supported Supported Supported Supported Supported Supported
RDP Client 5.2 Supported Supported Supported Supported Supported Supported Supported
RDP Client 6.0 Supported Supported Supported Supported from LR 11 patch1 Supported from LR 11 patch1 Supported from LR 11 patch1 Supported from LR 11 patch1
RDP Client 6.1 Supported Supported Supported Supported from LR 11 patch1 Supported from LR 11 patch1 Supported from LR 11 patch1 Supported from LR 11 patch1
RDP Client 7.0 Not supported (by MS) Supported Supported Supported from LR 11 patch1 Supported from LR 11 patch1 Supported from LR 11 patch1 Supported from LR 11 patch1
(*) Recording on RDP client versions 6.0, 6.1, or 7.0 will fail if the remote machine is running Windows Server 2008 with terminal services.

How to check the version number of the Remote Desktop Connection?
1. To open Remote Desktop Connection, click Start, point to All programs, point to Accessories, point to Communications, and then click Remote Desktop Connection.

The Remote Desktop Connection dialog box appears.
2. Click the computer icon in the upper-left corner of the title bar, and then click About.

Additional information on RDP could be found in http://en.wikipedia.org/wiki/Remote_Desktop_Protocol

2 comments: