Forum Replies Created
-
AuthorPosts
-
rempfer
ParticipantThe log I already sent is not sufficient?
I’m not trying anything unusual. I don’t even know what “an MDNS connection” is. As far as I know, NoMachine defaults to an NX/port 4000 connection-type. That’s what I’m using. Please check the log I already sent. If it is NOT what you want, I will run the experiment again with Settings > Server > Security, set log level to 9.
I do thank you for your help and am not trying to be difficult (although I feel somehow that I am doing just that). Sorry.
rempfer
ParticipantAdd’l info: Firewall is disabled on the Raspberry Pi, so port 4000 udp should go thru.
rempfer
ParticipantIt’s not a remote host. The Raspberry Pi is on the same LAN subnet as the PC attempting a connection. Somehow NoMachine not behaving on Raspbian the same way it does with other Linux distros.
I’ll keep playing with it.
Thank you, Britgirl.
— Dick Rempfer
rempfer
ParticipantThe Wayland option recommended was already set.
Actually I don’t even connect to RaspberryPi 400b:
“A connection timeout has occurred while trying to connect to ‘10.92.205.1’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.”
I can connect successfully with [remove], however.
Thanks for the help,
Dick Rempfer
-
AuthorPosts