Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1130
  • Last Modified:

Enable UltraVNC to connect across subnets

We have multiple Win XP machines on site on 2 different subnets.  We recently upgraded our UltraVNC software from version 1.0.2 to 1.0.5.  We added the software to our PC image so that when we reimage a machine, VNC is installed and we can remote connect to it.  Unfortunately, unless the reimaged PC is on the same subnet as the computer we're connecting from, we cannot connect to the computer.  

Any ideas where to look?  Firewall ports are open on the reimaged machines.  We're clearly missing a step in the setup that we lost in the upgrade.  

Thanks!
0
uwmdes
Asked:
uwmdes
  • 3
  • 2
1 Solution
 
nick2253Commented:
By your comments, I'm assuming that two computers on the same subnet can connect just fine?  If they can't connect, then there may be a problem with the VNC install on the image.

--Nick
0
 
uwmdesAuthor Commented:
That's correct. Two computers on the same subnet can connect just fine.
0
 
nick2253Commented:
Can the computers on the different subnets ping each other?

--Nick
0
NEW Internet Security Report Now Available!

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out this quarters report on the threats that shook the industry in Q4 2017.

 
javiersantanaCommented:
Well, you would need to create a default route in your routing table in order for the 2 separate subnets to communicate with each other. You can either do this on your device that controls network layer protocols or you can create persistent routes on each workstation individually.

Was this working before the upgrade?
0
 
uwmdesAuthor Commented:
Pinging the computer on the different subnet works fine.  Also, we still have a number of machines with the old version of UltraVNC running on the other subnet that can be connected to just fine (both through pinging and UltraVNC).  I checked the Admin settings for UltraVNC on an existing machine and on one of the reimaged machines, and they appear to match.  The firewall settings also appear to match.  

All of this was working before the upgrade.  There are 2 variables though.  One is the UltraVNC upgrade.  The other is the fact that we reimaged the machine, so all of the firewall settings had to be reapplied - hopefully correctly.  Though, again, between an existing machine and a newly reimaged machine, the settings appear to be the same.
0
 
uwmdesAuthor Commented:
We figured it out.  The way we were reopening the ports after reimaging was by using netfw.inf and calling "netsh firewall reset" on startup.  The instructions we found for altering netfw.inf included setting the open ports to "LocalSubnet" rather than "*" which allows them to be accessible from any subnet.  Changing this fixed the problem.  Thanks anyway for your help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now