Ontop of all this I was just informed that another person was able to gain access to the VNC when the machine was first relocated and turned on (the user behind the win2k nat router) and proceeded to use windows update. He lost the ability to connect upon rebooting after windows update performed a 2mb "critical update", ofcourse one doesn't really pay attention to the individual updates in these packages so I can't offer those details. The update would have covered any updates in the last 3 weeks or so (since sept 11 actually, which is when the box was last updated).
> 1, resolution of logged in user different that the default (administrator) > even the depth 16bit on one and 24bit on the other can cause this. There is no user logged in, the system is as the login screen. The connection is closed after entering the VNC password but before any screen comes up in the viewer. Also there are no resolution/depth changes when logging in anyway :( > 2, different password for the default vs current user. Only the default password has been set, no others. > 3, different reg settings for current_user vs local_machine. Settings are the same. > 4, faulty network/video card/drivers (vnc will exploit any problem with > drivers) System is fine in respect to no.4, worked fine before we relocated it. > So I suggest looking at resolution, then if that's not it edit the registry > and remove the orl group from software on the local_user. Note that when at > the login/lock/screen saver screen you will get the default (local_machine) > info and when you are at a logged in system you will be at the current_user > reg side. So if things are different either res/reg then you will get > connection closed. > > If the above doesn't work, then check the rest. > Hope this gives you a place to start. > > Steve > P.S. to change the password it is best to change the default via start -> > programs -> vnc -> administrative tools -> show default settings. > I also remove the password from current_user (via regedit) as if there is > one in default you don't need one in current user. Wish I could but vnc was the only access to the machine that would let me do that. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Gwilym Evans > Sent: Monday, October 01, 2001 9:30 AM > To: [EMAIL PROTECTED] > Subject: Connection closed (yep, again) > > > pesky ctrl key... anyway > > Hi all, > > Firstly, I've read the faq and a large portion of the list but it hasn't > helped. I know this has been discussed on the list before, it's the > "connection closed" problem again. > > 1. Viewer connects > 2. Viewer gets prompted for password > 3. Viewer enters correct password > 4. Viewer shows popup VNC Info: Connection Closed > > or > 1. Viewer connects > 2. Viewer gets prompted for password > 3. Viewer enters incorrect password > 4. Viewer shows authorisation failed popup > > Server is win2k professional, sp2. > Viewer is on any of the following: winxp, win2k, winme > Viewer is behind a netbsd ipnat NAT router, no problems with router are > apparent > Another viewer is behind a win2k nat router, same problem occurrs > Server's colour depth is set to 16bit. > Server is at login screen, happens for both fresh and for screensaver > (login.scr) > Server is in another state on a direct net connection on a different > network. > > Telnetting to the port (5900) gives: > RFB 003.003 > > This setup was working fine a few days ago. At that time the only real > difference (compared to now) is that the viewer and server was on the same > network (10.0.0.x). > > The only interactive access I currently have to the server is a command line > pipe through the web application running on the server and the other windows > mmc based tools. I can't figure out how to get any more useful information, > so if theres anything extra that would be helpful just let me know how and > I'll try and get it. > > Have a feeling I'll be racking up some long distance calls tomorrow :\ > --------------------------------------------------------------------- > To unsubscribe, mail [EMAIL PROTECTED] with the line: > 'unsubscribe vnc-list' in the message BODY > See also: http://www.uk.research.att.com/vnc/intouch.html > --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
