I just bought the game today and for the life of me I can't get the dedicated server to work. Every time I try to connect, I get "Connection failed. IP address may be wrong or blocked or game is full."
Here's what I tried so far:
Tweaked text8.dat file to try different ports and specifying both local and remote IPs
Disabled windows firewall on server and temporarily set to DMZ on router after simple port forwarding didn't work.
Tried both Steam and stand-alone version.
Installed Tunngle on both the client and server to try to avoid any other firewall issues.
I can ping the server and was even able to connect to a minecraft server via Tunngle so I know the link works.
Is your server on the same LAN you area or outside on a separate internet connection? Is the server on the same system you are running the client on, or on a different system on the same network?
If you are hosting locally over your LAN, you would just need to use the LAN IP address (not the external internet IP address) for the system running the server. Same is true if you are running both on the same system. If you are running the server externally over the internet on a separate connection, then the outside system needs to be set to accept inbound client connections on the specified ports, which need to be open and forwarded to the system.
Once configured correctly and the correct IP used (LAN or internet) for the client, it should connect correctly.
Full disclosure: I'm actually a network administrator by trade. I've tried everything short of using wireshark to figure out where the connection fails.
As long as the server and client are able to bind to their respective devices, it should be successful, so I'm not sure why it wouldn't other than something being blocked or not forwarded where needed along the way. Perhaps there are other restrictions along the way that prevent the handshake process for connecting. I can say the even if the TCP side of things is able to connect, you'll get an error message about no response from the UDP side. So it sounds like not even the initial TCP side of things is being allowed to communicate.
Found some new information that may be of use here.
I just was able to host on my own PC (Win 8.1) but with the same settings cannot host on the server PC (Win 10)
When I did a netstat -a on my own PC, it shows the port in question as "LISTENING"
netstat -a on the win 10 PC while the dedicated server is running does NOT show the port as "LISTENING" it's missing no matter what port I change it to in the server config.
I tried running the server as admin, compatibility settings in windows and made sure it wasn't windows firewall. It seems the server process is just not binding to the NIC at all even if I use 0.0.0.0 as a local IP.
Couldn't find it in a quick browse. If you send me a zipped msinfo report, that might help. Although it probably wouldn't change, do you get any different result when using the 2D server program vs the 3D server program? Does the server program automatically detect and fill in a local IP address at all? And if so, does that address line up with the correct LAN IP for the device that you are trying to bind a connection to?
I can provide some details on what the software is doing, which may help pin down where the problem is. When it starts, the program polls the available network devices as they should be registered and listed in Windows. The top one listed is the one that the program attempts to retrieve a LAN IP for. Since the program is displaying a blank entry, that suggests either the network device list is empty and/or Windows reported back to the program that no LAN IP had been assigned to it. So if nothing is displayed there, that's an indication that the program won't be able to connect to a/the network device at all anyway.
Many years ago, I recall someone having difficulty getting their network device to work due to a 3rd party application that displaced their main network device and substituted its own 'virtual' device in its place. This caused Windows to treat the virtual device as the main network device, even though it didn't operate as a standard network device. Once the device list was setup with the actual network device, it worked as expected. Not sure if that might be a similar scenario, but with all of the networks devices is the adaptor list and associated order list/settings, it might be worth checking into.
With the right driver and DirectX installed, I would guess that system would still be able to launch the 3D enabled server program with the Intel HD graphics. I doubt it would make a difference for this network issue though.
If the server program can pick up a LAN IP for a network device and display it in the menu, then it will likely be able to connect and run as normal. So if you can get that far, the rest should work successfully.
I've tried disabling all interfaces besides the main Ethernet but it still won't "grab" an address when I run the server.
I don't suppose there's any kind of debug logging where I could see what it's doing?
The only interfaces left are the Microsoft built-in ones, ISATAP and Toredo. I disable those and they come right back when I reboot.
Microsoft, in all their wisdom, decided to remove the ability to "re-order" network interfaces in the advanced settings. I reduced the interface metric for TCP/IP IPv4 but it still doesn't make a difference.
Are you able to manually retrieve the exact LAN IP's for the network devices on the system? If so, and if there is more than one, what happens when you try to manually type in those IP addresses and have the server program connect to them?
If the server program runs into a problem, it will provide a popup with details. But if the network device list returns 0 or if a device can't be connected to, the program will just display no IP or a connection failed message respectively.
Yeah, why they removed that (along with removing and/or moving other things) hasn't helped make Windows 10 better for sure.
Although I don't think it will ultimately help, if you contact me with your e-mail address, I'll set some time aside to put together a custom build of the server program that will output some numerical data when it attempts to try and connect to the device. I suspect all it will tell us is that the device is not available, but with nothing else to try, I figure it's worth a shot.
