Mcafee Firwall Issue

[James Weatherall]

Tim,

You may find that there is already error information logged in the
Applications Event Log on your system, with WinVNC4 as the event source
name.

You can cause a log file to be generated by the following:

Remove the service with

	winvnc4 -unregister -stop

Re-install the service with

	winvnc4 -register -log *:file:100

Then reboot the system.

In order for this to work, there must be a TEMP directory in the root of
the system drive.  E.g. C:\TEMP.  A WinVNC4.log file will then be
generated there the next time the service starts, i.e. when the system
next boots.  The log file should include all errors & debug info.

Cheers,

Wez @ RealVNC Ltd.

> -----Original Message-----
> From: Tim Macklenar [mailto:tim "at" tmacscc.com] 
> Sent: 18 December 2003 13:31
> To: 'James Weatherall'; vnc-list "at" realvnc.com
> Subject: RE: Mcafee Firwall Issue
> 
> 
> 
> Im using the vnc4beta version.  Not sure I saw the dependancy firewall
> suggestion but will search again.
> 
> thanks
> 
> tim
> 
> 
> 
> Thanks
> 
> Tim Macklenar
> TMAC's Custom Computers
> 972.529.9620
> tim "at" tmacscc.com
> www.tmacscc.com
> 
> 
> 
> -----Original Message-----
> From: James Weatherall [mailto:jnw "at" realvnc.com]
> Sent: Thursday, December 18, 2003 6:23 AM
> To: tim "at" tmacscc.com; vnc-list "at" realvnc.com
> Subject: RE: Mcafee Firwall Issue
> 
> 
> Sorry, I meant the try icon tooltip text.
> 
> > The icon looks normal, just waiting to connect.  No messages.
> >  Is there a
> > log file that I could look in to see if VNC is seeing 
> anything on the
> > server.
> 
> Which version of VNC are you running?
> 
> Setting the dependencies to include the firewall service, as suggested
> by another user on the list, is probably the easiest quick-fix.
> 
> Cheers,
> 
> Wez @ RealVNC Ltd.