That's definitely not the problem I'm getting ... I just logged in successfully today after failing yesterday, and I *do* have other logons running on XP.
I had logged as myself last night at home directly on the XP machine. This is the only change in status that I can think of. As such, I'd guess that the problem does relate to user state at the XP machine in some way. D> --- Angus Macleod <[EMAIL PROTECTED]> wrote: > I have found (with RealVNC 3.3.6 and TightVNC 1.2.6) > that if you connect to > an XP machine running VNC server that if there is > already a second log on > (i.e. user switching has been used), you will get a > black screen. If you log > on as the second user, as soon as your logon is > processed, the VNC > connection will be dropped, and subsequent > reconnections get the black > screen. It must be something to do with the way XP > handles the screens of > "background" users. If the extra logged on users log > off (bringing the logon > count down to 1 or 0), then VNC will see the desktop > again as usual. > > Angus. > ----- Original Message ----- > From: "David Gurr" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, March 11, 2003 5:41 AM > Subject: Re: Black screen in VNC and Terminal > Services > > > > I have a similar problem. I have an XP Pro system > at > > home running VNC Server. When I connect to it from > > work, sometimes it works fine, and sometimes I get > the > > black screen. > > > > This happens when using the vncviewer on Win95, > and > > when using it on Linux. > > > > I've often had it working fine one day, and the > next > > it fails, despite their being no reboots or > console > > logins at the server end. > > > > Restarting the server sometimes cures it, but > often > > doesn't. It'll then just start working again by > itself > > sometime later. > > > > For the record, I'm using 3.3.6 on server and > client. > > Sometime soon I'll try upgrading to 3.3.7. > > > > D> > > > > From: "Craig Cardinet" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Subject: Black screen in VNC and Terminal Services > > Date: Mon, 10 Mar 2003 10:37:27 -0600 > > > > I've searched through the topics and found quite a > few > > similar issues, > > but > > nothing that quite addresses the problem that I'm > > having. I use W2K > > Pro (at > > home) to connect to my office using both VNC and > > Terminal Services, > > depending. It's worked fine for months. Last > week, I > > attempted to > > connect > > to my pc at the office (W2K Pro), but I had left > my > > screen saver on, > > and > > after seeing a brief flash of the ss, got nothing > but > > a black screen. > > Trying to send C-A-D does nothing. I then tried > to > > connect to a W2K > > server > > pc through Terminal Services (as I've done 100 > times > > before, > > successfully) > > and I get the same black screen. I've uninstalled > VNC > > and TS - same > > thing. > > I can connect to the same pc's using both VNC and > TS > > from other remote > > pc's, > > no problem. Any suggestions? > > > > > > > > __________________________________________________ > > Do You Yahoo!? > > Everything you'll ever need on one web page > > from News and Sport to Email and Music Charts > > http://uk.my.yahoo.com > > _______________________________________________ > > VNC-List mailing list > > [EMAIL PROTECTED] > > http://www.realvnc.com/mailman/listinfo/vnc-list > > > __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
