New messages in the last hour
Get a response within minutes
92% percent of messages responded to
Please visit our Fix & Connect online tool if you require help with connectivity issues on your PS4 system.
If you're still experiencing NAT type issues on your PS4, please try the following three steps which can often help solve the problem. Please do let me know if these work for you, or report back any other solution that did the trick in your case.
Additional ports used for other specific functions/features are:
Please do let me know if you have any success.
If your router supports upnp just enable this and it will open all the required ports for you.
That is silly to suggest because it is a significant security issue to enable uPnP on your router.
then why does it allow me to chat with people on another account?
U aint got to act like a jerk u sound pi**ed just chill hes young like me it happens to me too but its my friend@Picolax
I'm having the same problem as you! is really annoying not being able to talk in party with friends, paid R $ 4.000,00 (live in Brazil)
Consiguio resolver o problema?! estou com o mesmo problema se souber como arrumar me ajude.
The upnp doesn't always work!
I'm on Virgin media with a super hub, mines enabled and I get....
Wireless I get type 2
Wired via home plugs I get type 3
BUT prior to the last update I had type 2 on wired via home plugs & type 3 on wireless
Explaine that one lol
Could be few things VM have borked the Superhub with an update,your homeplugs have failed or one of the ethernet cables is dodgy. VM Superhub's are one of the worst pieces of ISP supplied kit around seen plenty of VM issues in tech help boards over the years,many ditch them by placing them in modem mode and connect a decent router.
Then there's UPnP reliability with the amount of ports PSN uses your better off opening ports and/or setting up a DMZ,a NAT 2 PSN connection test will not fully guarantee open NAT 2 for party chat or third party game servers.
If I have any issues with NAT when I join a party chat I usually just leave then join again and that solves the issue.
You need to explain this, Picolax, just the link won't help, as a matter of fact NAT issues around playstation consoles, and I do mean all playstation consoles is due to the exact same reason you are presenting in this link...
Playstation 4 required ports for proper internet service:
-TCP 80(might not be true),443(might not be true), 3478-3480(it might be true)
-UDP 3478,3479(might be true too)
PSVita/PSTV required ports:
- TCP: 80, 443, 465(mail), 993(mail), 3478, 3479, 3480, 5223, 8080
- UDP: 3478, 3479
Same issue around exact requirements as I mentioned above
PS3 required ports:
TCP: 80, 443, 3478, 3479, 3480, 5223, 8080 and UDP: 3478, 3479.
Same issue around exact requirements as I mentioned above
I'm not going to look at the rest of the portfolio, but these 3 will do the trick...
A little bit of the basics, in why Sony is to blame on bad development:
Fact 1 - Home Internet Access through basic routers, that hold a single valid WAN IP address to share with all your private , through means of NAT home network.
Fact 2 - NAT(Network Address Translation) provided by these routers used upnp information to specify NAT configurations dynamically at the router, this will produce a Port Address Translation for outbound connections, but for inbound the port information must be matched as only on WAN IP is available.
Fact 3 - In NAT you cannot use the exact same port simultaneously and forward it to two different internal devices.
Now the basic error from Sony side:
1. Normally a PS4 customer, must also have been or still is customer for another Playstation device.
2. Conflicting NAT requirements occur when two systems compete for the same port for inbound traffic, hence you end up ith NAT type 3, and even if yo get lucky to have NAT type 2 wich means that yous console as successfully setup all inbound port services, your team members in the party might not be in the same situation, so you end up having issues reaching to them.
3. Why DMZ option can still fail to provide the so called NAT type? DMZ setup specifies a basic static NAT from the WAN IP to a specified IP of your choice, seems good enough, no upnp is still working so if another system tells the router to NAT lets say TCP 3478 to another IP it will have precedence over DMZ setup, so no "NAT type 2" again.
What needs to be done? Only Sony can sucessfully solve this for good:
1st- Identify exactly what are the required ports for inbound traffic, outbound traffic information is only required for firewalled routers, were you simply have to tell the router that those ports are OK to go out and that's all about outbond, but on inbound traffic that is completely different.
This needs to be shared by Sony, I could try to collect some traffic, but in the end I might not test all available network services, and also, they should be to one to put a real fix for this.
2nd- range 3478 to 3480 along with 5223 look more like sony's own networking services, but as long as devices require the same specs for inbound, the routers will allow one and only one...some will only allow the first successful attempt (my case for instance using the operators router), other will update and forward to the last device that uses upnp update (also my case using tp-link ac750)
Solution, each device should use different inbound network requirements, tcha-nan!!! easy...upnp setup would never conflit with that, now Sony move that lazy a** for good, I believe that this might not be hard to provide lets say is the next firmware upgrade for all your devices?
Website ©2017 Sony Interactive Entertainment Europe Limited. All content, game titles, trade names and/or trade dress, trademarks, artwork and associated imagery are trademarks and/or copyright material of their respective owners. All rights reserved. More info