Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect to server #57

Closed
kwadroke opened this issue Nov 13, 2015 · 6 comments
Closed

Unable to connect to server #57

kwadroke opened this issue Nov 13, 2015 · 6 comments

Comments

@kwadroke
Copy link

I am not able to connect to a server on the same PC or on another PC. I can see the server in the server list, but it just sits at "Connecting..."

I've compiled EE under Debian Linux using CMake for Win32 and Linux as well as under Windows 7 using CodeBlocks for Win32 with the same results. I was able to get it to build using the new Crash Logger.

When running the build under Linux for Win32, I've seen errors about not being able to bind to port 35667. Not sure if this is related.

@kwadroke
Copy link
Author

I ran netstat and the server is listening on port 35666. I built a debug version and the client reports

[INFO] ScannerServer::New server: 127.0.0.1 35666 Server
[INFO] ScannerServer::New server: 192.168.1.18 35666 Server

I don't see anything from the server console.

It seems like the server isn't acknowledging that it's getting a connection.

@kwadroke
Copy link
Author

Actually, I just found the problem or at least a problem.
It's a problem in SeriousProton, file src/multiplayer_client.cpp, line 35. status is never equal to ReadyToConnect. It's equal to 1. It should be checking for a number not text.
Commit b59b013 broke it, but technically it's been broken longer than that, it's just now the problem pops up.

@daid
Copy link
Owner

daid commented Nov 13, 2015

Actually, state is an enum, and enum have number values that match "identifier" values. ReadyToConnect however is 0, not 1. The problem is in the constructor of that code. And yes, I screwed up. But the code was not broken before.

@daid
Copy link
Owner

daid commented Nov 13, 2015

(fixed in serious proton source)

@daid daid closed this as completed Nov 13, 2015
@kwadroke
Copy link
Author

Ok. that works. All I know is I had the logger spit out the status and I only saw integers. I'm not that good with C/C++.

@daid
Copy link
Owner

daid commented Nov 13, 2015

Guess you learned something new today :-)

StarryWisdom pushed a commit to StarryWisdom/EmptyEpsilon that referenced this issue Dec 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants