VNC Oddity

[Frank Merrow]

So I have a system "fmerrow" in San Diego and I am trying to VNC into a 
system "campqa36" in Campbell.  This used to work, but is now 
failing.  (Nothing has changed that I know of.)  This is all corporate 
Intranet so while there are lots or routers and switches in the way, there 
are no fire walls that I know of.

What happens is from "fmerrow" I VNC into "campqa36" and I get the initial 
screen.  However, the cursor won't follow as I move it and nothing will 
refresh.  I checked it and no I am not in "view only" mode.  The funny 
thing is it is actually working, because if I double click on something IT 
DOES OPEN, but I don't see any changes on my end.  If I close and reconnect 
I see that the application has opened, but I didn't see it open on my 
client on this end.

More oddities: fmerrow can successfully VNC into any number of other 
systems without problems including campqa35 sitting in the same lab in 
Campbell.  It isn't a network problem per se, unless it is IP specific.

If I use any other system to log into campqa36, it works fine.  Everything 
works as you would expect.

I've checked the setting on both sides, everything seems fine.  Both the 
Campbell machine (the one that works and the one that doesn't) run VNC 
3.3.3.  The San Diego machines for the most part run 3.3.6, though since it 
seems to be a fmerrow specific problem, I upgraded to 3.3.7, but it didn't 
help.

Now here is the really cool thing: while I cannot successfully VNC from 
fmerrow to campqa36, I CAN from another system VNC into campqa36 and then 
turn around and SUCCESSFULLY VNC from campqa36 into fmerrow.  (!!!)

I suspect it is something simple, but I have run out of ideas for what to 
look at.

Help.

Frank