Author Topic: Pace 5268AC ports not opening  (Read 47309 times)

0 Members and 1 Guest are viewing this topic.

Offline Illuminati-Sama

  • PcWinTech Jr. Member
  • Join Date: Jun 2016
  • Posts: 1
  • Karma: 0
Pace 5268AC ports not opening
« on: June 19, 2016, 02:11:44 AM »
Hi, I have opened a port on my router, but every time I test it or a friend tries to connect to the game server I am hosting it fails claiming time out or connection refused. I have tried tcp and udp, I double and triple checked the IP and PC name, I have restarted both the router an my PC (made sure the IP hadnt changed). I never had any issue forwarding ports on my old router (some 2wire, dont remember the specifics) please help Forums

Pace 5268AC ports not opening
« on: June 19, 2016, 02:11:44 AM »

Offline trpted

  • PcWinTech Guru
  • ******
  • Join Date: Sep 2011
  • Posts: 1,190
  • Karma: 37
Re: Pace 5268AC ports not opening
« Reply #1 on: June 19, 2016, 12:34:22 PM »
This is what I noticed, in the hope that it helps you (even while I do not have the same NAT router)

#1 If the port is blocked (for example at the ISP), I get/got: No route to host

#2 If I am not forwarding port the port in my router, I get/got: Connection timed out

#3 If I am forwarding the port in the router but the server is not listening with the firewall either off OR told to allow that port, I get/got: Connection refused

#4 If I am forwarding the port in the router and the server is listening on that port with the firewall off (OR told to allow that port OR allow that app/program), I get/got:

Success: I can see your service on 24.229.*.* on port (5154)
Your ISP is not blocking port 5154

Note where: *.* after 24.229. - is the last two octets of my non bogan IP Address.


#5 You may be wondering by what I mean by listening (or at least how to check that)..

Here are some notes about listening ( quoting my self )


a) If you are on Windows I point you to

b) If you are not on Windows (Mac, Unix/Linux), go look lookup listen on port and then your OS name using Google (or your other favorite search engine).

c) If nothing is listening any TCP ports that you check with a web based port checker, then TCP ports does not show up as open.

d) Be advised that you can not have two servers listening on the same the port on the same computer. So for example before you use an inbond-client side port checker you must make sure that uTorrent is not running - which explains on that they say

If uTorrent is currently open, you will need to completely close it at this time. Make sure that the green uTorrent icon is not still hiding in your notification area (next to your clock). If it is, right click on it and choose "Exit". Before moving forward to things like selecting torrents, seeders, and leachers, we need to verify that your port is open. We recommend downloading our free Open Port Check Tool to test if incoming connections are being allowed through your router on your uTorrent Listening Port

e) And generally if the program/app is running that you are trying to forward for, then the server is listening.

#6 If you are sure that the program/app is running but is not listening that you are trying to forward for, then it would help to know the name of the app/program that you are trying to forward for.


More info...

#1 From DSLR ( -> Forums -> Broadband and Networking -> Networking -> How to know if ports are reaching my computer from outside the post by DSLR user mackey (user # 1479488) on 2015-Sep-24 at 8:05 pm - if you wanted to test port 5154, besides using an inbound client side port checker:

Run tcpdump (`tcpdump -p -n -i <interface> port 5154` would be a good command to start with). If you see incoming TCP SYN packets (not SYN/ACK), or incoming UDP packets from an IP which did not have an outgoing packet first, then the port is open.

#2 For tcpdump on Windows I found this info

#3 For a TCP and a UDP port checker you can use

#4 Using a packet sniffer (like tcpdump = command line / like wireshark = GUI) you should see the traffic from an outside IP address reaching your computer, like I did (when you are forwarding the ports to your computer).

Code: [Select]
user-name@pc-name:~$ tcpdump -p -n -i eth0 port 5154
tcpdump: eth0: You don't have permission to capture on that device
(socket: Operation not permitted)
user-name@pc-name:~$ sudo tcpdump -p -n -i eth0 port 5154
[sudo] password for user-name:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
08:40:24.169428 IP > UDP, length 6
08:42:15.839461 IP > Flags [S], seq 1464127243, win 8192, options [mss 1460], length 0
08:49:05.773987 IP > UDP, length 0
08:49:06.938818 IP > UDP, length 0
08:57:57.580814 IP > Flags [S], seq 3027635480, win 14600, options [mss 1460,sackOK,TS val 4240686068 ecr 0,nop,wscale 8], length 0
08:57:57.712334 IP > Flags [S], seq 1267700791, win 14600, options [mss 1460,sackOK,TS val 4240686102 ecr 0,nop,wscale 8], length 0
08:57:57.840328 IP > Flags [S], seq 1515263633, win 14600, options [mss 1460,sackOK,TS val 4240686134 ecr 0,nop,wscale 8], length 0
7 packets captured
7 packets received by filter
0 packets dropped by kernel

#5 Some notes about my testing..

a) is from this same computer.

b) As noted at -> Services -> Shield's Up they own -thru-

c) I believe is from as it only checks TCP ports.

d) As you can see, I checked port 5154.

#6 The only UDP ports that checks, that I know of, are:

a) DNS (53) -> Freeware -> Utilities -> DNS Benchmark -> DNS Spoofability Test Introduction (or -> Services -> DNS Spoofability Test)

b) Universal Plug n'Play (UPnP) =  1900

From -> Services -> Shield's Up: Click on Proceed and then GRC's Instant UPnP Exposure Test.

« Last Edit: June 19, 2016, 12:43:34 PM by trpted »
Private messages (PM) are not for support questions or for hints to not yet answered topics. The PMs are basically for confident conversation between the users, off the forum. Forums

Re: Pace 5268AC ports not opening
« Reply #1 on: June 19, 2016, 12:34:22 PM »