Unable to scan for Roon device with IP 192.178.168.49 (ref#9QTKI7)

Is Roon Server running?

· Yes, Roon Server is turned on and running.

What do you see on your screen?

· "Waiting for your Roon Server"

What happens if you press the "Select a different Roon Server" button?

· I don't see Roon Server.

Please try to restart your Roon Server by closing the Roon app in the taskbar or rebooting your Roon Server machine.

· No, the issue remains the same

Please try to restart your network setup by unplugging, waiting 30 seconds and then replugging in your networking gear.

· No, the issue remains the same

Please select how you've connected your Roon Server to the internet

· Roon Server is connected by *WiFi*

Have you checked your firewall settings to ensure that Roon is allowed through?

· Roon still won't connect even after checking this aspect

Have you verified that Roon Server is on the same subnet as your Remotes?

· My Remotes and Server are on the same subnet and I still can't connect

Sometimes the issues can be resolved with a reinstall of your Roon Remote app. Let's try to perform a reinstall and see if it helps.

· I've reinstalled the Roon Remote but it did not help

What is the operating system of your Roon Server host machine?

· *Windows*

Select any of the following components that are present in your local network setup

· *VPN* installed on RoonServer or Roon Remotes

You mentioned a VPN. Have you tried disabling it?

· I tried disabling my VPN/proxy connection and Roon still won't connect

Describe the issue

When i type de ip adres 192.178.168.49 i'm not able to scan for the roon device. ( just the same "waiting for your roon server...

Describe your network setup

Everthing worked well , en

Are you sure about that address? 192.178.168.49 is NOT in the range of private IP addresses, so it would be more than unusual to use such an address on a home LAN.

The typical private address range in Class C home networks is 192.168.0.0 to 192.168.255.255

3 Likes

Hey @maries_grootenboer,

Thanks for writing in! It’s good to see you on the community again. I believe @Suedkiez may be correct here - can you double check your IP scheme, perhaps it may be 192.168.178?

We’ll be on standby for your reply! :pray:

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