Well these are just remote possibilities here.. I only mention these because
you say that you could connect TO the same VNC server, FROM a workstation
that was not a domain member. This suggests to me that you have an issue
executing/opening a connection/resolving from the client, not an issue
receiving the connections on the VNC server. 

There are a couple possibilities;

If the application doesn't run at all, perhaps there is a software
restriction policy in place. (perhaps the domain admin(s) don't want people
running VNC viewers?)  Or, there could be a GPO enforced windows firewall
setting. There are a host of possibilities, not knowing your environment
it's hard to say - if you're not the admin, that would be a good place to
start anyway!

If it runs, but disappears indefinately when you hit the 'OK' button after
entering the host name, perhaps it is hanging up resolving the hostname.
Maybe there is something wrong the DNS in the domain? The non-domain client
could have different DNS settings, or could be using WINS, etc etc. If you
know the actual IP of the server, test this by trying to connect to the
server from the 'non-working' system, but use the IP address instead of the
hostname. If it works, then your admins have some work to do fixing their
internal DNS. 




-----Original Message-----
From: Chris Keitel [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 27, 2006 12:30 AM
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: Re: VNC Viewer 4.2.5 disappears

But I can connect to many other remote servers that are configured in
seemingly the same way with no problem.  What specifically am I looking for
in terms of Group Policy settings?

It can't be anything that would cause a complete block to the VNC program
because this problem only occurs between our corporate domain and this
sepcific server.

Is there anyway to find out what VNC viewer is doing when it disappears?
Does it log what it is attempting and what is is failing at?

Thanks,
Chris K

On 7/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> You could be on to something with the domain-issue there. But probably 
> not what you seem to think... Try asking your systems administrator 
> (whoever is in charge of your domain's Group Policy) if they have 
> configured Group Policy for those systems that might be blocking the 
> VNC application, or perhaps a windows firewall policy, or something 
> else like that. Such things would not apply to a system in a workgroup.
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> On Behalf Of Chris Keitel
> Sent: Wednesday, July 26, 2006 3:34 PM
> To: [email protected]
> Subject: VNC Viewer 4.2.5 disappears
>
> I'm having a problem with the Personal Version of RealVNC Viewer 
> 4.2.5.  I'm running the Personal Edition of the server (4.2.5) on 
> several different Windows XP SP2 computers in remote locations connected
by different ISPs.
>
> When I try to connect to one of the servers from my computer the VNC 
> application disappears from sight as soon as you click OK to open the 
> connection.  The process is still running in Task Manager and you can 
> open as many attempts as you want.  When I put the computer to sleep 
> or otherwise interrupt the internet connection, all of these processes 
> will come back with error messages saying the connection was closed and
then die.
>
> Fine.  However I can connect from another computer in my office with 
> an IP address on the same subnet.  It works as you would expect.  The 
> only difference between the computers is that the one that doesn't 
> work is on a Windows domain, and the one that does work is configured 
> as part of a workgroup.  I have tried this on another computer which 
> IS part of the domain (and it doesn't work) so I am wondering if I am 
> on to something.  Is this a known issue?
>
> Furthermore, at first the logs on the remote computer indicated
> "Connections: closed 193.251.51.217::2815 (Requested security type not 
> available.)"
> This seemed to be a lead, however it does not produce these warnings 
> any longer.  In fact there is no record of any connection attempts any 
> more, but the symptoms are the same.
>
> Can anyone help?
>
> -Chris K
> _______________________________________________
> VNC-List mailing list
> [email protected]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
> _______________________________________________
> VNC-List mailing list
> [email protected]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to