The best general method for setting up VNC on any NT family OS is the following, done with a clean install preferably:
<quote src="Floyd Russell"> "1. Install VNC 2. Install VNC Service 3. Start->Programs->VNC->Run WinVNC(AppMode) 4. Enter your password, this is for the current user. 5. Start->Programs->VNC->Administrative Tools->Show Default Settings 6. Enter your password, this is for the local machine 7. Close WinVNC 8. Start WinVNC Service You may need to start the service helper if you want to modify settings of the winvnc instance running. This problem is due to the way Terminal Services operates, since you are working in a virtual desktop." </quote> ----- Original Message ----- From: "geo carlsone" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, 2002-06-01 10:40 Subject: Problems connecting to xp with firewall and other security settings > Our location has XP on machines in a lab that is > set off by a separate firewall, and also the XPs > are configured (and this cannot change) to turn > off certain things like MS remote desktop and it turns > off > other internal firewall program settings and ports. > > None of these settings or setup can change due to > security policy. Nor can I experiment with any to > see what would work. > > I am running vnc server on this XP, and from machines > outside this lab, where I am, when I use vncserver, > I do get the prompt for password, and the vnc window > appears for 1-2 seconds, then goes away, with the > message vncviewer: VNC server closed connection > > Rarely, if I click somewhere in this window while it > is > up, I can actually operate in it for maybe a minute, > and then it goes away as before. > > I've changed the display port number, using 8080 or 80 > or various others, and that does not seem to be > the problem, as I always get the prompt for the > password > and the XP vnc window always comes up for those one or > two seconds. > > And same thing happens when I attempt to connect via > browser, > except the message in browser window when vnc window > goes away > is java.net.SocketException: Connection reset by peer. > I'm not aware of any other ports that vnc uses that > would have an effect on all this or that I might need > to change. > > > What I'd like to know is what is happening that > allows the connection at all, and then what happens > that causes it to go away ? > > I realize I've not given a lot of information as to > the > details of the lab firewall or the specifics of what > all is turned off in the XP since I don't know. > > > Thanks - mt > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com > _______________________________________________ > VNC-List mailing list > [EMAIL PROTECTED] > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
