Cant connect to VNC via local network

[angrynerdrock]

Using RealVNC Server/Viewer. I can connect via cloud connections, but trying to connect to any machine via its local IP address I get "The connection was refused by the computer".

Connecting via cloud isn't really going to help my overall goal. I work from home and have a work computer that is able to be controlled via VNC (I have had it working in the past). I wish to do this if I want to get up from my desk, I can continue working on everything via my laptop. I also have a personal machine that I want to connect to via VNC from time to time. This one has RealVNC server and is the one I can connect to via cloud connection. Typing its local IP gets the connection refused message. I don't know which VNC server is running on the work computer but RealVNC Viewer has connected to it just fine in the past. What steps should I take to figure out why I cannot connect via local ip?

Windows Firewall on local personal pc-
Off-get connection refused
On with exceptions for VNC and port 5900-connection timed out

Cant do RDP, work computer only allows VNC as its a thin client and connects to a remote pc via VMWARE.

Router- Netgear R6300v2, no firewall settings that I can find or change.

 

[bruceb]

See if this is of help: (may need to change the work computer to be sure service is always started)
https://support.realvnc.com/knowled...e-connection-was-refused-by-the-host-computer

Also be sure you have the latest version of the VNC client. Also on the computers be sure when you ran the vncserver command after installing the server and set the password, that you were on the account you intend to use to login.

 

[JackMDS]

If you want to connect from home you can not use local IP. The work site computer VNC Server has to be configured for connection through the Internet and if it the differentiation between the local computer is not done by their local IP but by using individual port assign to each computer.

I.e., works IT has to give you the info about it.

Read this page under Using VNC to Control a specific LAN Computer through the Internet there is a simple explanation for it.

 

[angrynerdrock]

See if this is of help: (may need to change the work computer to be sure service is always started)
https://support.realvnc.com/knowled...e-connection-was-refused-by-the-host-computer

Also be sure you have the latest version of the VNC client. Also on the computers be sure when you ran the vncserver command after installing the server and set the password, that you were on the account you intend to use to login.

Ya, updated software, still nothing. Had already read that article too.

If you want to connect from home you can not use local IP. The work site computer VNC Server has to be configured for connection through the Internet and if it the differentiation between the local computer is not done by their local IP but by using individual port assign to each computer.

I.e., works IT has to give you the info about it.

Read this page under Using VNC to Control a specific LAN Computer through the Internet there is a simple explanation for it.

I should clarify. VNC server is installed on the thin client, not the remote computer. So I can connect over the local network via VNC to the thin client and see/control anything its displaying (the remote computer). I know this because I have had it working in the past. If it was working on my personal computer and not the work computer, I'd chalk it up to being an issue with the work computer, but seeing as the personal computer has the same issue it makes me believe there is an issue somewhere else.

 

[mxnerd]

Why not try Teamviewer? Noting to setup or configure port forwarding.

If you want to use VNC, at least find out what port the VNC server is using first,

just saying it works in the past does not reveal the whole picture.

And what do you mean the work PC is a thin client that connet to remote PC via VMware?

Your description about work PC, personal PC, thin client, remote access , LAN access all messed up, you better sketch the whole network setup.

 

[angrynerdrock]

Why not try Teamviewer? Noting to setup or configure port forwarding.

If you want to use VNC, at least find out what port the VNC server is using first,

just saying it works in the past does not reveal the whole picture.

And what do you mean the work PC is a thin client that connet to remote PC via VMware?

Your description about work PC, personal PC, thin client, remote access , LAN access all messed up, you better sketch the whole network setup.

By thin client, I mean its a HP T610 thin client
https://www.walmart.com/ip/HP-Thin-...12=378316942_10000008862&wl14=hp t610&veh=sem

Its a low powered machine that facilitates remote access to a virtual computer remotely (on work servers) via VMware. I cannot access the virtual computer with anything aside from the work provided thin client. The thin client does, however, have a VNC server installed on it so I can control it via my laptop over local network (if it would connect that is)

How do I track down what port its using? In the past I would just have to enter the local IP and itd connect

 

[mxnerd]

I see.

Use a network port scanner then.

Like this one. https://www.techspot.com/downloads/6478-free-port-scanner.html

Enter the IP & port range and start scanning.

==

But if the thin client is provided by the company you work for, the IT dept should be able to provide the info you need. And make sure you have the correct password.

 

[angrynerdrock]

I see.

Use a network port scanner then.

Like this one. https://www.techspot.com/downloads/6478-free-port-scanner.html

Enter the IP & port range and start scanning.

==

But if the thin client is provided by the company you work for, the IT dept should be able to provide the info you need. And make sure you have the correct password.

Its showing ports 5900-5909 are all closed on both machines. I added an exception in the firewall, still no luck. Still closed

 

[mxnerd]

Its showing ports 5900-5909 are all closed on both machines. I added an exception in the firewall, still no luck. Still closed

Which 2 machines? Expand the upper range to 6000 and run it again.

Do you want to remote control the thin client and your PC from your laptop via VNC? Is that what you want to achieve?

If that's the case, you have to set firewall incoming exception on your PC and thin client, not your laptop.

But since your thin client probably is not Windows based, I don't know what you can do about it.

Consult your company and they should be able to help. At least you are not trying to hack, right?

I wonder whether your company remotely turn off VNC service though.

 

[angrynerdrock]

Which 2 machines? Expand the upper range to 6000 and run it again.

Do you want to remote control the thin client and your PC from your laptop via VNC? Is that what you want to achieve?

If that's the case, you have to set firewall incoming exception on your PC and thin client, not your laptop.

But since your thin client probably is not Windows based, I don't know what you can do about it.

Consult your company and they should be able to help. At least you are not trying to hack, right?

I wonder whether your company remotely turn off VNC service though.

Yes I want to control the PC and Thin Client from my laptop.

I did set the firewall exception on the PC, it still wont connect aside from a cloud connection. Port scanner from port 5900-6000 showed ports were closed.

 

[mxnerd]

If you can connect to your PC from internet, you must have setup port forwarding in the router. Find what port you configured in the R6300v2 router.

Yet you said you can't connect from LAN, that's weird if you already set firewall exception.

==

Haven't used RealVNC for many, many years.

Now you have to create account and buy subscription to access from the cloud? http://www.realvnc.com

I only use TightVNC (Server/Viewer) locally. I thought RealVNC operates like TightVNC. But it seems not.

Maybe you can try TightVNC on port other than 5900 on the same machine.

==

By the way, did you create firewall exception on Private network profile?

 

[mxnerd]

Seems HP thin client VNC capability is now disabled by default. Can only be enabled on server.

https://support.hp.com/ee-en/document/c03837090

 

[angrynerdrock]

If you can connect to your PC from internet, you must have setup port forwarding in the router. Find what port you configured in the R6300v2 router.

Yet you said you can't connect from LAN, that's weird if you already set firewall exception.

==

Haven't used RealVNC for many, many years.

Now you have to create account and buy subscription to access from the cloud? http://www.realvnc.com

I only use TightVNC (Server/Viewer) locally. I thought RealVNC operates like TightVNC. But it seems not.

Maybe you can try TightVNC on port other than 5900 on the same machine.

==

By the way, did you create firewall exception on Private network profile?

Installing TightVNC fixed the issue on the personal machine, even allowing RealVNC to connect via local IP address. Odd.

 

[angrynerdrock]

Seems HP thin client VNC capability is now disabled by default. Can only be enabled on server.

https://support.hp.com/ee-en/document/c03837090

Dang, guess it was nice while it worked. Now tethered to my desk lol

 

[angrynerdrock]

So I swapped out the thin client for a spare one I have, and VNC is working on the work machine (both on the LAN and to the internet)

 

[mxnerd]

Glad it worked out for you.

===

Found RealVNC is free for personal home use up to five devices. Only through cloud however, must register and create account on their website.