Friday, December 14, 2012 7:15 AM
We generate a incident ticket using GetNoviceUserInfo and then parsing the resulting connection string into a msrcincident file format. How should ipv6 addresses be formatted in the file? Right now we have something like this:
This obviously fails because the colons of the IPv6 adresses conflict with the IP:PORT interpretation. So how do we format it?
Friday, December 14, 2012 2:55 PMModeratorHi pichkoo,
Thank you for your inquiry about MS-RAI protocol. One of the Open specifications team member will contact you shortly.
Microsoft Windows Open specifications
- Edited by S NadendlaMicrosoft Employee, Moderator Friday, December 14, 2012 2:55 PM
Friday, December 14, 2012 7:40 PMModerator
I will investigate this and follow-up.
Saturday, December 15, 2012 10:47 AM
I may be wrong - but I think there is a new format for tickets which uses xml and works fine for IPv6.
"2.2.2 Remote Assistance Connection String 2"
<E> <A KH="YiKwWUY8Ioq5NB3wAQHSbs5kwrM=" ID="8rYm30RBW8/4dAWoUsWbFCF5jno/7jr5t NpHQc2goLbw4uuBBJvLsU02YYLlBMg5"/> <C> <T ID="1" SID="1440550163"> <L P="49749" N="2001:4898:1a:5:79e2:3356:9b22:3470"/> <L P="49751" N="172.31.250.64"/> </T> </C> </E>
Monday, December 17, 2012 4:55 AMI came across this but just dumping the connection string into a .msrincident file in this format does not work. Windows Remote Assistance expects the ticket to be in a certain format (like having LHTICKET,RCTICKET,UPLOADED, etc attributes).
Friday, December 21, 2012 5:30 AMHi guys, is there any update on this? To clarify the question I need to create RA tickets programmatically which will work in both ipv4/6 environments. I have mentioned my previous approach above where I just generate RCTICKET variable from RA Connection String 2. The RCTICKET variable does not seem to accept ipv6 addresses in any format I tried(square brackets, semicolon).
Monday, January 07, 2013 6:41 PMModerator
The Connection String 2 can include IPv6 and IPv4 addresses. The Encrypted RA Connection String 2 is hex format is transported as LHTICKET attribute of the MSRcincident file (see Product behavior notes <18> and <19>).
The format of the RA Connection String 2 is documented in Section 2.2.2.
2.2.2 Remote Assistance Connection String 2
Connection String 1 can only have IPv4 address. Connection String 1 is specific to Windows XP and Windows 2003.
2.2.1 Remote Assistance Connection String 1
6 Appendix A: Remote Assistance Invitation File Format
See description of the format and fields of MSRcincident of second type:
Following is a sample Remote Assistance Invitation File of the second type:<17>
For RA Invitation file of second type, the UPLOADDATA contains the LHTICKET and RCTICKET attributes.
The RCTICKET attribute can be present for compatibility with Windows XP and Windows 2003.
RCTICKET: The version-specific<19>Remote Assistance Connection String.
<17> Section 6: This type is specific to Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012.
<18> Section 6: In Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012, the password is mandatory and it is encrypted using the MS_ENH_RSA_AES_PROV predefined Cryptographic provider with CALG_SHA hashing and the CALG_AES_128 encryption algorithm. The cipher mode used can be CRYPT_MODE_CBC and the password used during the encryption process is a Unicode string.
Following is the password encryption flow diagram in the case of Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012:
<19> Section 6: This attribute can be present for Windows XP and Windows Server 2003 compatibility.
- Marked As Answer by Edgar A OlougounaMicrosoft Employee, Moderator Tuesday, January 08, 2013 8:49 PM
Thursday, January 10, 2013 4:38 AMRight, thanks for the help!