06. Oktober 2008 um 09:30 · Abgelegt unter Allgemein
JA! Es ist soweit – Crysis Wars hat findige Server Admins hervorgebracht, die via VirtualMachine (effizient) den Crysis Windows Server emulieren. Da “wine” als Generallösung für Win-Applikationen nicht funktionierte, hat sich der mycrysis.com User TRAB hingesetzt, und ein englisches Tuturial für Debian geschrieben:
Das Tutorial (eng)
Großes Tennis :) Wenn’s auch simpel ist – aber die Community wartet ja schon ewig…
Update:
Nachdem auch ich meine VirtualBox auf openSuse 10.2 eingerichtet habe, werde ich kurzerhand meine Erfahrungen nochmal Kund tun:
Ich bin von der OpenSource Lösung der VirtualBox sehr beeindruckt. Nicht nur, dass diese sehr stabil läuft, sie performt auch bei Gameservern außergewöhnlich gut. Ich habe den Thread von TRAB ein bisschen komplettiert, damit auch andere in den Genuss von VBox kommen können. Hier ein copy/paste:
You should add the NAT forwards to the tutorial:
| quote: |
- Stop the VBox (kill VRDP or whatever… adding NAT forwards only work with stopped box)
#> VBoxManage setextradata winxp “VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestcw/Protocol” UDP
#> VBoxManage setextradata winxp “VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestcw/HostPort” 64100
#> VBoxManage setextradata winxp “VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestcw/GuestPort” 64100
– Start Box
– Disable Firewall
– Start CW Server
|
If you have trouble getting vbox working on SuSE (mine is openSuse 10.2), just PM me.
Some extra hint for all of you, who never touched a vbox.
| quote: |
| #> VBoxHeadless -startvm winxp -vrdp=on -p 3389 &
|
that is not quite useful when you’re logged in at the shell because you need to have to hold the shell opened to run the server and vrdp. so try this one:
| quote: |
| #> screen -dmS vbox VBoxHeadless -startvm winxp -vrdp=on -p 3389
|
This will add a screen called “vbox” in the background (as daemon). Now whenever you want to shutdown the vbox (if not wanted via windows shutdown – later needed!), then do this:
Press and hold: Ctrl + A + D
This will detach and kill the daemon, and the vbox will shutdown.
Once you have configured your vbox a bit, you can get to the point of authentication. The normal vrdp will NOT (!) authenticate. Everybody can have access to your vbox via rdp! To fix this you can use the vbox external authentication (which is quite difficult to handle) OR you can just forward RDP to the vbox and use the windows authentication.
To do so you need to change the vrdp port first (vbox shutdown first!):
| quote: |
| #> VBoxManage modifyvm -vrdpport 4000
|
So this tells the vbox, that it won’t go over the standard rdp port anymore – so the windows rdp port is free to use! Fire up your vbox again:
| quote: |
| #> screen -dmS vbox VBoxHeadless -startvm winxp -vrdp=on
|
Now connect over rdp via IP:4000
When ya in the vbox again, enable Windows RDP:
Go Control -> System -> Remote and tick on both available options. Then give yourself a password at Control -> User Center (or whatever it’s called in english ^^). Without your user having a password, the system over RDP won’t give you access to the Machine for obvious security reasons. After that you gonna edit the registry for autologon:
Press Windows Key + R and enter “regedit”. Now go to this tree:
| quote: |
| HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
|
Add the following (String) keys:
| quote: |
“DefaultUserName”=”YourUsername”
“DefaultPassword”=”ThePasswordYouHaveSet”
“AutoAdminLogon”=”1″
|
Then reboot and see, if the autlogin works.
If it worked – shutdown windows. Make sure the box is down by entering
It should the ya, that no screen exists.
Now go to your linux shell and enter the NAT Port Forward Commands for RDP:
| quote: |
#> VBoxManage setextradata winxp “VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestrdp/Protocol” TCP
#> VBoxManage setextradata winxp “VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestrdp/HostPort” 3389
#> VBoxManage setextradata winxp “VBoxInternal/Devices/pcnet/0/LUN#0/Config/guestrdp/GuestPort” 3389
|
If ya done that, fireup the vbox again WITHOUT VRDP:
| quote: |
| #> screen -dmS vbox VBoxHeadless -startvm winxp -vrdp=off
|
Wait a minute – seriously – the RDP won’t work instantly since WinXP has to boot up first.
After this waiting time you can just connect to the server via IP:3389 (you can leave out the 3389).
Regards,
xsign