Ok, I solved it.
On Windows instead of using "-u" you can just leave the authentication to the
OS, using cmdkey if needed.
Here's the working command line:
wfreerdp --ignore-certificate --no-nego --pcb -t 2179
I just blogged about how to do it, including some precompiled Windows binaries
Hi guys,
I can connect perfectly to HyperV on Linux with the latest xfreerdp sources,
but I get the following error by trying to do the same on Windows with wfreerdp
compiled from the latest sources as well:
Debug console created.
connected to 192.168.1.8:2179
SSL_read: Failure in SSL library (
--On 26 September 2012 11:51:29 + Igor Shestakov
wrote:
> xfreerdp -u login --pcb -t 2179 --no-nego --ignore-certificate
> ip_address
I'm using:
xfreerdp --ignore-certificate --no-nego -u Administrator --pcb
D01C2557-9601-4127-9493-123412341234 -t 2179 10.40.0.7
You will need a bleedi
ntdeveloper ntdeveloper hotmail.com> writes:
>
>
> Hello,
> It seems connecting to hyper-v host's thr' freerdp has been fixed. I can see
> modified code in latest sources. But how do I connect to hyper-v's hosts?
> Are --pcid & --pcb both mandatory? What values should be passes to them?
>
>
devel@lists.sourceforge.net
Objet : [Freerdp-devel] Hyper-V RDP connection
Hello,
It seems connecting to hyper-v host's thr' freerdp has been fixed. I can see
modified code in latest sources. But how do I connect to hyper-v's hosts?
Are --pcid & --pcb both mandatory? What values shou
Hello,
It seems connecting to hyper-v host's thr' freerdp has been fixed. I can see
modified code in latest sources. But how do I connect to hyper-v's hosts?
Are --pcid & --pcb both mandatory? What values should be passes to them?
I tried this:
xfreerdp -u -p --pcid 0 --pcb Win7-PC
Output:
nikhil gmail.com> writes:
>
> @Lysann Kessler :
> thanks man... great job... and thanks for posting it here...
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security an
@Lysann Kessler :
thanks man... great job... and thanks for posting it here...
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how
The pull request is just the reverse operation, you are right.
Does this mean that TS_BITMAP_DATA.bitsPerPixel=16 if 15 bits per pixel were
selected for the session? oO
Regards,
Lysann
On Jul 24, 2012, at 9:41 PM, Christian Nilsson wrote:
> Hi,
> Changing that line as you propose would make -a
Hi,
Changing that line as you propose would make -a 15 not working i believe...
Please see https://github.com/FreeRDP/FreeRDP/pull/614
Regards,
Christian
On Tue, Jul 24, 2012 at 5:34 PM, Lysann Kessler <
lysann.kess...@googlemail.com> wrote:
> I got it!
>
> It's a bug in the X11 client that occu
I got it!
It's a bug in the X11 client that occurs if the preferredBitsPerPixel option
changes during the deactivation-reactivation sequence.
Upon the first successful connection the server sets preferredBitsPerPixel to
32, and the client saves this value in xf_post_connect (xfi->srcBpp =
insta
@everybody: Are there any known issues with bitmap decompression, or with
bitmap drawing in the X11 client? In this case it's 16bpp, if this makes a
difference.
Long version:
To make sure we all talk about the same packages, please see the file attached.
Let me outline the communication sequence
Yes you are right, graphics is badly distorted.
I captured few packets to look in to them. After 3-way handshaking, the first
packet that is sent from client looks good.
At least it's format is exactly the same as they have pointed out in the open
specification.
But the packet that is sent after
Hi,
please see my email from June as well:
http://sourceforge.net/mailarchive/forum.php?thread_name=51E23287-9A47-4E91-BE1B-226309A2D48F%40gmail.com&forum_name=freerdp-devel
There I listed the problems that must be tackled in order to get it working.
I also have Wireshark captures incl. SSL certi
Alessandro Pilotti pilotti.it> writes:
>
> Marc,
>
> I discovered that the Microsoft RDP ActiveX requires the attached CredSSP
settings in the registry in
> order to connect to an Hyper-V host on port 2179 for VM console access.
>
> Thanks,
>
> Alessandro
>
> Note: Save the following text i
Hi guys,
I am interested in connecting to Hyper-V VMs as well. Is there any progress on
this issue?
I already tried around a bit, made some modifications to the code and had some
success. First I tried to understand how to map the "advanced settings" of the
ActiveX RDP control to protocol beha
Marc,
I discovered that the Microsoft RDP ActiveX requires the attached CredSSP
settings in the registry in order to connect to an Hyper-V host on port 2179
for VM console access.
Thanks,
Alessandro
Note: Save the following text in a .reg file in order to import in in the
registry.
Windo
Here it is: http://dl.dropbox.com/u/9060190/vmrdp.pcap.zip
Generated with: dumpcap -f "tcp port 2179" -w vmrdp.pcap
Thanks,
Alessandro
On Apr 30, 2012, at 05:19 , Marc-André Moreau wrote:
> Do you have the pcap file? it's easier to read for me than the text output
>
> On Sun, Apr 29, 201
Do you have the pcap file? it's easier to read for me than the text output
On Sun, Apr 29, 2012 at 10:17 PM, Alessandro Pilotti wrote:
> the attachment in my previous email got removed, here's a link to the
> Wireshark capture data:
>
> http://dl.dropbox.com/u/9060190/VMRDP_packets.txt.zip
>
> A
the attachment in my previous email got removed, here's a link to the Wireshark
capture data:
http://dl.dropbox.com/u/9060190/VMRDP_packets.txt.zip
Alessandro
On Apr 30, 2012, at 05:11 , Alessandro Pilotti wrote:
> Hi Marc,
>
> please find attached the Wireshark packet captute export.
> Fi
Hi Marc,
please find attached the Wireshark packet captute export.
Filter: tcp.port == 2179
here's the .Net code that I used to generate it, wrapping mstscax.dll.
Interop assemblies assemblies generated with:
aximp %windir%\system32\mstscax.dll
The server OS is Hyper-V Server 2008 R2 SP1.
Hi Alessandro,
I'm not sure if this is fully documented in the specs, but I think it would
be very helpful if you could take a packet capture with wireshark so we can
have a sample of the connection sequence messages.
I don't think anyone has implemented it, but it does not look that hard to
impl
Hi guys,
I'd like to use FreeRDP to connect to Microsoft Hyper-V hosts for guest
management.
I'd be glad to help in developing missing features in case.
>From what I collected so far, it's a standard RDP connection on port 2179
>instead of 3389 with some additional data that needs to be passed
23 matches
Mail list logo
