Venice Unleashed

Hey there,

me and my friend (sitting in same room, using same internet connection) were just trying to connect to the same server and the second joiner always kicks the first one.

We use the same public ip adress. Is this a known problem and is there any solution?

Barthock

Edith: some server don't show this behavior, maybe a server configuration problem?

Try this:

Create a new shortcut to your .exe(The one you click to start the game).
Navigate to the exe and write the following behind the path:



So, the final path might be:



Make sure you placed the quotation marks before and behind the patch, but don't include the port parameter.

Please tell me if it worked
Regards

Hey,

thanks for your reply.

Adding the -port parameter at both clients:
same problem. okay makes sense same ip:port configuration.

Adding the -port parameter at one client:
works fine.

This means the server can only handle one ip:port instance.

Now i wonder why i have this problem on my own server, but on other servers this problem doesn't exist.
Is there any possibility that the server uses different ports for clients behind the same ip?

Thanks Barthock

Barthock wrote:Hey,

thanks for your reply.

Adding the -port parameter at both clients:
same problem. okay makes sense same ip:port configuration.

Adding the -port parameter at one client:
works fine.

This means the server can only handle one ip:port instance.

Now i wonder why i have this problem on my own server, but on other servers this problem doesn't exist.
Is there any possibility that the server uses different ports for clients behind the same ip?

Thanks Barthock

Try to use another port for your server aswell.

Then your both clients and your server would be using a different port.

Okay, i will try to change the server port. Is there any recomennded default port i should use?

I got an own server. The port is set to 19567. Try that.

TheShadow wrote:I got an own server. The port is set to 19567. Try that.

My Server is configured to the same port. I tried to change the server port, but then the server doesnt accept connections.

On default port i have the problem.
Changing the -port at the clients works, but i think this is not a good solution...

I think there must be a server-sided solution, because on other servers this problem doesnt exist.

Barthock

Barthock wrote:

TheShadow wrote:I got an own server. The port is set to 19567. Try that.

My Server is configured to the same port. I tried to change the server port, but then the server doesnt accept connections.

On default port i have the problem.
Changing the -port at the clients works, but i think this is not a good solution...

I think there must be a server-sided solution, because on other servers this problem doesnt exist.

Barthock

Okay.
Since the clients are first sending out data to the master server and your server is receiving data from it in order, you´ll have to make sure, that your firewall or NAT is not blocking those ports (10000,10001,19567)

If you have to forward them, use the TCP/UDP protocol. I dont know exactly whether the server is using the UDP-protocol too, but please open it aswell to prevent any further conflicts.

Hey, thanks for your reply.

I will try some configurations and post the result later. I have to wait a bit. My server is not reachable due to maintanance at the moment.

One question:
Client use port 10000 for handshake to master server?
Or to connect to the game server? Or both?

Servers use in my case "19567" for master server handshake and later for client handshake?

I'm trying to get used to the process

In my case:
ClientOfficialIP:10000 connects to masterserver, recieves the server list.
2ndClientOfficialIP:10000 connects to masterserver, recieves the server list.

Serverlist contains the ServerOfficialIP:19567

ClientOfficialIP:10000 connects to ServerOfficialIP:19567 and etablishes a connection instance to ClientOfficialIP:10000
2ndClientOfficialIP:10000 connects to ServerOfficialIP:19567 and etablishes a connection instance to 2ndClientOfficialIP:10000

ClientOfficialIP and 2ndClientOfficialIP are the same, so the GameServer recieves the data from both clients on the same connection instance. And here is the crash?

Wouldnt it be possible, that the server only uses "19567" for the handshake and then sets another port for further communication?

Barthock

Barthock wrote:Hey, thanks for your reply.

I will try some configurations and post the result later. I have to wait a bit. My server is not reachable due to maintanance at the moment.

Barthock

The bug seems to happen on some users' computers, when me and my brother do that, it works just fine. Hmm, I will put this in my known bugs and solutions database