Unable to connect to client PC

Here you will find help for frequently asked questions as well as for your specific question.

Unable to connect to client PC

Postby superjennyradio » 2021-07-29 14:24

I work for a small radio station and we recently had a power outage at our studios. The outage caused a host of problems, among them being IP Address issues within our automation network where we typically use static IPs. Once we re-established the proper IP addresses our VNC has been unable to connect to one of the PCs. (The most important one, of course) I have verified that port 5900 and 5800 are open. (It looks like our settings are set to "auto" for incoming connections, though) I can also ping that PC from the server PC from where we're trying to access it. Windows Firewall rules are set to allow both 5800/5900 from any local or remote address with TCP. I tried to connect by computer name (our typical way) and by IP address and neither work.

This machine is also sending data to a streaming PC for our online audio stream. I briefly switched the Incoming connections setting for specifically ports 5900 & 5800, then back to auto. We lost our online stream around the same time. It may have been coincidental as we've been having multiple issues due to the power outage. Long story, but at the time none of our stuff was actually protected by a battery back-up. We lost that a couple of weeks prior and were waiting for a replacement.

With all of that in mind, does anyone have any ideas? I'm not an expert in IT in any way, so I'm a little out of my depth at the moment.

Any help is appreciated.
Posts: 1
Joined: 2021-07-29 14:04

Re: Unable to connect to client PC

Postby Bonji » 2021-08-03 13:47

The only thing that jumps out to me is that you have static IPs and had to manage them lately. If you can, shut down the computer you are trying to connect to, and then try pinging that IP again to see if you still get a reply. If so, that would mean you have two devices using the same IP. Just enabling the firewall to block ICMP is not good enough because the switching/routing infrastructure may be directing traffic to one or the other device and you don't easily know.

If shutting down the computer is not an option, you can verify the VNC client computer is talking to the correct server. If both computers are on the same subnet, from the client you can run the command 'arp -a' in a command prompt (after successfully pinging the server) to list and verify the MAC address of the server computer to ensure you're talking to what you think you are talking to.

If you determine traffic routing isn't the problem, then it would seem to be a problem with the VNC server computer.
Posts: 339
Joined: 2008-05-13 14:54

Return to General help

Who is online

Users browsing this forum: Bing [Bot] and 13 guests