ipoisonxl Posted March 4, 2014 Share Posted March 4, 2014 Hi! I'm making a private server for me and a friend, but the port forwarding isn't working. I know how to port forward, I already have another port forwarded for Minecraft, and that works fine. But for some reason, it doesn't work with Project Zomboid. here's my settings for the server's port forward. What's wrong with it? It should work fine, butand yes, I am running the server while checking if the ports are open. It simply isn't open, and it's not connecting in game either. Any help is appreciated, thanks. Link to comment Share on other sites More sharing options...
Hrath Posted March 5, 2014 Share Posted March 5, 2014 I am getting the exact same problem. I have a Belkin router. Link to comment Share on other sites More sharing options...
Connall Posted March 5, 2014 Share Posted March 5, 2014 Assuming your running the server on the same computer, are you able to connect to the server with "localhost" as the address? Just to check if the server is running properly. Link to comment Share on other sites More sharing options...
Vantus Posted March 5, 2014 Share Posted March 5, 2014 Personally, I don't see the port testers linked on this forum as the be-all-and-end-all.I have the exact same result as the OP (saying my ports are closed) even though my ports are forwarded and I am running around on my Server with my friends.It's not completely accurate from my experience. Link to comment Share on other sites More sharing options...
ipoisonxl Posted March 5, 2014 Author Share Posted March 5, 2014 In my case, I'm able to connect to localhost, but my friend wasn't able to connect to my IP. Yes, I'm using my external IP address. Link to comment Share on other sites More sharing options...
nasKo Posted March 5, 2014 Share Posted March 5, 2014 Port 16261 is a UDP port.The others are TCP ports. You can check if your system is accepting connections on the UDP port 16261 by starting the server and then opening a cmd and enteringnetstat -anNow check the output for the UDP port 16261.In some cases it's normal that port testers might show TCP ports as closed because they are not in use when players are not connected and playing.Most online port checkers are not able to check for UDP ports.The FAQ will be updated in that regard, soon. Link to comment Share on other sites More sharing options...
Hrath Posted March 5, 2014 Share Posted March 5, 2014 Both my friend and I have tried hosting from our computers but to no avail. Ports are forwarded and I'm able to connect to my own using the external ip but he can't connect. Windows firewall is off, anti virus is Avast and off. I only have two of the TCP ports open. I'm at a loss. Any help would be great. Link to comment Share on other sites More sharing options...
EnigmaGrey Posted March 5, 2014 Share Posted March 5, 2014 Ports need to be both TCP and UDP, and you'll probably need at least 3 for two people. Link to comment Share on other sites More sharing options...
ipoisonxl Posted March 6, 2014 Author Share Posted March 6, 2014 I opened 10 ports, UDP and TCP. For the netstat -an thing, the output for UDP port 16261 is *:*, or something along those lines. If anyone wants to test, server will be open all night. IP is: EDIT: (no testing necessary anymore) Link to comment Share on other sites More sharing options...
Hrath Posted March 6, 2014 Share Posted March 6, 2014 Hey, I was able to get into your Server no problem. Link to comment Share on other sites More sharing options...
ipoisonxl Posted March 6, 2014 Author Share Posted March 6, 2014 Yeah, it works now. Thanks everyone for the help! Link to comment Share on other sites More sharing options...
Strider Posted March 14, 2014 Share Posted March 14, 2014 Port 16261 is a UDP port.The others are TCP ports. You can check if your system is accepting connections on the UDP port 16261 by starting the server and then opening a cmd and enteringnetstat -anNow check the output for the UDP port 16261.In some cases it's normal that port testers might show TCP ports as closed because they are not in use when players are not connected and playing.Most online port checkers are not able to check for UDP ports.The FAQ will be updated in that regard, soon. I'm having the same problem. Pretty much identical to the OP. Connection failed for those that try to connect. I've my ports set up as follows http://imgur.com/DtInwV3 Any advice in this regard would be helpful nasKo. Also, netstat shows : UDP 0.0.0.0:16261 *:* Link to comment Share on other sites More sharing options...
nasKo Posted March 14, 2014 Share Posted March 14, 2014 Port 16261 is a UDP port.The others are TCP ports.You can check if your system is accepting connections on the UDP port 16261 by starting the server and then opening a cmd and enteringnetstat -anNow check the output for the UDP port 16261.In some cases it's normal that port testers might show TCP ports as closed because they are not in use when players are not connected and playing.Most online port checkers are not able to check for UDP ports.The FAQ will be updated in that regard, soon.I'm having the same problem. Pretty much identical to the OP. Connection failed for those that try to connect. I've my ports set up as followshttp://imgur.com/DtInwV3Any advice in this regard would be helpful nasKo. Also, netstat shows : UDP 0.0.0.0:16261 *:*They probably cannot connect because you haven't forwarded the TCP ports.If possible, just switch it from "UDP" to "UDP/TCP" (sometimes called "both") Link to comment Share on other sites More sharing options...
Strider Posted March 14, 2014 Share Posted March 14, 2014 Oh, I should point out that I can connect to my own server so it is running ok it would seem. It'd seem to suggest a port forwarding problem. I've made the change. I'm going to leave the server up, hopefully somebody will be able to test it for me. IP: 62.249.220.97UN: guestPW: guest Link to comment Share on other sites More sharing options...
nasKo Posted March 14, 2014 Share Posted March 14, 2014 Oh, I should point out that I can connect to my own server so it is running ok it would seem. It'd seem to suggest a port forwarding problem. I've made the change. I'm going to leave the server up, hopefully somebody will be able to test it for me. IP: 62.249.220.97 UN: guest PW: guestCan't test from here but it's normal that you can connect to your own server (because there's no port forwarding required for it). Good indicator, though. If other people cannot connect, it's likely a network issue, not a server issue. Link to comment Share on other sites More sharing options...
Strider Posted March 14, 2014 Share Posted March 14, 2014 Oh, I should point out that I can connect to my own server so it is running ok it would seem. It'd seem to suggest a port forwarding problem. I've made the change. I'm going to leave the server up, hopefully somebody will be able to test it for me. IP: 62.249.220.97UN: guestPW: guestCan't test from here but it's normal that you can connect to your own server (because there's no port forwarding required for it). Good indicator, though.If other people cannot connect, it's likely a network issue, not a server issue. That's what I was pretty much getting at. I'll wait until someone is able to test. Link to comment Share on other sites More sharing options...
nasKo Posted March 14, 2014 Share Posted March 14, 2014 Ah. I'll shut up, then.always sounds like a good idea Link to comment Share on other sites More sharing options...
Strider Posted March 14, 2014 Share Posted March 14, 2014 Ah. I'll shut up, then.always sounds like a good idea Thanks for your help btw Link to comment Share on other sites More sharing options...
Strider Posted March 14, 2014 Share Posted March 14, 2014 Nasko - I'm still unable to host. Do you have anything else you can suggest to me, I'm at a bit of a loss. Thanks Link to comment Share on other sites More sharing options...
Snipeingkicker Posted June 6, 2014 Share Posted June 6, 2014 I made an account just so I could post my solution. After spending hours searching the web and changing ports to udp or tcp over and over I found out what I was missing.Make sure you have 16261 under udpand add individually in tcp the 16262 then add 16263 and so on.Of course just doing that doesn't fix it. What you have to do is, start the server after you did the above. The big step that I missed is, RUN THE GAME AS ADMIN.Once you did that you can connect to your server from your public ip or the internal ip. That's all you had to do. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now