- This topic has 3 replies, 2 voices, and was last updated 2 weeks, 3 days ago by
.
-
Posts
-
As the title states I’m having a problem where one of my computers (2013 iMac with Win10 on it) is unable to connect to my main PC (also with Win10). This hasn’t been a problem until now. I can connect fine to my Mac Air with Linux Mint on it from this machine. Also those two other machines can connect to the iMac fine as well.
The connection attempt eventually times out giving this:
A timeout error occurred while attempting to connect to (my ip here) on port “4000”. The problem could have been caused by a network issue, a firewall or NAT blocking incoming traffic, or an incorrect server address. Please check your configuration and try again.
The main PC has a display plugged into it as I know NoMachine won’t create a virtual one like [removed] does. Also I only need NoMachine to function right now so I can get into the main and start [removed] when that sometimes doesn’t start on booting the system without having to go to the main and do it directly.
I have the connection logs zip file if it’s needed.
Are all these computers on the same local network or are you connecting to them from external network? We understand that connections are like this:
Win (iMac) to Main PC (Win) – not working, giving timeout error
Win (iMac) to Linux (MacAir) – ok
Linux (MacAir) to Win (iMac) – ok
Linux (MacAir) to Main PC (Win) – ?
MainPC to Win (iMac) – ok
MainPC to Linux (MacAir) – ?It seems the problematic machine is the Windows MainPC and it’s not clear if you can connect to this machine from any of the others. Is it possible that on the MainPC there is a firewall blocking incoming connection? If you briefly disable it and then try to connect, can you?
Can you show a screenshot of the Edit panel of the connection to the MainPC?
I checked the edit panel and saw there were two IP address options so I changed back to 168.192.1.0 or whatever it was (the other one ended with a 56 I think) and now it works! Thanks for that pointer 😀
You must be logged in to reply to this topic. Please login here.