Trouble logging in samsung s22 ultra

howdy

of late last 2 to 3 weeks ive had trouble being logged out when i open roon with my s22 ultra phone.

i get made to select my merging nadac stack. then log in. sometimes i go straight in. this morning it took me one merging restart and then 4 log in attempts before i successfully played music.

i get a to many attempts failed and no music plays.

ive had this setup working fine for a couple of years. only ever other issue i have was sometimes id open the app while playing and id have to close it a reopen for it to work again or it would just hang on the screen with no response.

everything is up to date.

only new thing is ive gone from 25mbs to 750mbs nbn in the last few weeks black friday. no other internet issues.



Hi @stephen_kinnane ,

Thanks for reaching out. Looking over the error you posted, it sounds like your Roon Server can’t communicate with the account servers properly. We have seen users have a better experience in the past if they change their Router’s DNS servers from the ISP provided ones to Cloudflare DNS, Quad9 or Google DNS. Can you please give this a try and let me know if it helps?

thanks ill see if i can do this

Hi @stephen_kinnane,

Our diagnostic servers indicate that the S22 might still be having difficulty reaching RoonServer. Were you able to change the assigned DNS server, and did that have any effect?

If you’re still having issues, please describe the basic arrangement of your network, including routers, switches, and mesh nodes. Please also verify that you’ve updated to the latest available build of Roon.

Thanks!

howdy i tried using this app

and running the merging but i could get it to work didnt really understand what to do. tried using the merging this morning and had to log in twice and restart once for it to recognise my s22.

i have just updated the roon app today.

could you explain how to use the app i downloaded with the merging please.

my whole network is

coax to nbn

ethernet purist audio design cat 7

orbi rbr 50

35m purist audio design cat 7

bonn nx switch

accoustic revive cat 7

bonn nx

accoustic revive cat 7

merging dac player + power.

my tv and marantz both play from second bonn nx with ethernet no problem movies and music

still have the same issue if i use warp

1.1.1.1 and turn it on i cant find my roon core merging player

still cant log in i used one of the dns


t

im pretty upset no support. no answers? why is no one helping?

Hi @stephen_kinnane,

Thank you for your patience. We understand this issue has been frustrating.

Here’s where we stand after reviewing the case, and what we can offer as next step if you’re willing to troubleshoot further:

First off, we missed the chance to save you some unnecessary tinkering. The Cloudflare WARP product is, unfortunately, unrelated to the request my colleague had sent previously, and has likely exacerbated the issue at hand: a session-layer validation problem between the S22 and RoonServer.

Specifically, we were asking you to reassign your router’s DNS server to something known to be reliable, like the Cloudflare DNS generic server (which uses address 1.1.1.1) or another major reliable server (Google, 8.8.8.8, etc). This is because we need to be sure that the address for our login servers is being resolved reliably within your local network so that your RoonServer machine can reach it. This is a step you will take entirely within your router, not the phone.

RoonServer is not recognizing the phone’s Roon session as active. This is almost certainly a consequence of the various managed network components that sit between the upstream router and the server machine in the topology you’ve described.

You’ll need to:

a) enable IGMP snooping and multicast forwarding in the Orbi settings
b) describe where the RoonServer machine is connected in the network topology you’ve shared
c) bypass any managed network switches between RoonServer and the access point or router serving the Samsung S22
d) Disable all VPNs or separate network interfaces on the phone, including WARP.

We’ll follow up promptly once we see a response. Thank you again for your patience.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.