The thing is that I'm totally green with those things. And the pictures don't look anything like what I see on my screen, so I don't even know if i'm in the right place looking for the place to be.. . But if I could se a more step by step how you guys set it up, I think I could figure out, sort of where to be and what to do.
You need the ip address of server on your internal network (usually in the 192.168.x.y range - open an command window and type ipconfig). You need to log into your router's config pages and rummage around for something that looks like port forwarding. It's sometimes called 'Applications', 'NAT', or 'Firewall'. The you need to find where you can specify sets of single ports and protocols and put the right sets of values in - from memory, 60001 UDP, 60002 TCP and 60003 UDP. Each of these needs to be forwarded or mapped to the ip address of your server - 192.168.x.y (whatever it may be). You can usually type a single port (or a range), with a little drop down to select TCP / UDP / Both, then another box to specify the IP address that traffic arriving on these ports & protocols should be mapped to. In some cases you can send the traffic on to a different port on the server - if your config pages are asking for an input and output port for each mapping, use the same port for input and output. There's really nothing more the devs can do here. There are probably good sources of help which can be googled, maybe even a forum for your particular router. Windows firewall should be trivial to configure - it might already by added to the list of allowed programs
It does work for some but not for others. I've done all the steps many times on different machines and routers and it still does not work. Right now I'm blaming the ISp but I am going to do some test at a buddy who has the same ISp. Fyi the issue is : no response from server. After anyone who tries to connect enters the password
guys this site portforward.com/english/routers/port_forwarding/ has free tutorials for hundreds of different routers
I think im giving up on this. Tried on a completely different router and ISP. Got it to work internally ( joined with a laptop on the same router ) Tried an external connection and again got : No response from server. Also shows no ping. But that did not spot the connection internally earlier. I know how to port forward. Its something i have been doing for years it just doesn't work somehow. Here is some screenshot. Did some port check test on my ip and somehow the UPD part is not working. That pretty much shows its on this side. But like i mentioned i did the exact same thing on a different internet provider and router and still could not get it to work either.
I think I'll wait on this one, until it's implemented in a way that means we don't have to mess around with our routers or ipconfig. It seems like people that know what they're doing are having trouble so I stand no chance.
I'm not trying to sound like a tool, but if you don't know how to open ports on your router and are new to these concepts, perhaps running a dedicated server isn't a good idea?
hmm dude. I think the issue is somewhere else. Not with their program. Its working for tons of people out there. Once the rush is done someone will come to this thread and hopefully might have a solution for us.
I agree. Like i mentioned above i have done this many times. Right now using an external program i was able to see that UPD is getting "refused" on those port. What i find odd is my buddy did it as well on a completely different ISP and router ( motorola ) and he gets the same result. I don't blame the tool here. There is something else at play here.
Maybe windows firewall or another software firewall? Not sure if the os makes any difference - using win 7 ultimate here. Edit - perhaps there's something already using those ports? Netstat -o -a will show what process ids are using what ports, then show the pids in task manager and see what you can find
I dont really want to flood the page here. But here is the netstat Spoiler: Netstat list Proto Local Address Foreign Address State PID TCP 0.0.0.0:135 Memots-Tabtop:0 LISTENING 724 TCP 0.0.0.0:445 Memots-Tabtop:0 LISTENING 4 TCP 0.0.0.0:8088 Memots-Tabtop:0 LISTENING 4 TCP 0.0.0.0:27036 Memots-Tabtop:0 LISTENING 5688 TCP 0.0.0.0:49152 Memots-Tabtop:0 LISTENING 508 TCP 0.0.0.0:49153 Memots-Tabtop:0 LISTENING 836 TCP 0.0.0.0:49154 Memots-Tabtop:0 LISTENING 896 TCP 0.0.0.0:49155 Memots-Tabtop:0 LISTENING 1408 TCP 0.0.0.0:49156 Memots-Tabtop:0 LISTENING 620 TCP 0.0.0.0:49157 Memots-Tabtop:0 LISTENING 612 TCP 0.0.0.0:49538 Memots-Tabtop:0 LISTENING 3156 TCP 0.0.0.0:60001 Memots-Tabtop:0 LISTENING 1088 TCP 127.0.0.1:5354 Memots-Tabtop:0 LISTENING 1660 TCP 192.168.1.64:139 Memots-Tabtop:0 LISTENING 4 TCP 192.168.1.64:50367 sea15s01-in-f13:https CLOSE_WAIT 2340 TCP 192.168.1.64:50370 hk2sch130020843:https ESTABLISHED 2728 TCP 192.168.1.64:50373 pa-in-f108:imaps ESTABLISHED 2340 TCP 192.168.1.64:50400 static:https ESTABLISHED 3500 TCP 192.168.1.64:50408 static:https ESTABLISHED 3500 TCP 192.168.1.64:50464 pe-in-f188:https ESTABLISHED 4588 TCP 192.168.1.64:50547 a23-195-226-172:http ESTABLISHED 2728 TCP 192.168.1.64:50548 a23-195-226-172:http ESTABLISHED 2728 TCP 192.168.1.64:50549 cache:https ESTABLISHED 4588 TCP 192.168.1.64:50550 a-0011:https ESTABLISHED 808 TCP [::]:135 Memots-Tabtop:0 LISTENING 724 TCP [::]:445 Memots-Tabtop:0 LISTENING 4 TCP [::]:8088 Memots-Tabtop:0 LISTENING 4 TCP [::]:49152 Memots-Tabtop:0 LISTENING 508 TCP [::]:49153 Memots-Tabtop:0 LISTENING 836 TCP [::]:49154 Memots-Tabtop:0 LISTENING 896 TCP [::]:49155 Memots-Tabtop:0 LISTENING 1408 TCP [::]:49156 Memots-Tabtop:0 LISTENING 620 TCP [::]:49157 Memots-Tabtop:0 LISTENING 612 TCP [::]:49538 Memots-Tabtop:0 LISTENING 3156 TCP [::1]:8088 Memots-Tabtop:50407 ESTABLISHED 4 TCP [::1]:49242 Memots-Tabtop:0 LISTENING 5464 TCP [::1]:50407 Memots-Tabtop:8088 ESTABLISHED 1088 UDP 0.0.0.0:500 *:* 896 UDP 0.0.0.0:4500 *:* 896 UDP 0.0.0.0:5355 *:* 1068 UDP 0.0.0.0:27036 *:* 5688 UDP 0.0.0.0:51832 *:* 6248 UDP 0.0.0.0:52774 *:* 1660 UDP 0.0.0.0:56924 *:* 2208 UDP 0.0.0.0:58767 *:* 5688 UDP 0.0.0.0:60000 *:* 1088 UDP 0.0.0.0:60002 *:* 1088 UDP 0.0.0.0:61137 *:* 1408 UDP 127.0.0.1:1900 *:* 3212 UDP 127.0.0.1:54497 *:* 3212 UDP 192.168.1.64:137 *:* 4 UDP 192.168.1.64:138 *:* 4 UDP 192.168.1.64:1900 *:* 3212 UDP 192.168.1.64:5353 *:* 1660 UDP 192.168.1.64:54496 *:* 3212 UDP [::]:500 *:* 896 UDP [::]:4500 *:* 896 UDP [::]:5355 *:* 1068 UDP [::]:52775 *:* 1660 UDP [::1]:1900 *:* 3212 UDP [::1]:5353 *:* 1660 UDP [::1]:54495 *:* 3212 UDP [fe80::b451:fd12:e89f:6f95%19]:1900 *:* 3212 UDP [fe80::b451:fd12:e89f:6f95%19]:54494 *:* 3212 Also. I disabled the firewall on the machine running the server and anti virus as well during the testing. win 8.1 one that is noteworthy is i cannot ping my external Ip either from external service.
Is the dedi server app running? If not, process 1088 is using 1 of the ports so that would stop it working Don't worry about being unable to ping the external address - its usually blocked and shouldn't be needed
disabled the server app. Spoiler: Netstat Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:135 Memots-Tabtop:0 LISTENING 724 TCP 0.0.0.0:445 Memots-Tabtop:0 LISTENING 4 TCP 0.0.0.0:8088 Memots-Tabtop:0 LISTENING 4 TCP 0.0.0.0:27036 Memots-Tabtop:0 LISTENING 5688 TCP 0.0.0.0:49152 Memots-Tabtop:0 LISTENING 508 TCP 0.0.0.0:49153 Memots-Tabtop:0 LISTENING 836 TCP 0.0.0.0:49154 Memots-Tabtop:0 LISTENING 896 TCP 0.0.0.0:49155 Memots-Tabtop:0 LISTENING 1408 TCP 0.0.0.0:49156 Memots-Tabtop:0 LISTENING 620 TCP 0.0.0.0:49157 Memots-Tabtop:0 LISTENING 612 TCP 0.0.0.0:49538 Memots-Tabtop:0 LISTENING 3156 TCP 0.0.0.0:60001 Memots-Tabtop:0 LISTENING 1088 TCP 127.0.0.1:5354 Memots-Tabtop:0 LISTENING 1660 TCP 192.168.1.64:139 Memots-Tabtop:0 LISTENING 4 TCP 192.168.1.64:50367 sea15s01-in-f13:https CLOSE_WAIT 2340 TCP 192.168.1.64:50370 hk2sch130020843:https ESTABLISHED 2728 TCP 192.168.1.64:50373 pa-in-f108:imaps ESTABLISHED 2340 TCP 192.168.1.64:50400 static:https ESTABLISHED 3500 TCP 192.168.1.64:50408 static:https ESTABLISHED 3500 TCP 192.168.1.64:50464 pe-in-f188:https ESTABLISHED 4588 TCP 192.168.1.64:50547 a23-195-226-172:http ESTABLISHED 2728 TCP 192.168.1.64:50548 a23-195-226-172:http ESTABLISHED 2728 TCP 192.168.1.64:50549 cache:https ESTABLISHED 4588 TCP 192.168.1.64:50550 a-0011:https ESTABLISHED 808 TCP [::]:135 Memots-Tabtop:0 LISTENING 724 TCP [::]:445 Memots-Tabtop:0 LISTENING 4 TCP [::]:8088 Memots-Tabtop:0 LISTENING 4 TCP [::]:49152 Memots-Tabtop:0 LISTENING 508 TCP [::]:49153 Memots-Tabtop:0 LISTENING 836 TCP [::]:49154 Memots-Tabtop:0 LISTENING 896 TCP [::]:49155 Memots-Tabtop:0 LISTENING 1408 TCP [::]:49156 Memots-Tabtop:0 LISTENING 620 TCP [::]:49157 Memots-Tabtop:0 LISTENING 612 TCP [::]:49538 Memots-Tabtop:0 LISTENING 3156 TCP [::1]:8088 Memots-Tabtop:50407 ESTABLISHED 4 TCP [::1]:49242 Memots-Tabtop:0 LISTENING 5464 TCP [::1]:50407 Memots-Tabtop:8088 ESTABLISHED 1088 UDP 0.0.0.0:500 *:* 896 UDP 0.0.0.0:4500 *:* 896 UDP 0.0.0.0:5355 *:* 1068 UDP 0.0.0.0:27036 *:* 5688 UDP 0.0.0.0:51832 *:* 6248 UDP 0.0.0.0:52774 *:* 1660 UDP 0.0.0.0:56924 *:* 2208 UDP 0.0.0.0:58767 *:* 5688 UDP 0.0.0.0:60000 *:* 1088 UDP 0.0.0.0:60002 *:* 1088 UDP 0.0.0.0:61137 *:* 1408 UDP 127.0.0.1:1900 *:* 3212 UDP 127.0.0.1:54497 *:* 3212 UDP 192.168.1.64:137 *:* 4 UDP 192.168.1.64:138 *:* 4 UDP 192.168.1.64:1900 *:* 3212 UDP 192.168.1.64:5353 *:* 1660 UDP 192.168.1.64:54496 *:* 3212 UDP [::]:500 *:* 896 UDP [::]:4500 *:* 896 UDP [::]:5355 *:* 1068 UDP [::]:52775 *:* 1660 UDP [::1]:1900 *:* 3212 UDP [::1]:5353 *:* 1660 UDP [::1]:54495 *:* 3212 UDP [fe80::b451:fd12:e89f:6f95%19]:1900 *:* 3212 UDP [fe80::b451:fd12:e89f:6f95%19]:54494 *:* 3212 Still shows up. The the funny part is there is no such process listed at 1088
This is not going to happen. Due to the principles of how a router works, especially network adress translation (NAT), it is essential to open ports if you want to make any service on a client pc visible from the internet. The problem is that portforwarding is configuered a bit different depending on router model. So it's just not possible to give a general manual on how to do it.
Hold on. Bad cut and paste on the previous Its gone now. Spoiler: netstat list Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:135 Memots-Tabtop:0 LISTENING 724 TCP 0.0.0.0:445 Memots-Tabtop:0 LISTENING 4 TCP 0.0.0.0:27036 Memots-Tabtop:0 LISTENING 5688 TCP 0.0.0.0:49152 Memots-Tabtop:0 LISTENING 508 TCP 0.0.0.0:49153 Memots-Tabtop:0 LISTENING 836 TCP 0.0.0.0:49154 Memots-Tabtop:0 LISTENING 896 TCP 0.0.0.0:49155 Memots-Tabtop:0 LISTENING 1408 TCP 0.0.0.0:49156 Memots-Tabtop:0 LISTENING 620 TCP 0.0.0.0:49157 Memots-Tabtop:0 LISTENING 612 TCP 0.0.0.0:49538 Memots-Tabtop:0 LISTENING 3156 TCP 127.0.0.1:5354 Memots-Tabtop:0 LISTENING 1660 TCP 192.168.1.64:139 Memots-Tabtop:0 LISTENING 4 TCP 192.168.1.64:50370 hk2sch130020843:https ESTABLISHED 2728 TCP 192.168.1.64:50373 pa-in-f108:imaps ESTABLISHED 2340 TCP 192.168.1.64:50464 pe-in-f188:https ESTABLISHED 4588 TCP 192.168.1.64:50643 pe-in-f109:imaps ESTABLISHED 2340 TCP 192.168.1.64:50644 sea15s01-in-f13:https CLOSE_WAIT 2340 TCP 192.168.1.64:50669 pa-in-f95:http ESTABLISHED 4588 TCP 192.168.1.64:50682 a-0011:https ESTABLISHED 808 TCP 192.168.1.64:50683 169:https ESTABLISHED 2208 TCP 192.168.1.64:50684 cache:https ESTABLISHED 4588 TCP 192.168.1.64:50685 cache:https ESTABLISHED 4588 TCP [::]:135 Memots-Tabtop:0 LISTENING 724 TCP [::]:445 Memots-Tabtop:0 LISTENING 4 TCP [::]:49152 Memots-Tabtop:0 LISTENING 508 TCP [::]:49153 Memots-Tabtop:0 LISTENING 836 TCP [::]:49154 Memots-Tabtop:0 LISTENING 896 TCP [::]:49155 Memots-Tabtop:0 LISTENING 1408 TCP [::]:49156 Memots-Tabtop:0 LISTENING 620 TCP [::]:49157 Memots-Tabtop:0 LISTENING 612 TCP [::]:49538 Memots-Tabtop:0 LISTENING 3156 TCP [::1]:49242 Memots-Tabtop:0 LISTENING 5464 UDP 0.0.0.0:500 *:* 896 UDP 0.0.0.0:4500 *:* 896 UDP 0.0.0.0:5355 *:* 1068 UDP 0.0.0.0:27036 *:* 5688 UDP 0.0.0.0:51832 *:* 6248 UDP 0.0.0.0:52774 *:* 1660 UDP 0.0.0.0:56924 *:* 2208 UDP 0.0.0.0:58767 *:* 5688 UDP 0.0.0.0:60230 *:* 4588 UDP 0.0.0.0:60662 *:* 4588 UDP 0.0.0.0:61137 *:* 1408 UDP 127.0.0.1:1900 *:* 3212 UDP 127.0.0.1:54497 *:* 3212 UDP 192.168.1.64:137 *:* 4 UDP 192.168.1.64:138 *:* 4 UDP 192.168.1.64:1900 *:* 3212 UDP 192.168.1.64:5353 *:* 1660 UDP 192.168.1.64:54496 *:* 3212 UDP [::]:500 *:* 896 UDP [::]:4500 *:* 896 UDP [::]:5355 *:* 1068 UDP [::]:52775 *:* 1660 UDP [::1]:1900 *:* 3212 UDP [::1]:5353 *:* 1660 UDP [::1]:54495 *:* 3212 UDP [fe80::b451:fd12:e89f:6f95%19]:546 *:* 836 UDP [fe80::b451:fd12:e89f:6f95%19]:1900 *:* 3212 UDP [fe80::b451:fd12:e89f:6f95%19]:54494 *:* 3212 So there is nothing currently using the ports Also @Arthur Spooner Thats the one i have. http://portforward.com/english/routers/port_forwarding/Actiontec/V1000H_-_Telus/defaultguide.htm Its is quite straight forward The router is setup correctly. And thanks @mr_belowski for wanting to help. I feel i spent way too much time on this already
I can create a server, I just can't get in it....(no response) cheers for the info,,,but I don't understand anything you said (lol) why does it work in Pcars...I can create a lobby piece of piss there...I just don't wanna drive pcars....