wine utv udp socket

[runko]

I will try that, with the local host ip as you instructed. Something unrelated is preventing me from logging in to my server, so I can't do that just yet.

I wanted to mention, though, something perhaps related to this. When I did that before, (i did it with my external IP), I got some messages indicating that a window was trying to be spawned, (X11), but was unsuccessful in the attempt, (because this computer does not have a display). I had to get xvfb (a virtualized display, see wikipedia). The reason I mention this is because, I want to check if you have a similar experience. Using wine just regular wine command, does not have this issue, but I'm assuming there is some other problem with this, because you mention using wineconsole in the guide.

[Ragnos.UTzone]

if you use the "wine"-command, it does not check if there is a Desktop Environment or even a x-server, it just does what it would do on windows. And on windows, the cmd-window containing your UTV-server would pop up. wineconsole doesn't do this, exactly for applications like servers.

I didn't read the whole thread to be honest, but your utv should run fine, using the commandline provided by jeppo. Please note that this line should be issued from the inside of the utv\System-folder, or you use absolute paths to your files. (e.g. Z:\home\user\bla) Also you should change the multihome-ip to your actual ip, at least if you want to reach your server from other clients.

[jeppo.UTzone]

The utv servers from UTzone run on root servers without displays only with ssh acess.

Try the cmd i post when its run with 127.0.0.1 and not with your ip than you have maybe

a firewall problem (ports closed)

or the user that run the server has no rights to open the port

or an orher process has the port open

[runko]

Zitat von Ragnos

if you use the "wine"-command, it does not check if there is a Desktop Environment or even a x-server, it just does what it would do on windows. And on windows, the cmd-window containing your UTV-server would pop up. wineconsole doesn't do this, exactly for applications like servers.

Yes, I was thinking the same thing. That's why I thought it was unusual that using wineconsole was giving me errors related to trying to launch a window. It still doing so actually, despite what is written below, (that appears to be a separate issue).

Jeppo, thanks! I don't get this error when trying to use 127.0.0.1. However, I thought that I have already set up my firewall by opening up the what I believe to be the correct ports. I had opened 28902 and 7777<->7787 for inbound. Also, I can run a normal ut2004 server without issue, people can connect. I will look more in depth about this.. I don't think the user doesn't have the rights (using sudo command), and I think no other application is using the port.

[runko]

Hm, it seems i should have put in my private IP instead of my public IP, which is redirected to my private ip, which I got from ifconfig. It appears to be working now.

Here's another question, , I see sometimes people are putting the utv in a loop, do you know why, does this need to be done?

#!/bin/bash
echo "UTV Server Starting up"
while true
do
echo "To exit loop hit CTRL-C"
echo "Starting Server"
wineconsole --backend=curses UCC.exe utv inifile=utv.ini log=utv.log
echo "Server Exited To exit loop hit CTRL-C"
sleep 5
echo "Loop Restarting now"
done

thanks again for your help =)

[Wormbo]

That's just a convenience script to automatically start the UTV proxy again when it was shut down or crashed. You should only do that once you got it to run the way you want.