Wez - thank for your reply - to follow the points through: "This is incorrect. The Java and native VNC Viewers are interchangeable. The most common cause of issues with the Java Viewer is the use of a separate port for serving the Java Viewer from the one used for the VNC protocol."
I'll look into this as it may solve the problem I posted this morning re "Unable to connect using a browser". Don't know where to start looking though so any tips would be helpful. I'm assuming I still use ports 590x and 580x etc to communicate to the VNC software in both user and service mode? "This shouldn't happen. Which platform is your laptop running? Basically, there is no way that any application should be able to blue-screen your machine unless the operating system or drivers are broken in some way." The laptop details are as follows: HARDWARE Sony VAIO VGN-A117S Model Number PCG-8Q4M running Centrino 1.7GHz processor.2Mb Cache memory 512 MB DDR SDRAM 80GB Hard Drive Graphics: ATI Mobility RADEON 9700 with 64MB VRAM SOFTWARE Windows XP (Home Edition) running Service Pack 2 I've had this machine for 2 weeks from new and have installed SP2 so this is different from the original configuration. I'll check out the Sony Web site for updates related to SP2 and let you know if this solves the problem - Am I correct to suspect video drivers ? "Port 80 is not used by the VNC protocol, by default, nor to server the Java Viewer." I got this from the article below: http://faq.gotomyvnc.com/fom-serve/cache/77.html I tried it as part of the process of eliminating the problems I'll keep trying Thanks again for your help on all this Tony Frost James Weatherall <[EMAIL PROTECTED]> wrote: Tony, > >From this I'm assuming that the viewer is only used to > communicate in "User Mode" and that a browser is only used to > communicate in "Service Mode". Sorry to all those experts who > are now falling about laughing but it wasn't obvious to me > and I still don't know if this is correct. But it works for > me as they say. This is incorrect. The Java and native VNC Viewers are interchangeable. The most common cause of issues with the Java Viewer is the use of a separate port for serving the Java Viewer from the one used for the VNC protocol. > OK moving on !!! So I now had connection (for a shot time at > any rate). The problem was that having run the viewer on my > PC it was causing my Laptop - running the server (in User > Mode :o) ) - to "blue screen" and re-boot. Not exactly a > practical solution to remote access. This shouldn't happen. Which platform is your laptop running? Basically, there is no way that any application should be able to blue-screen your machine unless the operating system or drivers are broken in some way. > Firewalls - I had my gateway firewall enabled and the XP and > Norton Internet Security Firewalls disabled on both the > laptop and PC. I have reactivated the NIS with no adverse > effect and for those who have come across it I have NOT had > to remove port 80 from the list of scanned ports in NIS - > although this may be an issue when I connect through the > Internet and my gateway. Port 80 is not used by the VNC protocol, by default, nor to server the Java Viewer. > Window XP issues - I have disable "Fast User Switching" but > thinks still work with it enabled provided I log out of each > user - I have multiple users on each machine - so in effect I > don't use the facility. Yes. We tend to recommend turning it off entirely purely so that you don't try to connect in to your XP box and find it won't work because somebody else has FUSed it, or that you don't connect in and forget about FUS and lock yourself out. Related to that, an XP compatibility module is in development. Cheers, Wez @ RealVNC Ltd. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
