Re: [suse 8 | vncviewer] F8 Not working...

2003-11-14 Thread mrinvader
Lets see *Certain other companie$* have prompt service like that!! Thanks
Tristan, it worked!

On Fri, 14 Nov 2003, Tristan Richardson wrote:

> This sounds like a bug in the 4.0b4 unix viewer whereby the F8 menu
> won't pop up when either caps lock or num lock are on.  The following
> simple patch should fix it:
>
>
> *** CConn.cxx.orig Thu Sep  4 14:04:40 2003
> --- CConn.cxx Fri Oct 24 10:29:45 2003
> ***
> *** 134,140 
> case KeyPress:
> case KeyRelease:
>   XLookupString(&ev->xkey, str, 256, &ks, NULL);
> ! if (ks == menuKeysym && ev->xkey.state == 0) {
> if (w == desktop && ev->type == KeyPress) {
>   showMenu(ev->xkey.x_root, ev->xkey.y_root);
>   break;
> --- 134,140 
> case KeyPress:
> case KeyRelease:
>   XLookupString(&ev->xkey, str, 256, &ks, NULL);
> ! if (ks == menuKeysym && (ev->xkey.state & (ShiftMask|ControlMask)) == 0) {
> if (w == desktop && ev->type == KeyPress) {
>   showMenu(ev->xkey.x_root, ev->xkey.y_root);
>   break;
>
>
-- 
Yours,
Charles T. Houghtby IV
IT Manager, Rapid Appraisal, INC
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Re: Can't connect to Win 2000 machine when remote computer is locked

2003-11-14 Thread Nigel Baker
The problem only seems to exist in Ver 3.3.7 of VNC. Use version 3.3.6 and
it works fine.
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


DOS command window problem for Windows 2000

2003-11-14 Thread Crewdson, Dave
I have seen several people in the past commenting that they have no cursor
control in DOS windows when using VNC.
 
The only solution I saw was to click "command prompt" instead of
Start..Run...cmd.  This does not work for me.  
 
I am running VNC from Windows XP to log into a Windows 2000 machine.  The
DOS window appears but typing in it or pressing ENTER is very sporadic. 
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


RE : Can't connect to Win 2000 machine when remote computer is locked

2003-11-14 Thread Seak, Teng-Fong
Is VNC server registered as a service?

> -Message d'origine-
> De : Nigel Baker [mailto:[EMAIL PROTECTED] 
> Envoyi : vendredi 14 novembre 2003 17:38
> @ : [EMAIL PROTECTED]
> Objet : Can't connect to Win 2000 machine when remote 
> computer is locked
> 
> 
> I cannot connect to the remote Windows 2000 machine if it has 
> been locked using the Task Manager->Lock Computer function 
> (remote computer is still logged on, just locked). If the 
> computer is not locked then VNC works fine. Using version 3.3.7
> 
> Start VNC Viewer from the remote machine. Password prompt 
> appears. Enter password. Password dialog box closes then 
> nothing. 
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Re: Can't connect to Win 2000 machine when remote computer is locked

2003-11-14 Thread Nigel Baker
The VNC server is running as a system service on the remote machine.

I cannot connect to the remote Windows 2000 machine if it has been locked
using the Task Manager->Lock Computer function (remote computer is still
logged on, just locked). If the computer is not locked then VNC works fine.
Using version 3.3.7

Start VNC Viewer from the remote machine. Password prompt appears. Enter
password. Password dialog box closes then nothing.
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Re: Can't connect to Win 2000 machine when remote computer is locked

2003-11-14 Thread William Hooper
Nigel Baker  said:
> I cannot connect to the remote Windows 2000 machine if it has been locked
> using the Task Manager->Lock Computer function (remote computer is still
> logged on, just locked). If the computer is not locked then VNC works
> fine.
> Using version 3.3.7

http://www.realvnc.com/faq.html#ctrl-alt-del
"If you're running the VNC server as an application under Windows
NT/2000/XP then it can only provide remote access to the display if a user
is logged in and the workstation is not locked. In order to allow the
Ctrl-Alt-Del keypress to work and be accessed even if no user is logged in
or it is locked, you must run the VNC server as a system service."

-- 
William Hooper
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Re: [suse 8 | vncviewer] F8 Not working...

2003-11-14 Thread Tristan Richardson
> On Tue, 11 Nov 2003 [EMAIL PROTECTED] wrote:
>
> > Hi All!
> > I have 4.0b4, compiled from source, on SuSE linux 8.0. I am having
trouble
> > with the F8 menu not showing up... i tried doing a manual modification
of
> > the .Xresources file to put in a custom menu (i used the sample), and it
> > did not work in 4.0b4, but worked in 3.3.7. I also tried manually
> > specifying different F-keys, no luck there either. any ideas?

This sounds like a bug in the 4.0b4 unix viewer whereby the F8 menu won't
pop up
when either caps lock or num lock are on.  The following simple patch should
fix it:


*** CConn.cxx.orig Thu Sep  4 14:04:40 2003
--- CConn.cxx Fri Oct 24 10:29:45 2003
***
*** 134,140 
case KeyPress:
case KeyRelease:
  XLookupString(&ev->xkey, str, 256, &ks, NULL);
! if (ks == menuKeysym && ev->xkey.state == 0) {
if (w == desktop && ev->type == KeyPress) {
  showMenu(ev->xkey.x_root, ev->xkey.y_root);
  break;
--- 134,140 
case KeyPress:
case KeyRelease:
  XLookupString(&ev->xkey, str, 256, &ks, NULL);
! if (ks == menuKeysym && (ev->xkey.state & (ShiftMask|ControlMask)) ==
0) {
if (w == desktop && ev->type == KeyPress) {
  showMenu(ev->xkey.x_root, ev->xkey.y_root);
  break;


Cheers

Tristan
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Re: [suse 8 | vncviewer] F8 Not working...

2003-11-14 Thread mrinvader
Oh and btw, i just downmloaded 4.0b3 src and F8 works. any help with 4.0b4
would be appreciated.

On Tue, 11 Nov 2003 [EMAIL PROTECTED] wrote:

> Hi All!
> I have 4.0b4, compiled from source, on SuSE linux 8.0. I am having trouble
> with the F8 menu not showing up... i tried doing a manual modification of
> the .Xresources file to put in a custom menu (i used the sample), and it
> did not work in 4.0b4, but worked in 3.3.7. I also tried manually
> specifying different F-keys, no luck there either. any ideas?
>
>
>

-- 
Yours,
Charles T. Houghtby IV
IT Manager, Rapid Appraisal, INC

---
During a grouse hunt in North Carolina two intrepid sportsmen
were blasting away at a clump of trees near a stone wall.  Suddenly a
red-faced country squire popped his head over the wall and shouted,
"Hey, you almost hit my wife."
"Did I?"  cried the hunter, aghast.  "Terribly sorry.  Have a
shot at mine, over there."

--

"Oh" my new operator calls as I leave, "I can't remember what your backup
tape looked like. Is this it here on the Bulk Eraser?"
--The Last BOFH
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Can't connect to Win 2000 machine when remote computer is locked

2003-11-14 Thread Nigel Baker
I cannot connect to the remote Windows 2000 machine if it has been locked
using the Task Manager->Lock Computer function (remote computer is still
logged on, just locked). If the computer is not locked then VNC works fine.
Using version 3.3.7

Start VNC Viewer from the remote machine. Password prompt appears. Enter
password. Password dialog box closes then nothing.
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


vnc-list@realvnc.com

2003-11-14 Thread William Hooper
Please send replies to the list.

Alan Dunn  said:
> Thank you for responding.
> In the log I found this which looked like the problem zone:
>
> "Fonttranssocketunixconnect: can't connect errorno=2
> failed to set default font path 'unix/:7100'
> Fatal server error"
> could not open default font fixed"

Check that your font server (I believe Mandrake uses xfs) is running.  You
could also set the paths in the vncserver script directly to the fonts,
but then you lose the features of the font server.

> This no doubt refelects the message I get when starting vncserver which is
> "couldn't start Xvnc; trying default font path Please set correct font
> path
> in the vncserver script"

Yep, errors usually show up for a reason...

-- 
William Hooper
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Re: Apparent socket problem

2003-11-14 Thread James Weatherall
Elwin,

Check that both machines have TCP setup correctly.  If it seems to be
setup OK but doesn't work then try removing and reinstalling the TCP
stack.

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


vnc-list@realvnc.com

2003-11-14 Thread William Hooper
Alan Dunn  said:
> A linux/tightvnc newbie here.
>
> can anyone offer straightforward help?

Start by looking at the VNC log in ~/.vnc/*.log

-- 
William Hooper
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Re: Apparent socket problem

2003-11-14 Thread William Hooper
Elwin Green  said:
> When I try run vncserver on the second machine, the
> Current User Properties has the "Accept Socket
> Connections" box unchecked. If I check it and start
> vncserver again, the box appears unchecked again. The
> same thing happens with the Default Local System
> Properties.
>
> When I run vncviewer, I get an "Error Creating Socket"
> message.
>
> When I run vncviewer in Listen mode, I get this
> message: "Error creating listening daemon. (Error
> binding Daemon socket)Perhaps another VNCviewier is
> already running?"

Do you have TCP/IP installed on this machine?

-- 
William Hooper
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


Reset by peer

2003-11-14 Thread spook
I'm connecting behind companys firewall (nat included) (XP -> XP) and all goes well 
until i punch in the password.. java console gives this msg.. may b a n00b prob.. but 
so am i

java.net.SocketException: Connection reset by peer: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.(Unknown Source)
at java.net.Socket.(Unknown Source)
at rfbProto.(rfbProto.java)
at vncviewer.connectAndAuthenticate(vncviewer.java)
at vncviewer.run(vncviewer.java)
at java.lang.Thread.run(Unknown Source)
java.net.SocketException: Connection reset by peer: connect



Maksuton sdhkvposti aina kdytvssd http://luukku.com
Kuukausimaksuton MTV3 Internet-liittymd www.mtv3.fi/liittyma
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


vnc-list@realvnc.com

2003-11-14 Thread Alan Dunn
A linux/tightvnc newbie here.

I want to use tightvnc to link my win2k desktop to our mandrake linux server
(internal network). I am sure I have a session, put in the password, and I
have connection info which says I have a connection - but all I get is a
blue screen with a watch cursor - not matter how long I wait it is not going
any further. I have tried logging out at the server, or being logged on -
makes no difference.

can anyone offer straightforward help?
thanks alan dunn
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


xp home limited user no vnc

2003-11-14 Thread Conor Murphy
Has anyone managed to connect to a VNC server running on xp home under a 
limited user?? It works fine under administrator, so i suspect it has 
something to do with the user not being able to open to port 5900. Any 
ideas?

_
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


RE : Starting VNCViewer by right clicking on Machine in Network

2003-11-14 Thread Mark Smith
I have created the registry entries and the .cmd file described, but  my
Win2K system  will not run the Viewer from a right click on the network
name. The new startvnc.cmd file is located in the root directory (c:\).
Win2K displays a window and reports that it cannot locate the file "".exe,
and wants me to locate it.

Thanks for the help

- Mark


- Original Message -
> Message: 2
>  Date: Wed, 12 Nov 2003 14:29:39 +0100
> From: "Seak, Teng-Fong" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
>
> Yes, I find it very useful!
>
> I'd like to know where you'd found documentation about the use/syntax in
this particular registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\
>
> The .cmd file is used to trim off the first "\\" from %D.  Do you think
it's possible to do so without using external file?
>
> > -Message d'origine-
> > De : Michael Pellegrino [mailto:[EMAIL PROTECTED]
> > Envoyi : mardi 11 novembre 2003 20:09
> > @ : [EMAIL PROTECTED]
> > Objet : Starting VNCViewer by right clicking on Machine in
> > Network Neighborhood
> >
> >
> > I was looking for this information and having a lot of
> > trouble finding it.  My brother came up with this.  I've only
> > tested this on Windows 2000 and it works great.  Sometimes
> > the simple stuff is really elegant...
> >
> > Here is a registry key to import:
> >
> > -cut here  vnc.reg
> > Windows Registry Editor Version 5.00
> >
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\shell\VNC]
> >
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Folder\shell\VNC\command]
> > @="c:\\startvnc.cmd \"%D\""
> > --- cut here
> >
> > Here is the command file to launch VNCVIEWER - name it
> > "startvnc.cmd" or change the name in the registry key.
> >
> > cut here--- startvnc.cmd
> > set addr=%1
> > start C:\Progra~1\RealVNC\vncviewer.exe %addr:~3,-1%:5900
> > exit
> > cut heree---
> >
> > Just import the registry key, copy the above commands to a
> > file named "c:\startvnc.cmd".
> >
> > That's all there is to it.
> >
> >
> > This depends on the NETBIOS name of the computer being the
> > same as the DNS name, which is the default.
> >
> > Hope someone finds this useful.
> >
> >
> > Mike
>
> --__--__--
___
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list