Re: Viewing desktop from different computer same settings, won't connect

On Wed, 6 Jun 2018 14:03:24 -0700 (MST) alowe <[email protected]> wrote:

> I have a desktop computer with no keyboard or screen. The only way to access
> it is via remote. It's set up to run TightVNC server on startup and I've
> been successfully accessing it via a laptop for about a year.
>
> Unfortunately that laptop died so I am now using TightVNC viewer from a
> newer laptop. I managed to get the settings used from the old laptop's hard
> drive so I know they are identical. Even manually set the IP and gateway on
> the new laptop to same as old one. And I added an exception to the laptop so
> it accepts TightVNC. The desktop has no firewall.
>
> When I connect the Ethernet cable and run TightVNC viewer with the settings
> that previously worked for the last year it returns an error:
>
> 192.168.1.1:5900 - TightVNC Viewer
> Error in TightVNC Viewer: No connection could be made because the target
> machine actively refused it.
>
> The only difference between now and when it used to work is the version of
> TightVNC viewer is 64bit and the old version was 32bit.
>
> When I ping the desktop on 192.168.1.1 is responds immediately with 0% loss.
> So, I'm out of ideas. I don't understand why the desktop would refuse to
> connect to a computer with the same IP address it used to connect to just
> fine.
>
> The only other thing I could try would be to uninstall TightVNC 64bit and
> try TightVNC 32bit but I don't see any logical reason why that would make
> any difference.
>

The only thing I can think of is that your VNC server is not actually listening
on 5900.  If your viewer computer is Linux (or Windows with telnet installed),
try the following where ccarter should be your VNC server hostname or IP:

> telnet ccarter 5900
Trying 192.168.0.60...
Connected to ccarter.
Escape character is '^]'.
RFB 003.008

My server is x11vnc, but you should get some response.  If it doesn't connect
you've got a problem on the viewer end, or a firewall on either server or viewer
end is not permitting 5900. 

If you can ssh to the VNC server (or hook up kybd/monitor), do the following as
root:

# lsof -i 4 -a | grep 5900
x11vnc     1613      root    9u  IPv4     14759      0t0  TCP *:5900 (LISTEN)

If that doesn't work, and if you're sure VNC Server is running, grep for the
name of the VNC server program (I don't know what it's called) instead of port
5900. Maybe it's listening on a different port.

--Mark

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___________________________________________________________
TightVNC mailing list, [email protected]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list