LOGIN SOFTWARE

[EA2ESB]

I can't find anywhere to enter my username and password. The software does not ask for it at any time and of course, it does not work.

I sure may sound stupid, sorry.

NO ID in red.

P.S. I am already registered on the website with an active user.

[RandyW]

I sure may sound stupid, sorry.

Not at all. It doesn't sound like the client is connecting to ANY server.

Copy / paste the full log here, or send it to rmnoise@ournetplace.com.
( To find the full log, navigate to INFO -> FULL LOG within the client.)

[EA2ESB]

Hi Randy.

We will continue the conversation here, in case it helps other people.

I sent you the log, does it seem like a DNS problem?

I have added an exception in the firewall and everything remains the same.

Run Windows 11

I'm going to open the port that puts the log on the router and try again.

Thank you very much for your help

2024-03-11 20:40:19.415742 Local sound devices:
2024-03-11 20:40:19.427797 input device: 0 MME: Asignador de sonido Microsoft - Input
2024-03-11 20:40:19.427797 input device: 1 MME: Microphone (High Definition Aud
2024-03-11 20:40:19.427797 input device: 2 MME: CABLE Output (VB-Audio Virtual
2024-03-11 20:40:19.428797 input device: 3 MME: VFO A (Virtual Audio Cable)
2024-03-11 20:40:19.428797 input device: 4 MME: Línea (2- USB AUDIO CODEC)
2024-03-11 20:40:19.428797 input device: 5 MME: VoiceMeeter Output (VB-Audio Vo
2024-03-11 20:40:19.440799 output device: 6 MME: Asignador de sonido Microsoft - Output
2024-03-11 20:40:19.440799 output device: 7 MME: 1 - SAMSUNG (AMD High Definitio
2024-03-11 20:40:19.441800 output device: 8 MME: VFO A (Virtual Audio Cable)
2024-03-11 20:40:19.441800 output device: 9 MME: VoiceMeeter Input (VB-Audio Voi
2024-03-11 20:40:19.441800 output device: 10 MME: Altavoces (VB-Audio Virtual Cab
2024-03-11 20:40:19.441800 output device: 11 MME: Altavoces (2- USB AUDIO CODEC)
2024-03-11 20:40:19.441800 input device: 12 Windows DirectSound: Controlador primario de captura de sonido
2024-03-11 20:40:19.441800 input device: 13 Windows DirectSound: Microphone (High Definition Audio Device)
2024-03-11 20:40:19.441800 input device: 14 Windows DirectSound: CABLE Output (VB-Audio Virtual Cable)
2024-03-11 20:40:19.441800 input device: 15 Windows DirectSound: VFO A (Virtual Audio Cable)
2024-03-11 20:40:19.441800 input device: 16 Windows DirectSound: Línea (2- USB AUDIO CODEC)
2024-03-11 20:40:19.441800 input device: 17 Windows DirectSound: VoiceMeeter Output (VB-Audio VoiceMeeter VAIO)
2024-03-11 20:40:19.442797 output device: 18 Windows DirectSound: Controlador primario de sonido
2024-03-11 20:40:19.442797 output device: 19 Windows DirectSound: 1 - SAMSUNG (AMD High Definition Audio Device)
2024-03-11 20:40:19.442797 output device: 20 Windows DirectSound: VFO A (Virtual Audio Cable)
2024-03-11 20:40:19.442797 output device: 21 Windows DirectSound: VoiceMeeter Input (VB-Audio VoiceMeeter VAIO)
2024-03-11 20:40:19.442797 output device: 22 Windows DirectSound: Altavoces (VB-Audio Virtual Cable)
2024-03-11 20:40:19.442797 output device: 23 Windows DirectSound: Altavoces (2- USB AUDIO CODEC)
2024-03-11 20:40:19.443797 Unsupported input device: 29 Windows WASAPI: CABLE Output (VB-Audio Virtual Cable)
2024-03-11 20:40:19.444798 Unsupported input device: 30 Windows WASAPI: Microphone (High Definition Audio Device)
2024-03-11 20:40:19.444798 Unsupported input device: 31 Windows WASAPI: VFO A (Virtual Audio Cable)
2024-03-11 20:40:19.445797 Unsupported input device: 32 Windows WASAPI: Línea (2- USB AUDIO CODEC)
2024-03-11 20:40:19.446801 Unsupported input device: 33 Windows WASAPI: VoiceMeeter Output (VB-Audio VoiceMeeter VAIO)
2024-03-11 20:40:19.447797 Unsupported output device: 24 Windows WASAPI: VFO A (Virtual Audio Cable)
2024-03-11 20:40:19.517882 Unsupported output device: 25 Windows WASAPI: 1 - SAMSUNG (AMD High Definition Audio Device)
2024-03-11 20:40:19.518883 Unsupported output device: 26 Windows WASAPI: VoiceMeeter Input (VB-Audio VoiceMeeter VAIO)
2024-03-11 20:40:19.519883 Unsupported output device: 27 Windows WASAPI: Altavoces (VB-Audio Virtual Cable)
2024-03-11 20:40:19.520885 Unsupported output device: 28 Windows WASAPI: Altavoces (2- USB AUDIO CODEC)
2024-03-11 20:40:19.520885 Unsupported input device: 34 Windows WDM-KS: Micrófono (HD Audio Microphone)
2024-03-11 20:40:19.521885 input device: 35 Windows WDM-KS: VoiceMeeter Output (VoiceMeeter vaio)
2024-03-11 20:40:19.521885 Unsupported input device: 38 Windows WDM-KS: Línea (USB AUDIO CODEC)
2024-03-11 20:40:19.521885 Unsupported input device: 41 Windows WDM-KS: Mic 1 (Virtual Cable 1)
2024-03-11 20:40:19.521885 Unsupported input device: 42 Windows WDM-KS: Line 1 (Virtual Cable 1)
2024-03-11 20:40:19.521885 Unsupported input device: 43 Windows WDM-KS: S/PDIF 1 (Virtual Cable 1)
2024-03-11 20:40:19.521885 input device: 44 Windows WDM-KS: CABLE Output (VB-Audio Point)
2024-03-11 20:40:19.521885 output device: 36 Windows WDM-KS: Speakers (VoiceMeeter vaio)
2024-03-11 20:40:19.521885 Unsupported output device: 37 Windows WDM-KS: Altavoces (USB AUDIO CODEC)
2024-03-11 20:40:19.521885 Unsupported output device: 39 Windows WDM-KS: Output (AMD HD Audio HDMI out #0)
2024-03-11 20:40:19.521885 Unsupported output device: 40 Windows WDM-KS: Line Out (Virtual Cable 1)
2024-03-11 20:40:19.521885 output device: 45 Windows WDM-KS: Speakers (VB-Audio Point)
2024-03-11 20:40:19.839451 internet: init: info: trying to bind udp source port: 61791
2024-03-11 20:40:19.839451 internet: init: info: UDP socket initialized on source port 61791
2024-03-11 20:40:19.841455 internet: server launcher: info: retrieving server list
2024-03-11 20:40:19.951971 soundcard online.
2024-03-11 20:40:24.896482 internet: server launcher: warning: could not get DNS

[RandyW]

I sent you the log, does it seem like a DNS problem?

2024-03-11 20:40:19.841455 internet: server launcher: info: retrieving server list
...
2024-03-11 20:40:24.896482 internet: server launcher: warning: could not get DNS

It certainly appears to be related to DNS. That would exactly explain your symptoms. The 5 second delay between "retrieving server list" and "could not get DNS" suggests a response is simply not being received.

DNS worked from google's public DNS server:

Code: Select all

$ dig @8.8.4.4 servers.rmnoise.com TXT

; <<>> DiG 9.16.48-Ubuntu <<>> @8.8.4.4 servers.rmnoise.com TXT
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30434
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;servers.rmnoise.com.           IN      TXT

;; ANSWER SECTION:
servers.rmnoise.com.    600     IN      TXT     "rmnoise1.rmnoise.com:11109,rmnoise2.rmnoise.com:11109,rmnoise3.rmnoise.com:11109"

;; Query time: 60 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: Mon Mar 11 15:48:09 CDT 2024
;; MSG SIZE  rcvd: 141

[EA2ESB]

Ping works correctly.

I don't understand something well.

Thanks, I'll keep trying.

[RandyW]

In windows, you need to use nslookup to retrieve a TXT record:

Code: Select all

C:\Users\randy>nslookup
Default Server:  UnKnown
Address:  192.168.175.1

> set type=txt
> servers.rmnoise.com.
Server:  UnKnown
Address:  192.168.175.1

Non-authoritative answer:
servers.rmnoise.com     text =

        "rmnoise1.rmnoise.com:11109,rmnoise2.rmnoise.com:11109,rmnoise3.rmnoise.com:11109"

[EA2ESB]

Microsoft Windows [Versión 10.0.22631.3235]
(c) Microsoft Corporation. Todos los derechos reservados.

C:\Windows\System32>nslookup
Servidor predeterminado: UnKnown
Address: 212.230.135.1

> set type=txt
> servers.rmnoise.com
Servidor: UnKnown
Address: 212.230.135.1

Respuesta no autoritativa:
servers.rmnoise.com text =

"rmnoise1.rmnoise.com:11109,rmnoise2.rmnoise.com:11109,rmnoise3.rmnoise.com:11109"
>

It seems that there is no problem connecting to the servers from my PC, for whatever reason it blocks it from the application.

Do you share this opinion with me?

[RandyW]

I'm now wondering if a your virus scanner might be blocking those DNS requests from RM Noise, but not from nslookup. You could experiment with temporarily disabling your virus scanner...

[EA2ESB]

It was the first thing I tried, it didn't work, it's still disabled. Is there any evidence that it works correctly in any Windows 11?

[RandyW]

It was the first thing I tried, it didn't work, it's still disabled. Is there any evidence that it works correctly in any Windows 11?

Yes