You are not logged in.
EDIT: SOLVED
When connecting via rdesktop-vrdp you connect to the host IP not the guest IP. This was obviously lost on me.
rdesktop-vrdp seneca:50005
--------
I'm having trouble getting VirtualBox RDP working over my LAN for some reason.
Arch Linux Host/Arch Linux Guest. Remote machine is also running Arch. Using rdesktop-vrdp. VirtualBox and the extension pack is installed on all machines.
I am using Bridged Networking.
I can successfully ssh into the Virtual Machine guest over the LAN, so network connectivity is OK.
I can successfully RDP into the guest machine from the host using the command:
rdesktop-vrdp localhost:50005
I cannot successfully RDP into the guest machine from the host using the command:
rdesktop-vrdp firefly:50005
Nor can I successfully RDP into the guest (firefly) from any machine on my LAN using the hostname (firefly) or IP address (192.168.9.130).
I'm thinking this has something to do with the port not being open?
[gregory@firefly ~]$ nmap -Pn -p 50005 192.168.9.130
Starting Nmap 6.47 ( http://nmap.org ) at 2015-03-19 17:31 EDT
Nmap scan report for firefly (192.168.9.130)
Host is up (0.000051s latency).
PORT STATE SERVICE
50005/tcp closed unknown
Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds
I'm not sure if the closed port is the issue or if there is some other quirk of VBox networking blocking my connections? Though SSH works fine on a custom port?
[gregory@firefly ~]$ sudo iptables -nvL
Chain INPUT (policy ACCEPT 112 packets, 10751 bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 67 packets, 7124 bytes)
pkts bytes target prot opt in out source destination
[gregory@firefly ~]$
Last edited by rollenwiese (2015-03-20 00:24:13)
Offline