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!
uwmdesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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
Managing Security Policy in a Changing Environment

The enterprise network environment is evolving rapidly as companies extend their physical data centers to embrace cloud computing and software-defined networking. This new reality means that the challenge of managing the security policy is much more dynamic and complex.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.