New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Use Proxmox instead.
https://www.virtualbox.org/manual/ch08.html
i was install proxmox but same problem i cant access with rpd and proxmox windows performance bad(software raid 0)
shorter and more understandable pls?
did you even install it? You need to install the Windows via VNC, just mounting the ISO does not magically install it and open RDP....
YOur Proxmox also sucked because you had no VirtIO enabled, either in Proxmox or no driver inside the KVM.
install x2go or xrdp(no terminal cryptic bs then)/ installl virtualbox like you usually do, the machine you create for windoze will need to have the checkboxes under display settings for rdp and make sure the firewall doesnt give you burnt toast and dah you go.
i have 2x3tb hdd debian install only 1 tb but centos all space usable and i install proxmox 4 and select virtuo drivers
i install vnc and virtualbox 4.1 windows firewall off, centos iptables off but still i cant connect with rdp
You have to do port forwarding you're using NAT. If you're using an "extra ip" set the network tipe to bridge.
No, i dont use extra ip, how can i do port forward
RTFM
Lots of guide out there, search for iptables port forward. You could also use redir to forward the rdp port
redir --lport=3389 --caddr=yourvpsip --cport=3389
Fucking manual too long and i dont know need use which mode . Now i use nat mode windows connect internet but i cant connect with rdp
Now iptables close when i active iptables i cant connect vnc with centos
post the result of
iptables -L
`[root@static ~]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
`
Not sure why you can't access vnc when you enable iptables, seems it's empty with accept policy.
Server now empty i can give root access if you want.
Don't give root access to a random user on a forum lol. I'm on mobile now but later I can help you if you still haven't solved
Still same, when you're your free time send me pm
An easier way to configure a server for port forwarding etc. in cases as using proxmox or virtualbox, is installing webmin. With a GUI you can configure firewall/port forwarding and do some other useful configuration, too.
If you don't know how to properly configure, follow those simple steps:
Following same instructions, you can port other ports to the same or other vms.
Hope I hepled
Thanks for instructions but my linux command level of knowledge bad i will try
Maybe try my guide:
http://www.lowendtalk.com/discussion/21980/a-quick-guide-for-setting-up-windows-on-the-new-kimsufi-range
cheers for this, one more entry in the lazy ways to do things
@MuZo fix problems just did virtualbox gui port forward
I contacted @Uruloki on chat and now it should be solved. He wanted to access his Windows VM via RDP and so do the port forwarding.
From what I saw Virtualbox acts pretty weird: on the host there is a
vboxnet0
interface using the192.168.56.0/24
network, but the virtual machine gets a10.0.2.X
IP from the Virtualbox DHCP. The problem is that it seems that the host can't connect to the 10.0.2.X IP: ping can't reach (yes firewall was disabled in the vm) and redir fails to connect too.I found that Virtualbox has a simple way to do port forwarding integrated in the GUI under the network settings, so I just used that and it's working fine. I'm not sure how they make it work network wise. See those example images:
Source: http://www.howtogeek.com/122641/how-to-forward-ports-to-a-virtual-machine-and-use-it-as-a-server/
Obviously for RDP that would be port 3389 TCP.