NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PS4 won't connect to my Orbi RBR10
*Note: my mesh system id the RBR10/RBS10, it won't find it on the model search bar* My PS4 won't connect to my new Orbi router, when trying to connect to the network it gives me a "DNS not found" i...
Changing Orbi firmware is not likely to improve the situation, and may introduce new issues. I would solve the PS4 problem first and delay updating Orbi firmware until there is a lot of evidence that the update has gone smoothly for other users.
Is this the procedure being followed?
https://www.spectrum.net/support/internet/playstation-4-ps4-wifi-connection/
Does the PS4 display the "results" of the connection?
(IP address, subnet mask, gateway, DNS server)
Everything on the link is being followed.
When trying to connect
1. 5GHz bands only
2. Choose my wifi
3. Use the "easy" setup
4. No proxy
5. Attempts to connect and displays "a DNS server cannot be used, The DNS server didn't respond in time.
After this i usually go into custom mode instead of easy and i use a general DNS server, (1.1.1.1). Custom mode has; IP address settings to Automatic, DHCP to Do not specify, DNS to Manual primary: 1.1.1.1 and secondary 1.0.0.1. , MTU to automatic, proxy server to do not use.
When i completed all of that i test internet connection
SSID: Wifi Name
Obtaining IP address: Successful
Internet connection: Failed "cannot connect to server within the time limit."
ive contacted support of both Netgear and PSN and they both blamed eachother.
Is there anything that im doing wrong or that should i change and let me know if you need more details.
Thanks in advance!
When trying to connect
1. 5GHz bands only
2. Choose my wifi
3. Use the "easy" setup
4. No proxy
5. Attempts to connect and displays "a DNS server cannot be used, The DNS server didn't respond in time.
After this i usually go into custom mode instead of easy and i use a general DNS server, (1.1.1.1). Custom mode has; IP address settings to Automatic, DHCP to Do not specify, DNS to Manual primary: 1.1.1.1 and secondary 1.0.0.1. , MTU to automatic, proxy server to do not use.
When i completed all of that i test internet connection
SSID: Wifi Name
Obtaining IP address: Successful
Internet connection: Failed "cannot connect to server within the time limit."
ive contacted support of both Netgear and PSN and they both blamed eachother.
Is there anything that im doing wrong or that should i change and let me know if you need more details.
Thanks in advance!
Have never used PS4, so some of the networking choices are "new to me". (particularly Defining the DHCP server - learn something every day!)
The process seems entirely correct to me. What it sounds like is either the gateway IP address or the subnet mask is incorrect. This would cause attempts to contact a DNS server to fail. The gateway should be the IP of the Orbi router and the subnet mask should be 255.255.255.0
The Orbi is configured as a "router", correct? Other devices connect and function correctly?
When the PS4 connects, the Orbi Attached Devices (or "app") shows the PS4 having an IP address that falls within the DHCP range?
Glad you are learning ahaha.
But yea when trying to do a custom IP adress setup i am too fill in these:
IP address
Subnet Mask
Default Gateway
Primary DNS
Secondary DNS
It also come with a PPPoE but i dont think its useful here.
The IP adress like you have told me can be found on the Orbi router itself, Subnet like you said should be 255.255.255.0, but what do i put in the Default Gateway and the DNS's.
Yes everyother device in my house connects and functions properly. The PS4 never techincally never connects, its connected via an extender that is connected to the router. I honnestly do not know what a DHCP is and i know a lot less if it falls within the range of the DHCP. I am still new too everything wifi related.
https://community.netgear.com/t5/Orbi/PS4-Refusing-to-connect-to-Orbi-WiFi/m-p/1697509
you will notice in this thread are posts that agree with what I've been saying for years. In MOST cases it's the firmware and I'm NOT the only who is tired of chasing useless questions when all they did was roll the firmware back. You can thank me now.
