User Manual, chapter 7.4.4 wrote:The "external" method provides external authentication through a special authentication library.
VirtualBox comes with two default libraries for external authentication:
In other words, the "external" method per default performs authentication with the user accounts that exist on the host system. Any user with valid authentication credentials is accepted, i.e. the username does not have to correspond to the user running the VM.
- On Linux hosts, VRDPAuth.so authenticates users against the host's PAM system.
- On Windows hosts, VRDPAuth.dll authenticates users against the host's WinLogon system.
Perryg wrote:Well no I can't but if you put the (.virtualbox folder) that has the file (VRDPAuth.dll) in your path statement on Vista it will work.
Perryg wrote:What are the guest settings for VM that you are trying to access? IE: the server port? By default it is 3389 and more than likely is in conflict with one that is already setup for MS remote.
Also you do not RDP into the VM. You VRDP into the host with the connection port. (just in case you are not familiar with it) 192.168.1.2:3390 where the 192.168.1.2 is the host IP not the guest IP.
Also after you set the path you did reboot the host machine, right?
Finally the user name and password are the user name and password for the host and not the VM. You do not need to be admin just in the user group of the host.
00:00:24.089 VRDP: New connection:
00:00:24.113 VRDP: Flags 0x00000003
00:00:24.114 VRDP: Channel: [cliprdr] . Accepted.
00:00:24.116 VRDP: Client seems to be rdesktop.
00:00:24.116 VRDP: Logon: Lain (127.0.0.1) build 2600. User: [sasquatch] Domain:  Screen: 0
00:00:24.116 VRDPAUTH: User: [sasquatch]. Domain: . Authentication type: [External]
00:00:24.116 VRDPAUTH: ConsoleVRDPServer::Authenticate: loading external authentication library 'VRDPAuth'
00:00:24.126 VRDPAUTH: Could not resolve import 'VRDPAuth2'. Error code: VERR_SYMBOL_NOT_FOUND
00:00:24.126 VRDPAUTH: Using entry point 'VRDPAuth'.
00:00:27.707 VRDPAUTH: external authentication module returned 'access denied'
00:00:27.707 VRDPAUTH: Access denied.
00:00:27.708 VRDP: Connection closed:
00:00:27.708 VRDP: Logoff: Lain (127.0.0.1) build 2600. User: [sasquatch] Domain:  Reason 0x0001.
00:00:56.317 VRDP: New connection:
00:00:56.335 VRDP: Flags 0x00000003
00:00:56.336 VRDP: Channel: [cliprdr] . Accepted.
00:00:56.338 VRDP: Client seems to be rdesktop.
00:00:56.339 VRDP: Logon: Lain (127.0.0.1) build 2600. User: [sasquatch] Domain:  Screen: 0
00:00:56.340 VRDPAUTH: User: [sasquatch]. Domain: . Authentication type: [External]
00:00:56.418 VRDPAUTH: external authentication module returned 'access granted'
00:00:56.418 VRDPAUTH: Access granted.
00:00:56.419 VBVA: VRDP acceleration has been requested.
00:01:08.149 VRDP: Received the Disconnect Request packet.
00:01:08.149 VRDP: Connection closed:
00:01:08.149 VRDP: Logoff: Lain (127.0.0.1) build 2600. User: [sasquatch] Domain:  Reason 0x0001.
00:01:08.149 VRDP: TCP server failed to send data to the client!!! Disconnecting the client.
00:01:08.149 VBVA: VRDP acceleration has been disabled.
00:01:11.960 VRDP: New connection:
00:01:11.975 VRDP: Flags 0x00000003
00:01:11.976 VRDP: Channel: [cliprdr] . Accepted.
00:01:11.979 VRDP: Client seems to be rdesktop.
00:01:11.979 VRDP: Logon: Lain (127.0.0.1) build 2600. User: [sasquatch] Domain:  Screen: 0
00:01:11.980 VRDPAUTH: User: [sasquatch]. Domain: . Authentication type: [External]
00:01:15.205 VRDPAUTH: external authentication module returned 'access denied'
00:01:15.205 VRDPAUTH: Access denied.
00:01:15.205 VRDP: Connection closed:
00:01:15.205 VRDP: Logoff: Lain (127.0.0.1) build 2600. User: [sasquatch] Domain:  Reason 0x0001.
Sasquatch wrote:I just tested the external on my Linux Host, with a Windows XP VM and it works just fine. I used the following command to connect to the VM:
I use the supplied vrdp rdesktop version from VB, but the normal rdesktop would work just as well. The '-u' is for the user name, the '-p -' is to ask for my password before the connection is made. On Windows Hosts, you have the same kind of options. This is what I get in my VM log. Note that the first and last tries were without the explicit password or username for the connection:
Sasquatch wrote:So you have also tried to connect to the VRDP server with already filled in username and password? From my tests, if either one is missing, the connection will be refused.
Sasquatch wrote:Well, I just tested it with two VMs, one with VRDP enabled, the other playing the RDP client. Both were Windows XP, and because my host is Linux, I don't have port 3389 in use so that's ruled out of the equation. Now, when I tried to connect to my Host for the VRDP, it never asked for my username and password, but instead gave me two errors. Attached are the two errors I got, the last one is really strange because neither side has run out of memory (VMs have 512, and about 100 MB in use, Host has 3 GB of RAM, with more than 2 left).
Users browsing this forum: mpack and 47 guests