[SOLVED] Run virtual installation in windows xp desktop from laptop with wifi

[7272andy]

My guess would be the firewall (that was my initial issue), I changed the default port number and allowed it through the firewall.

[sling-shot]

Code: [Select]

00:01:39.965980 VRDP: VRDP: VD: Frames=10 MinMS=15 MaxMS=300 HistoryMS=2000 VideoMS=300
00:01:39.967179 VRDP: TCP server failed to bind to a port: 3389 [3389]
00:01:39.967244 VRDP: TCP server closed.
00:01:39.967304 VRDP: Failed to start VRDP-IN thread, rc = VERR_NET_ADDRESS_IN_USE

I have tried endless things including disabling firewall completely. Still the result is same as above. I am not sure what is that I am missing.

[pags]

Is this a WIRED <-> WIRELESS setup?  Are they on different sub-nets?  If so, there may be routing issues in one of the directions...

[sling-shot]

I have not set any subnet than the defaults.

Desktop running Windows XP is wired to router and has the virtual machine.
Laptop running PCLinuxOS is connected by wireless to the router and I want to run the virtual install in XP from laptop as if I am sitting on it.

Extension pack is installed. I have tried command line to enable vrde. I have disabled firewall. Still the same error.

Ah... Should I change back to NAT and see? Currently virtual machine is in bridged mode.

[pags]

I have not set any subnet than the defaults.

Desktop running Windows XP is wired to router and has the virtual machine.
Laptop running PCLinuxOS is connected by wireless to the router and I want to run the virtual install in XP from laptop as if I am sitting on it.

Extension pack is installed. I have tried command line to enable vrde. I have disabled firewall. Still the same error.

Ah... Should I change back to NAT and see? Currently virtual machine is in bridged mode.

No, don't change back to NAT.  That won't help anything.

Are you OK posting the IP addresses of the desktop, and laptop?  I presume they are private, non-routable (192.168.x.x, or 10.x.x.x).  If they appear to be on different sub-nets, we can look at the routing tables of each system, next.

[sling-shot]

The router is 192.168.1.1
Depending on who boots first, the others follow.
I have not checked inside the VM, but it was 192.168.1.10
There are also a couple of smartphones around accessing the router.

[pags]

The router is 192.168.1.1
Depending on who boots first, the others follow.
I have not checked inside the VM, but it was 192.168.1.10
There are also a couple of smartphones around accessing the router.

The router has a wired connection, like the desktop, so they shared the same sub-net (192.168.1.x).  I also need to see the laptops wireless IP (and, if you could, check the router's IP from there, as well).

My thinking is that the router may be acting as a firewall between the wired and wireless networks, and only letting traffic move in one direction (you may be able to get around this if your router has a DMZ).

These are currently assumptions on my part, until I get more information.

[7272andy]

Code: [Select]

00:01:39.965980 VRDP: VRDP: VD: Frames=10 MinMS=15 MaxMS=300 HistoryMS=2000 VideoMS=300
00:01:39.967179 VRDP: TCP server failed to bind to a port: 3389 [3389]
00:01:39.967244 VRDP: TCP server closed.
00:01:39.967304 VRDP: Failed to start VRDP-IN thread, rc = VERR_NET_ADDRESS_IN_USE

I have tried endless things including disabling firewall completely. Still the result is same as above. I am not sure what is that I am missing.

Port 3389 is in use and preventing VRDP from binding to it. Try changing the port to 3388 (I had to do the same thing)

Regards

[kjpetrie]

The router is 192.168.1.1
Depending on who boots first, the others follow.
I have not checked inside the VM, but it was 192.168.1.10
There are also a couple of smartphones around accessing the router.

1. You need to set your machines up with static IPs or set the router to allocate the same IP every time to each machine. You'll find it very difficult to route packets if the IP addresses aren't reliable.

2. For packaging, you don't really need a full desktop - ssh/sftp/rsync will be enough as packaging is mostly done in CLI. You can still run a single GUI application with X-forwarding, though there might be latency if the wifi is slow, so Synaptic and leafpad will still be available. If you want a full desktop over a slow connection, look at NX. It's proprietory, but it sends the desktop as JPEG images with variable amounts of compression, so you can trade image quality against speed for best results. It's in the repo. It uses ssh so you need to get that working first.

Is there a reason the VM is installed in the desktop rather than the laptop?

[sling-shot]

Port 3389 is in use and preventing VRDP from binding to it. Try changing the port to 3388 (I had to do the same thing)

Regards

I have no idea who is using it. And no idea how to change the port. There are no GUI options apparently or I am again missing it.
Could you please tell me how to do it?

[mellon]

Perhaps this link may help you a bit.
http://www.virtualbox.org/manual/ch07.html

I have no trouble in accessing direct a running Win7 guest on a linux host via KDRC using the RDP protocol and port 3389.
The manual chapter indicates that port 3389 in your case might already be in use by the host XP system preventing access to the VB guest.

Mellon

 

[sling-shot]

Thanks. It is there under Display. I will check and be back.

[sling-shot]

I just logged into PCLinuxOS on the same desktop just to test.
So the VirtualBox log from this shows :

Code: [Select]

00:00:02.008994   Oracle VM VirtualBox Extension Pack (Version: 4.2.6 r82870; VRDE Module: VBoxVRDP)
00:00:02.098794 Using XKB for keycode to scan code conversion
00:00:02.132326 VRDP: Statistics created: [full], enabled: 0.
00:00:02.143943 VRDP: VRDP: VD: Frames=10 MinMS=15 MaxMS=300 HistoryMS=2000 VideoMS=300
00:00:02.158300 VRDP: TCP server listening on port 3389.
00:00:02.161781 VRDP: Audio: rate correction mode 0x3.
00:00:02.161908 VRDE: loaded version 4 of the server.
00:00:02.161919 VRDE: [IMAGE]
00:00:02.161929 VRDE: [MOUSEPTR]
00:00:02.161937 VRDE: [SCARD]
00:00:02.161944 VRDE: [TSMFRAW]

That means it is ready for connection right?

------

Then I fired the laptop up and started rdesktop with IP address 192.168.1.2 and port 3389 and I did get an all black window. (If I had waited a bit longer I might have probably got the full desktop)

Then I started KRDC and using same numbers but additionally inputting the user name and password of the desktop user, I could see the desktop virtual instance on my laptop. Hmmmm....

But.... and it is a big one,,,, the performance is so teeth gnashing that I have completely given up on using this form EVER

-----

I shall call this thread SOLVED. Thanks everyone.