Hello everyone,I’ve already went through several post forums and tutorials on the internet, and I cannot figure out why my port-forward wont work.I was using Double NAT at my home, but now I’m trying without my own modem (so connecting straight to v10a, through WIFI) and the ports still show as closed through port checking tools. Already completed the following:Fixed the internal IP of the desktop to 192.168.2.x with LAN DHCP on the v10a; With NAT Portmapping, created a new TCP&UDP rule with private and public port 9876-9877 to the pinned internal IP; Rebooted the modem, and also power-cycled it with the power cable.My home network is set to “private mode” in windows, and I even tried turning off the Firewall in order to check it. Still, the port remains closed.Can anyone advise?Should I try a cabled connection instead of WiFi? (even though it wouldn't work for ever since I cannot have a cable to my computer)

Port Forward is not working v10a

Hello everyone,

I’ve already went through several post forums and tutorials on the internet, and I cannot figure out why my port-forward wont work.

I was using Double NAT at my home, but now I’m trying without my own modem (so connecting straight to v10a, through WIFI) and the ports still show as closed through port checking tools.

Already completed the following:

Fixed the internal IP of the desktop to 192.168.2.x with LAN DHCP on the v10a;
With NAT Portmapping, created a new TCP&UDP rule with private and public port 9876-9877 to the pinned internal IP;
Rebooted the modem, and also power-cycled it with the power cable.

My home network is set to “private mode” in windows, and I even tried turning off the Firewall in order to check it. Still, the port remains closed.

Can anyone advise?

Should I try a cabled connection instead of WiFi? (even though it wouldn't work for ever since I cannot have a cable to my computer)

Bladzijde 1 / 1

Hello @Guilherme Déo

Is the program which serves those ports running, otherwise they will show closed because nothing on them is responding.

Can you reach those ports from another device on your local network, maybe with a portchecker app?

Are you using the Guest WiFi or normal WiFi, on the Guest WiFi network it will not work.

For testing it's also better to use a cable.

Is the program which serves those ports running, otherwise they will show closed because nothing on them is responding.

That actually makes a lot of sense, and I realize that I was being dumb hahaha
However, even running it now, I still face the same issue:

netstat -ab

TCP 192.168.2.14:54395 195.122.177.135:https TIME_WAIT
TCP 192.168.2.14:54405 155.133.248.38:27032 ESTABLISHED
>VRisingServer.exe]
UDP 0.0.0.0:9876 *:*
>VRisingServer.exe]
UDP 0.0.0.0:9877 *:*
>VRisingServer.exe]
UDP 0.0.0.0:65318 *:*
>VRisingServer.exe]

Actually, now I realize, why is it showing 0.0.0.0? I have no idea… might need to tweak the server configuration a bit…

Im using normal wifi, will also try reaching it from another machine on my network and get back with results.

Thanks!

So indeed, I tried starting a different server, on the same port, and now it works…

The server of the game is probably not working properly, therefore not listening correctly on the ports.

Will have to figure with them, but this is not an issue with KPN Modem, and it is working as expected.

Thank you!

De Kennisbank

Meld je aan

Welkom

Bestand scannen voor virussen

Dit bestand kan niet worden gedownload