RE: PC-Anywhere

[Michael Milette]

At 08:50 AM 2001-06-27 -0400, you wrote:
>Is there a good reason NT authentication couldn't be added to the Windows NT
>VNC server?  This seems like a pretty good idea.

See http://www.rabidpenguin.org/diversions.html by Jared Smolens. There you 
will find the WinVNC NT Auth Patches to 3.3.2R6. Authenticates against NT 
but unfortunately not against the NT domain.

Never actually tried it so I can't say if it works or not.

 Michael
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: Secure VNC sessions

[Michael Milette]

At 09:35 AM 2001-07-05 +0100, you wrote:
>I know win2000 server has a single user version of Terminal Server
>in it, but has XP had this expanded to include workstation too?

Yes, but only in the professional edition, not the personal edition.

 Michael
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Help: CTRL-ALT-ESC isn't sent to client

[Michael Milette]

Hi there!

I was wondering if any of you could tell me how I could possibly send a 
CTRL-ALT-ESC from a VNC Client running on a Windows 98 platform to a host 
running a VNC Client on a Windows NT 4.0 platform? Unlike CTRL-ALT-DEL, 
there doesn't appear to be any VNC menu item which would allow me send the 
appropriate keystrokes to bring up the Windows NT Task Manager. Also unlike 
the CTRL-ALT-DEL sequence, Windows 9x has no reason to intercept the 
CTRL-ALT-ESC sequence as it doesn't do anything on that platform.

I know I can right click on the NT task bar and select Task Manager but 
there are times when the task bar just isn't visible. Any suggestions would 
be much appreciated.

        Michael Milette
TNG Consulting Inc.
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

CTRL-SHIFT-ESC (Was RE: Help: CTRL-ALT-ESC isn't sent to client)

[Michael Milette]

Oops. Sorry about that. I was actually refering to CTRL-SHIFT-ESC.

 Michael Milette
 TNG Consulting Inc.

At 08:32 AM 2001-08-07 -0400, you wrote:
>Hmm...can't help you with this because Ctrl-Alt-Esc doesn't do *anything* on
>my NT4 machine even at the console, so I can't test it.  I've always used
>Ctrl-Alt-Del and clicked "Task Manager" to bring up the task manager.
>
>-Original Message-
>From: Michael Milette [mailto:[EMAIL PROTECTED]]
>Sent: Monday, August 06, 2001 11:53 PM
>To: [EMAIL PROTECTED]
>Subject: Help: CTRL-ALT-ESC isn't sent to client
>
>
>Hi there!
>
>I was wondering if any of you could tell me how I could possibly send a
>CTRL-ALT-ESC from a VNC Client running on a Windows 98 platform to a host
>running a VNC Client on a Windows NT 4.0 platform?
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

RE: Bad Review of VNC at CNET

[Michael Milette]

Bonjour Patrice,

I have had it running with a very similar configuration to yours except 
that the CPU's were just quad Xeon 450's. I will even raise you the fact 
that it wasn't only running NT Server but NT 4.0 Terminal Server Edition 
plus MetaFrame and it worked great. I would connect remotely to MetaFrame 
and then run VNC to connect to a local machine. I have even had multiple 
sessions going by multiple users.

Of course I have see situations where programs like PatchWorks will tighten 
security to the point where almost nothing will run on a box. Even without 
PatchWorks, I seem to remember a security utility which can increase the 
level of security of your server. Set to the highest level, your system 
won't even be able to see any network.

Perhaps if you could give us some additional insight into what exactly the 
symptoms are, we might be able to provide you with a few suggestions. Give 
it a try. You will find that many people here enjoy helping each other out, 
something you don't necessarily see with commercial software. In my 
experience with commercial software, except in the case of the simplest 
problem with the users ability to use the software, tech support will 
typically act as if you are the very first person in the world to ever 
experience the problem and then will tell you that they will send a request 
to have the developers look it. This does not guaranty that it will 
actually be fixed. I have spoken to many Tech Support managers who made it 
clear to me that the first bugs to get fixed are the ones they get the most 
calls for. If you are actually the only person to ever complain about a 
real bug, they may never even look into it.

This is not to say that VNC is any better in that respect. I have been 
waiting for a bug to be fixed for about 2 years now (depleting resources 
while connecting on Windows 9x over a slow connection). However, at least 
there is an active community of end users ready and willing to help you out 
and the developer has actually looked into "the source code", confirmed the 
problem and has stated that he will try to fix it some day since it is not 
a small undertaking to correct the problem. With commercial software, you 
NEVER get to talk to the developer. For all we know, they never even see 
your bug report.

Just one word of warning: People around here get cheesed off really quick 
(probably too quick if you ask me) if you ask a question which has already 
been answered on the Frequently Asked Questions (FAQ) page. It is very 
possible that the reviewer of the VNC article at CNET did ask a question 
and was sent to the FAQ page to find the answer him/herself.

I realize that the FAQ page is there for a reason, and a good reason too. 
However for newcomers who may not be used to looking for information on the 
Internet, this can leave you with a bad taste in your mouth. First 
impressions are very important. Someone who feels good about having found 
and subscribed to vnc-list could easily be quickly discouraged when simply 
told "RTFM" or just "Read the FAQ before asking a question here!"

Hope this helps. By the way, the FAQ page can be found at 
http://www.uk.research.att.com/vnc/faq.html.

At 08:00 AM 2001-09-18, you wrote:
>VNC doesn't work against a Dell PowerEdge 6400 quad-700MHz CPU machine, 2G
>of RAM, with NT Server 4 SP 6a with security hotfixes applied, including the
>fixes highlighted by PatchWork.
>
>VNC works against an old Pentium II clone, with less memory, no brand name,
>NT4 SP5.
>
>Regards,
>Patrice Boivin
>Systems Analyst (Oracle Certified DBA)
>
>Systems Admin & Operations | Admin. et Exploit. des systhmes
>Technology Services| Services technologiques
>Informatics Branch | Direction de l'informatique
>Maritimes Region, DFO  | Rigion des Maritimes, MPO
>
>E-Mail: [EMAIL PROTECTED] 
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: Sever Side Scaling/Zooming?

[Michael Milette]

Hi Kyle,

There sure is. Go into the connection options of the WinVNC client, either 
before you connect by clicking on the "Options..." button where you enter 
then address of the host machine you want to connect to or even after 
connecting by right click the VNC button on the task bar and select 
"Connection Options", and look for the "Scale by" setting in the "Display" 
section of the dialog box. Configure as needed and click OK. That's all 
there is too it.

Hope that helps...

Michael Milette
TNG Consulting Inc.

At 10:44 AM 2001-09-18, you wrote:
>Hi,
>Is there any way of making the server scale an 800x600 desktop to 640x480?  I
>have a laptop that can only display 640x480 but all the programs I would like
>to run are only visible at 800x600.  The laptop isn't powerful enough to run
>x so it has to use svncserver (which works fine at 640x480) but it is
>incapable of scaling... Also I think this feature would be much better in the
>server anyways because it can save on bandwidth and processor time on the
>weaker computer.
>Is this type of funtionality already there?  Or is it in the works?
>Otherwise which piece(s) of source should I be diging through?
>Thanks,
>Kyle
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: Confirm Connection

[Michael Milette]

Try the TightVNC implementation (as others have recommended).

If you also need it available for desktop maintenance (without requiring to 
prompt the user), you might be able to schedule it (using the task 
scheduler) to shutdown and then re-start it up in a mode that does not 
require a response to the prompt during certain hours. Don't forget to then 
repeat the shutdown/restart process again enabling the prompt.

 Michael

At 01:04 PM 2001-11-01, you wrote:
>We are currently looking at VNC as a remote control software. It looks
>awesome in every respect except it does not appear to request a
>confirmation of connection. In our industry this is a must because of
>confidential information. Is there an add on or registry changes for NT or
>Windows 2000 that would allow a challened response or confirmation of
>connection. Any help would be greatly appreciated.
>Thanks
>-
>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
-

Re: winVNC between 95 and 2000

[Michael Milette]

Hi Alpesh,

If you wait long enough, I suspect that your Win95 client might actually 
crash your system do to a problem with Windows 9x. Try the next version of 
TightVNC (1.2.2 I think) which is due out any day now at 
http://www.tightvnc.com/. It is supposed to address the problem and is 
optimized for slow modem connections.

In the mean time, you can try changing (the Windows 2000 machine) the 
resolution of the screen and/or the number of colours on your host. A lower 
resolution and number of colours will result in less data to transmit over 
the modem. I have noticed that just changing the video mode can fix the 
problem with some video drivers which experience compatibility issues.

Last but not least, you didn't mention if there was a firewall involved 
between the two connections. This may be another area to explore for 
problems if a firewall is involved.

I know it works because I use it all the time. Hope you find some of this 
helpful.

 Michael Milette
 TNG Consulting Inc.

At 03:18 PM 2001-11-08, you wrote:
>Hi,
>I am trying to connect from a VNC viewer on Win95 to a Win 2000 machine 
>running VNC server. VNC server running as a service. The client can 
>authenticate to the server but is not getting any screen updates. It just 
>waits for the screen update.
>
>The win95 has DUN1.4. VNC release is vnc-3.3.3r9-x86-win32.
>
>Any ideas or suggestion are greatly appreciated,
>Alpesh.
>--
-
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
-

RE: ATT, Tridia, or Tight?

[Michael Milette]

Hi Erik,

You may want to ask yourself the following questions when choosing a 
version of VNC:

o  Do you want to hide the VNC icon on the task bar?
o  Do you need to prompt the user for permission to take over their screen?
o  Do you want to disable the hosts wallpaper while connected?
o  Do you need high data compression (should not be an issue on a network)?
o  Which operating systems will it be installed on? (you mentioned WinNT/2000)
o  Do you want to keep logs?
o  Do you want commercial product tech support? (TridiaVNC only)
o  Do you need encryption?
o  Will you be connecting over a slow modem connection or fast network?
o  Will you need to do file transfers?
o  Do you want Windows NT domain authentication?

I came up with the above list of questions off the top of my head taking 
into consideration what I know of WinVNC, TightVNC and TridiaVNC/Pro.

It would be nice if someone with a good knowledge of the various flavours 
of VNC could put together a comprehensive product feature comparison chart.

As I am sure other have mentioned, which ever solution you choose, be sure 
to test not only the product but test your method of changing/upgrading it 
in the future. Another area some people have had difficulty with is 
configuration and passwords. You will want to test your configuration with 
various applications and ensure that users are not able to modify the 
configuration and password information.

If you have a DNS, giving workstations an easy to remember name (like the 
username) will allow you to take over the right users screen instead of 
having to remember or lookup IP addresses. Just be sure to maintain  the 
list or you might end up trying to take over the screen of the wrong user 
due to a PC's having been swapped by your technicians during trouble 
shooting calls. This also gives you the added flexibility of allowing users 
to connect to their PC at work from home should this eventually be 
desireable. You would simply tell them to dial into your modem pool and 
enter their user name when launching VNC.

Of course all of this applies no mater which screen takeover product you 
end up using.

If you even suspect that you might eventually want to go down the remote 
access route, I would suggest looking into TridiaVNC or TightVNC as these 
include optimization for slow connections.

 Hope some of this helps...

 Michael

-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of erikcw
>Sent: den 21 november 2001 23:51
>To: [EMAIL PROTECTED]
>Subject: ATT, Tridia, or Tight?
>
>
>I'm preparing to deploy VNC on my company network of approx 350 WinNT/2000
>machines.  Which is the best distribution to use?
>
>Thanks!
>Erik
-
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
-

RE: ATT, Tridia, or Tight?

[Michael Milette]

___
THE OFFICIAL ANSWER

The official answer is that you can not remove the VNC Icon from the system 
tray... and don't bother asking for this feature to be added because the 
author has taken a very strong position on this (and I agree with him) and 
to my knowledge he hasn't even come close to ever being convinced to change 
his mind. It all has to do with privacy, morals and ethics. See 
http://www.uk.research.att.com/vnc/faq.html#q46 for the official details. 
Personally I think we are lucky that it is just a tiny icon. Could have 
been worse... like a bar right across the screen or something like that.
___
THE WARNING

[ Please don't take the following the wrong way. Parts of it may sound 
harsh but is in fact nothing more than a simple friendly warning based on 
the experience of many who have gone though similar experiences and is not 
meant to necessarily be a reflection of your personal situation. ]

PLEASE BE SURE TO GET MANAGEMENTS SUPPORT BEFORE YOU IMPLEMENT ANY REMOTE 
TAKEOVER SOLUTION, be it VNC, PCAnywhere, Remote Desktop Connection, NetOP 
or any of the others out there, especially if you are planning on running 
this in stealth mode. I remember installing a program called LanAssist 
years ago on old DOS machines to help me support users. I almost got fired 
the first time the VP found out that I could take over their screen at any 
time.

Without management supporting and having a good understanding of your 
initiative, your users could have management force you to completely remove 
this valuable tool from your network which would really defeat the what you 
are trying to accomplish. It's not hard to cry foul when dealing with 
privacy issues. It doesn't matter if you are the most ethical person in the 
world. What counts is what users believe and if they even have the 
slightest concern that you might be looking over their virtual shoulder 
when they are not expecting it and without them knowing it, your project 
will die right there and then. It's not all that different than tapping a 
telephone line really when you think about it.
___
THE SOLUTION

Assuming you have full management support, I have included below a few 
suggestions below on how you might overcome the challenge of removing the 
VNC icon from the system tray. Keep in mind that I haven't actually ever 
had the need or even tried any of the following techniques:

1) Download, modify and recompile the source code so that the icon no 
longer appears on the task bar. Not supported.

2) Try using TridiaVNC (supported by Tridia only). I believe a setting to 
remove or hide the icon is (or at least used to be) included. See 
http://www.tridiavnc.com/list-mailist/2001/Feb/0002.html for details.

3) There is a utility called Resource Hacker 
(http://www.rpi.net.au/~ajohnson/resourcehacker/) which will allow you to 
open WinVNC.exe, edit it and then save it. It will allow you to remove the 
icon from WinVNC.exe and may solve your problem. Whether VNC works after 
that is another question. Not supported of course.

4) Take a chance and try applying the TridiaVNC "DisableTrayIcon" registry 
change to TightVNC. TightVNC adds many features to the standard WinVNC and 
might possibly support the ability to disable the TightVNC tray icon.

5) For more details and other alternatives, check out the "WinVNC Tray Icon 
Mini-FAQ", available at http://vnc.ingecom.com/tray.htm.
___
THE SUPPORT

With the exception of the TridiaVNC and possibly the TightVNC solutions, 
any other tweak that gets rid of the icon could result in loss of support 
by the author of VNC as well as fellow VNC users. You have been warned.

 Michael Milette
 TNG Consulting Inc.

At 04:53 PM 2001-11-22, you wrote:
>how do you hide the VNC icon on the task bar?
-
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
-

Re: Be gentle with me!

[Michael Milette]

Hi Lee,

Sorry to disappoint (hope you are not too crushed) you but you won't be 
going into the registry this time unless you need to set this up using an 
unattended batch process of some kind.

SETTING UP VNC

1) Start up the VNC host (or server if you prefer).

If this is the first time you are running the VNC host, skip to step 4 as 
the dialog box usually comes up the first time you run it. Otherwise, 
continue with step 2.

2) Right click on the white VNC taskbar icon
3) Select properties
4) Un-check "Auto" in the "Incoming Connections" section
5) Change the Display Number.

This value is an offset of the 5800 port number. You need to set this value 
to a different number on each of your machines. Note that they need not be 
numbered sequentially. For example, if you want the host to use 5801, you 
would specify a value of 1, 5802 would be 2, etc.

6) Click OK when you are done.

SETTING UP YOUR ROUTER

You will have to add one entry on your router for each of the 6 machines 
that you want to access using VNC. Unfortunately I am not familiar with 
your router so you will have to work this out on your own. Suffice to say 
that the process is pretty much the same as it was for ports 5800 and 5900 
except that you have to repeat it for each of the machines. For example, if 
you have a machine with a display value of 2, you will have to add an entry 
on your router for 5802. I am not sure if you have to add an entry for 5902 
as well. You will have to test this on your own.

CONNECTION THOUGH THE ROUTER

When you connect using the VNC client, you would specify the host followed 
by a colon followed by the same number you set in step 5 above.

For example, if Jack's machine is set to display number 1, you could 
connect to his machine by entering:

 123.123.123.123:1

If you want to access Mary's machine, whose display number was set to 2, 
you would need to connect to her machine by entering:

 123.123.123.123:2

In each cases, 123.123.123.123 was used. This should of course be replaced 
with the IP address of your router. Note that when connecting to the hosts 
THROUGH THE ROUTER, everyone connects to the same IP address, however 
everyone uses a different port number.

DIRECT LAN CONNECTION

When connecting to the host WITHOUT going though the router (for example, 
from one machine on the LAN to another), users must connect use the IP 
address of the individual machine they want to access, however they must 
still specify the correct port number.

For example, if Jack's machine is set to display number 1, you could 
connect to his machine by entering:

 192.168.0.3:1

If you want to access Mary's machine, whose display number was set to 2, 
you would need to connect to her machine by entering:

 192.168.0.12:2

HOPE THIS HELPS

If you have any questions, feel free to ask.

 Michael

At 04:38 PM 2001-10-12, Lee Douglas wrote:
>I've read the faq's and the documentation and I think I see hints of how 
>to do this, but I'm just not sure.
>
>My problem:
>
>I have 6 Win 98 SE machines set up behind a single router (Cayman 3220-H). 
>I've managed to forward ports 5800 and 5900 to one of the machines and can 
>connect very nicely too that one machine.
>
>My question is how (specifically) do I set up the other machines so that 
>they can also be addressed? I can forward additional ports to each machine 
>on the router, I just can't figure out how to make the machines listen and 
>respond on ports other than 5800 and 5900.
>
>It seems to have something to do with registry changes, but I can't quite 
>make them out and I'm reluctant to muck up the registry on one or more of 
>the machines.
>
>So, can some kind soul please point me to _explicit_ directions and/or 
>give me directions through the list?
>
>TIA!
>
>Lee
>-
>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
-

Re: Password question

[Michael Milette]

Hi Jaime,

I believe it is encrypted and stored in hexadecimal the registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default]
Password=...something in hex...

There could possibly be another similar entry at:

[HKEY_CURRENT_USER\SOFTWARE\ORL\WinVNC3\Default]
Password=...something in hex...

This second one would be used if the user is already logged into the machine.

 Michael Milette
 TNG Consulting Inc.

At 06:21 PM 2001-10-12, Salas, Jaime wrote:
>When you set a password for the WINVNC where does that file sit at. Is it an
>INI File or does VNC have it hard coded into the software. Could you please
>let me know.
>
>
>Thanks !
>
>Jaime C. Salas
>
>Volt Services Group
>Corporate I.T. Management
>Ph#714-921-7554
>mailto: [EMAIL PROTECTED]
-
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
-

Re: How to list VNC server displays

[Michael Milette]

Hi Fred,

On Windows, "netstat -a" at the command prompt will list all of the ports 
in use. Then look for port numbers that are an offset of 5800 and 5900. I 
don't know what operating system you are using but if it has a similar 
command, you might want to give it a try.

         Michael Milette
 TNG Consulting Inc.

At 11:39 PM 2001-10-16, you wrote:
>Hello,
>
>Is there a way to check what vncserver displays I've started using 
>"vncserver :N"?
>Can't seem to find any in the documentation.  A search of the archive turns up
>unrelated issues for the first few pates.
>
>Thanks,
>
>Fred
>
>--
>Fred Ma
>Department of Electronics
>Carleton University, Mackenzie Building
>1125 Colonel By Drive
>Ottawa, Ontario
>Canada K1S 5B6
>[EMAIL PROTECTED]
>==
-
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
-

RE: TVNC Pro Observations

[Michael Milette]

The free server that authenticates with NT can be found at 
http://www.smtechnologies.com/downloads.htm. Just scroll down to the bottom 
of the page.

 Michael

At 11:20 AM 2001-10-17, Steve Bostedor wrote:
>That is pretty steep.  Someone else on here made a way to authenticate with
>NT in a free version if that is a feature that you are looking for, and you
>can have a nice front end GUI/scanner for $30/unlimited workstations at
>http://tgcs.web-it.com.  I'll attempt to hunt down the URL for the free
>server that authenticates with NT.
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of
>[EMAIL PROTECTED]
>Sent: Wednesday, October 17, 2001 11:07 AM
>To: [EMAIL PROTECTED]
>Subject: TVNC Pro Observations
>
>
>Tried the Beta/Demo.. just seems like htey tacked
>on a pretty front end to locate and connect.. ( oh
>and 'file transfer coming soon'. )
>
>Makes things a bit eaiser, with a gui/click and view
>interface, but what sysadmin doesnt know what his
>machines are called and if they have vnc installed,
>( 'auto detect' )  and cant type a simple name in pretty
>darned fast
>
>Using NT Domain authencitation IS cool, if you are
>on an NT domain.. be easy to effectivly change passwords
>in-masse instead of touching each pc..
>
>But it sounds a bit high for a ( windows centeric ) convience,
>@ $50/workstation? True it might save time... donno ...
>
>Zig-
>-
>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
>-
-
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
-

Re: AW: Timeout Problem with XP - firewall not the problem

[Michael Milette]

 I still have control of 
when my operating system and applications get upgraded.

 Michael Milette

At 07:14 AM 2001-12-11, you wrote:
>on http://www.symantec.com/pcanywhere/Consumer/
>they write pcanywhere can be used on XP. Is this legal?
>
> >  "Except as otherwise permitted by the NetMeeting, Remote Assistance,
> >   and Remote Desktop features described below, you may not use the
> >   Product to permit any Device to use, access, display or run other
> >   executable software residing on the Workstation Computer, nor may
> >   you permit any Device to use, access, display, or run the Product
> >   or Product's user interface, unless the Device has a separate
> >   license for the Product." (from: Microsoft Windows XP Pro EULA)
>-
>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
-

RE: AW: Timeout Problem with XP - firewall not the problem

[Michael Milette]

S! I don't think they need any more help in coming up with new ideas on 
how to increase profits...

 Michael

At 05:00 PM 2001-12-12, you wrote:
>Subject: RE: AW: Timeout Problem with XP - firewall not the problem
>To: [EMAIL PROTECTED]
>
>If (hypothetically) the number of non-Micro$oft hosts on the Internet
>dropped below, say, 20% or so, they would probably make it illegal to
>connect to a non-Windoze box at all. They might even make it illegal to
>spread rumors that non Micro$oft OS's even exist...
-
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
-

Re: Hide the VNC on workstations

[Michael Milette]

Hi Scott,

I'm afraid you won't get any support here to hide the VNC icon. Check the 
vnc-list archives at http://www.uk.research.att.com/search.html and the FAQ 
at http://www.uk.research.att.com/vnc/faq.html to learn why. However at the 
very least you should read the excellent recent reply on the same subject 
(written by yours truly) at 
http://www.uk.research.att.com/vnc/archives/2001-11/0461.html.

As for ensuring that students can not change the password, simply lock down 
the registry using the security settings if you are using Windows NT, 2000 
or XP.

If you are using something in the Windows 9x family including ME, you will 
have a tougher job locking down the system. That being said, you could do 
something like resetting the registry key where the password is stored each 
time the machine boots up or possibly do it several times a day using the 
scheduler.

If you are not too worried about your students hacking the registry to 
reset the password, you can prevent them from accessing the configuration 
options in VNC by running it in restricted mode. See WinVNC Documentation - 
Advanced Settings on the http://www.uk.research.att.com/vnc/winvnc.html 
page for the details. Look specifically for the AllowProperties setting.

By the way, if you budget is tight and you want to lock down Win9x 
machines, check out the following:

Lock Down Your PC - Keep unauthorized eyes and fingers away from your 
precious files, folders, and settings. Article by PC World.com available at:
 http://www.pcworld.com/hereshow/article/0,aid,10907,00.asp

Lock Your Desktop - Another article on locking down your Windows 9x 
desktop. This one is from PC Magazine and available at:
 http://www.zdnet.com/pcmag/pctech/content/18/14/ut1814.001.html

IconLock - A free PC Magazine utility. IconLock was designed to provide a 
layer of protection without sacrificing performance or system usability. 
The download link in the above article doesn't work but you can download 
the latest version from the following page:
 http://www.zdnet.com/downloads/stories/info/0,,77408,.html

Before you consider TridiaVNC (commercial product) or TightVNC, both which 
support the hiding of the icon though a change in the registry, you might 
consider the fact that if you leave the icon there, the kids may be a 
little more careful about what they are doing if they know that somebody 
could be watching them. I have even heard about people who like the icon so 
much, they are looking for a program to have it turn black randomly so that 
they think they are being monitored.

If you are using an operating system other than Windows, please disregard 
this message altogether.

 Hope some of this helps...

         Michael Milette


At 01:13 PM 2001-12-13, you wrote:
>Hello,
>  I would like to deploy VNC on the computers in the school district. I
>need to hide the application and make it so students can not change the
>password.
>Does anyone know how to do this.
>Plus, what is the best method to deploy this to many computers at once
>or rapidly.
>
>Thanks
>
>Scott Van Singel
>IT Director
>Sturgis Public Schools
>Phone: 616-659-1512
>Email: [EMAIL PROTECTED]
>-
>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
-

Re: Make an VNC-Connection visible

[Michael Milette]

Assuming you are using Windows, the white VNC icon that appears on the task 
bar will change from white to black while someone is connected. 
Unfortunately I don't know of any way, without modifying the source code to 
show that someone connected and then disconnected from your screen while 
you were away from your PC.

The only work around might be to enable the option which pops-up a dialog 
box asking the user on the host machine for permission to allow a guest to 
connect to their screen. This feature is not included in the standard 
WinVNC but is available if you are using TightVNC and possibly TridiaVNC.

 Michael

At 03:58 AM 2001-12-14, you wrote:
>Hi,
>
>is there possible to make a connection visible so that a user can see if an
>Admin already connected to him?
>
>Thanks to all
>
>Paykan
-
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
-

Re: Screen Resolution ???

[Michael Milette]

An alternative to the experimental scaling solution provided by other might 
be to simply use the VNC in full screen mode. You won't see the hosts full 
screen if your clients resolution is lower than the host but the scroll 
bars will be gone. Then simply move the mouse past the edge of the screen 
to move around the desktop. Moving around the desktop is very quick and a 
lot easier to than using the scroll bars.

Just don't forget to press CTRL-ESC-ESC to get the task bar back at the 
bottom of the screen.

 Michael

At 12:47 PM 2002-01-02, Keith wrote:
> I have a question not sure if this software package allows you to do
>this but I currently
> connect to a VNCserver (1280x764) with a laptop and I have to move
>the column bars
> around with the mouse to be able to see the whole screen.
>
> Is there anyway of changing the settings either on the laptop and or
>the PC running as the
> server to allow the client to to see the whole screen without using
>the mouse and the column
> bars 
-
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
-

Re: vnc w/ 4port Linksys DSL router

[Michael Milette]

At 05:18 PM 2002-01-05, you wrote:
>Question 1:   I understand that I have to set port forwarding on the dsl
>router setup to port 5900 (or 59xx), but what address do I plug in to be
>forwarded?  I presume I use one of the addresses supplied by my ISP, but
>do I use the IP address, the Primary DNS, the Gateway, or the Subnet
>Mask, or do I use the Destination LAN (DCHP) IP address?  I'm new at
>networking, and a bit confused as to which address to use.

1) The "Service Port Range" needs to be set to 5900~5900.
2) The protocol must be set to TCP.
3) The IP address is the address of the host machine you want to take over.

If this doesn't work, please note that you may have to open port 5800 as 
well if you are using the Java viewer in a web browser. Try looking though 
the FAQ's for more information. The FAQ can be found at 
http://www.uk.research.att.com/vnc/faq.html.

>Question 2:   The Linksys dsl router requires me to turn off DCHP to use
>Port Forwarding.  Am I loosing something important by doing this?

Check again. Unless you are using one of the BETA revisions of the 
firmware, you should not have to disable DHCP in order to enable port 
forwarding.

DHCP is used to assign each of the computers on your network a unique IP 
address. If all of the companies IP addresses are hard coded, you do not 
require DHCP.

Note that in some cases, DHCP will assign a different address to a machine 
when that machine requests or tries to renew its address. If this happen, 
you will not be able to VNC though the router as the address set under 
forwarding will no longer correspond to the right machine, if any at all. 
In this case, hard coded IP addresses will be the only way to ensure a 
consistent IP address. Note that only the machines running a VNC host you 
will be connecting to will require a hard coded address.

Finally, if you plan on connecting to more than one machine on your network 
though the Linksys, you will need to have them each setup on a different 
port. For example, Jack's machine will be listening for a VNC connection on 
port 5900. Larry's might be on 5901, Mary's on 5902, etc. In that case, you 
will have to add a port forwarding entry on the Linksys for each machine, 
also specifying the appropriate IP address for each machine.

>Question 3:   By opening up port 5900 on the dsl router, am I also
>opening up a hole in my firewall that a hacker (or whatever we're calling
>them) can detect and walk through?

Yes. Anytime you poke a hole in your firewall, you decreasing the level of 
security of your network. As port 5900 is a well known port for VNC, one 
thing you might consider is to change it to a non-standard port. This 
proposal is not foolproof but it will reduce the chances of being detected 
by someone specifically scanning for machines running VNC on port 5900.

>Thanks for your help.

You are welcome. Hope you find some of this helpful. Feel free to let The 
List know if you run into any problems.

 Michael
-
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
-

Re: Netgear Router, Port 5900, Not Working

[Michael Milette]

At 06:07 PM 2002-01-05, you wrote:
>I have a Netgear Router on my DSL connection, I have routed port 5900
>to the machine where VNC Server is running ( Win98) with the latest
>download of VNC and I get no connection.
>
>If I connect across the local LAN using the 192. address, it works
>just fine so I know VNC is working.

Here are some suggestions:

1) When attempting to connect to your machine over the Internet, you must 
specify the IP address of your router, not the IP address of the host machine.

2) Make sure your VNC host server is not being assigned a dynamic IP 
address. Otherwise, the IP address of your machine at work may change by 
the time you get home in which case the configuration on the firewall would 
become invalid.

3) Telnet to your routers Internet IP address from home. Specify the IP 
address on the Internet as the host name, and 5900 for the port number. You 
should see "RFB 003.003" appear on the screen. If you do, VNC is responding 
correctly and the problem may be at the client end. If you don't, the 
problem could be either on the router or the host machine.

4) I know this is probably blatantly obvious but make sure your host 
computer is powered on when you try to connect. It is conceivable that 
someone is going around powering off the computers before leaving at night 
after you leave and turning them back on in the morning before you arrive.

5) If you are using the Java VNC Client from within a web browser, you will 
need to forward port 5800 as well as 5900.

6) Make sure VNC is waiting for a connection on port 5900 (display value 
should be "0").

7) Make sure nobody else is also connected to your host machine at the same 
time.

8) Find the following registry key exists. This registry key basically 
restricts which IP address can connect to your machine. If it does exist, 
export the branch (just in case) and then delete the AuthHosts key:

 HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\AuthHosts

9) Make sure your router is forwarding incoming (sometimes also called 
inbound) port 5900 to port 5900 at the LAN IP address (192.x.x.x) of your 
machine.

10) Come back after you have checked the above and ask again. If and when 
you do, please also include answers to the following questions:

 a) What exactly is the error message you are getting? Even when 
there is no connection, you still get an error message though it may take a 
few minutes.

 b) What is the speed of your clients connection? If it is too 
slow, VNC can actually crash your host computer if it takes too long to 
download the initial screen to the client. TightVNC has recently fixed this 
bug and may be a better alternative for slow modem connections.

 Hope you find some of this useful. Have a great day!

 Michael
-
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
-

Re: TightVNC

[Michael Milette]

If you want to use it with Win9x/ME over a slow modem connection, I highly 
recommend TightVNC. Besides the compression, the latest release of TightVNC 
includes a bug fix which eliminates the drain and potential crashing of the 
VNC server during the initial transfer of the desktop image. After all, 
there is little point in crashing the machine you are trying to help.

Other than that, there are a few other enhancements included in TightVNC 
which are not part of the basic WinVNC.

Development and maintenance of TightVNC also appears to more active these 
days so bug fixes are more likely to be included in it although this could 
change at any time (who knows what those guys are up to).

So why use AT&T's VNC? The only reason that I can think of only affects you 
if you want to use it on a platform that is not supported. VNC is available 
for more platforms than any of its offsprings.

Don't forget to also consider TridiaVNC (http://www.tridiavnc.com/) if you 
are looking for something with official support. It has a similar set of 
features (if not more) to those included in TightVNC. If you run into any 
problems, you have the comfort of knowing you have someplace to call to get 
immediate help  in addition to discussion forums like this one.

         Michael Milette

At 09:50 AM 2002-01-10, you wrote:
>Just curious if anyone has use this version of VNC?  I am thinking about
>using it but how does it compare in the realworld to regular VNC?
>http://www.tightvnc.com/
>
>Andrew Krug, MCP
>IT Manager
>Academy of Managed Care Pharmacy
>100 North Pitt Street
>Suite 400
>Alexandria, VA 22314
>P:703.683.8416
>F:703.683.8417
>E:[EMAIL PROTECTED]
-
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
-

Re: Offspring of VNC?

[Michael Milette]

Over the last few months, I have seen several variations mentioned here on 
the list. Unfortunately I have not been compiling a list for such an 
occasion. Though I am sure there are many more out there, here are some 
just off the top of my head:

At http://www.rabidpenguin.org/diversions.html you will find two versions 
of VNC: One that allows you to use IP authentication and another that uses 
NT authentication.

There is also another version that from 
http://www.smtechnologies.com/downloads.htm that authenticates against an 
NT domain.

I am not sure if it is actually a different version of VNC or not but 
http://fredrik.hubbe.net/win2vnc.html has something called Win2VNC that is 
basically a dual-screen VNC hack for Windows.

Of course we should not forget ZVNC, the ZeBeDee enabled version of VNC 
available from http://people.we.mediaone.net/ddyer/znc/zvnc.html

You can find these and others at 
http://www.uk.research.att.com/vnc/extras.html or on the "other platforms & 
environments" page at http://www.uk.research.att.com/vnc/platforms.html.

         Michael Milette

At 05:31 PM 2002-01-10, you wrote:
>Other offspring? What are the other spin offs of VNC? We have TightVNC, and
>TridiaVNC. Anything else?
>
>Andrew Krug, MCP
>IT Manager
>Academy of Managed Care Pharmacy
>100 North Pitt Street
>Suite 400
>Alexandria, VA 22314
>P:703.683.8416
>F:703.683.8417
>E:[EMAIL PROTECTED]
-
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
-

Re: WinVNC 3.3.3r9 Memory Leak

[Michael Milette]

I am not sure if you are referring to the resource memory leak but if so, 
it was fixed in the latest version of TightVNC.

 Michael

At 07:57 AM 2002-01-15, you wrote:
>IMO also it is a classic (and well-known) WIn95 bug; on the other hand, 
>the "fix" from VNC is what I perceive as a classic Unixish
>apporach where a component takes on more thanit's share of the burden in 
>resolving a problem.
-
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
-

Re: DOS VNC

[Michael Milette]

Hi there,

Check out PCREMOTE by PC Magazine. It was first published (as far as I 
know) on January 16th, 1990 and can be found on the web by searching for 
V9N01.ZIP.

The only drawback is that it only works over a COM port. If you can work 
this into your system, this might just be what you have been looking for.

On the plus side, it is free. Hope this helps...

 Michael

At 08:54 PM 2002-01-23, you wrote:
>Hi all,
> is there any programs available for DOS? just curious, if have,
>think it will help in my job to control and troubleshoot POS machines
>currently still using DOS 6.22
>
>Thanks
>
>Daniel
-
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
-

Re: Connecting to multiple servers on one network

[Michael Milette]

Hi Nate,

Though I don't personally own one, every article I have read about Netgear 
routers indicate that port forwarding is included as a feature. I don't 
know if this helps but follow the link below to see what the web page for 
the user interface might look like:

http://www.pcmech.com/pics/routershoot/netgear/web/sua-nat.jpg

You might recognize it or something similar in your routers configuration 
screens. Keep looking and good luck...

         Michael Milette
 TNG Consulting Inc.

At 02:24 PM 2002-01-25, you wrote:
>Hi,
>
>I have a small network with several machines running Win2000. I am using a 
>Netgear router as the front end firewall and I route the ports 5800 and 
>5900 to a specific machine running VNC server.
>
>However, I have several machines running the VNC server and when I am 
>travelling I want to be able to connect to these  machines in my network. 
>Not just one of them.
>
>I had done this once by forwarding ports 5800/5900 to machine A, 5801/5901 
>to machine B, etc.  This was on a different router. When I changed to the 
>Netgear router, I can't seem to do this any longer. The only one that 
>responds is the machine on 5800/5900. No others respond.
>
>Any ideas/suggestions?
-
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
-

Re: VNC with another port than 5900

[Michael Milette]

To calculate the port number Casper, simply use the appropriate formula below:

To select a port number higher than 5900:

 Display Number = [desired port number] - 5900

To select a port number lower than 5900:

 Display Number = [desired port number] - 5900 + 65536

So in the case where you want to use port number 3030, you will want to use 
"Display number" 62666 on both the server and the client as calculated 
using the second formula above:

 62666 = 3030 - 5900 + 65536.

 Michael

At 05:26 PM 2002-01-28, you wrote:
>I want to use port 3030. How do I do that ?
>
>I've tried, but it always add 5900 to the number!
>
>-Casper-
>-
>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
-

Re: VNC with another port than 5900

[Michael Milette]

You know Mike, I was under that impression too. I was sure I had seen 
others recommend taking that path in the past. I was so sure that I had 
even written up a response to that effect.

However just before hitting the "Send" button, I decided to try to enter a 
negative number. At least on the server side, it just beeped at me when I 
tried to enter the minus sign in the Display Number field. I tried it both 
with the most recent versions of WinVNC and TightVNC.

Maybe it works on other platforms but from what I can tell, negative 
numbers using a minus sign isn't a feasible solution on Windows.

         Michael Milette
 TNG Consulting Inc.

At 06:41 PM 2002-01-28, you wrote:
>Casper,
>
>   If I remember right you can use negative numbers so just subtract 5900
>from the port you want to use.
>
>Mike
>
> > I want to use port 3030. How do I do that ?
> >
> > I've tried, but it always add 5900 to the number!
> >
> > -Casper-
> > -
> > 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
>-
-
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
-

Re: vnc-list-digest V1 #1427

[Michael Milette]

Assuming you have a serial mouse Christ, give 
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q131976 a try 
(Microsoft KB Article Q131976).

Alternatively, try 
http://www.esrf.fr/computing/cs/sysadmin/rtk/pc104project/howto/winnt.htm. 
See the section on "Booting without a keyboard and without a mouse, screen 
detached".

Finally, and I have no idea if this works, I read somewhere that you can 
open the Control Panel. Go to Devices and set the Mouse Class Driver to 
"Manual." If you decide to once again connect a mouse, then you will need 
to reset this option to "System".

Though I doubt any of these are the ideal (Windows 9x type) solution, I 
hope at least one of these helps...

             Michael Milette
 TNG Consulting Inc.

At 07:47 PM 2002-01-28, you wrote:
>Greetings,
>
>I know this is a little "off the topic", but does any one know how to get 
>an NT server to boot without a mouse without reporting an error event? I'd 
>like to be able to boot either with or without the mouse.
>
>Thanks
>
>Chris Jaecker
-
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
-

Re: Windows Logging

[Michael Milette]

Though I have never used it myself, there is something about logging in 
TightVNC in the advanced settings dialogue box (which is not part of the 
basic WinVNC server by the way).  It might be what you are looking for. The 
only thing is that it logs to a file instead of the NT Application log.

 Michael Milette

At 03:02 PM 2002-02-07, you wrote:
>Subject: Re: Windows Logging
>To: [EMAIL PROTECTED]
>
>On Thu, Feb 07, 2002 at 11:20:05AM -0800, Patrick Calvert wrote:
> > I am researching the use of VNC to replace another product.  The only thing
> > the other product does that VNC doesn't is when someone connects to a 
> system
> > the hosting systems logs the computer name of who connected into the
> > application log.  Has anyone come up with an add-on that performs this
> > function?
-
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
-

Re: TightVNC 1.2.2, is it beneficial?

[Michael Milette]

At 10:06 AM 2002-02-08, you wrote:
>>From: "Moreland, Julius" <[EMAIL PROTECTED]>
>>Date: Fri Feb 8 2002 10:06am
>>To:   "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>>Subj: TightVNC 1.2.2, is it beneficial?
>>
>>I am considering deploying this to our clients in place of VNCr9.
>>
>>Does anyone have an opinion on this version of Tight VNC?
>>
>>Any raves or rants?

The greatest advantage of TightVNC over WinVNC I have found is that the bug 
which eats up all your system resources on a Win9x machine and potentially 
crashing the machine is fixed as of TightVNC 1.2.2. I use VNC to provide 
remote support and it just wasn't accomplishing the desired effect when the 
initial connection over a modem would crash the computer of the person I 
was supposed to be helping.

An important fact for me is that unlike WinVNC, I see TightVNC actively 
being developed which means that there is a better chance of a bug getting 
fixed sooner with TightVNC than with WinVNC.

At least one of the WinVNC developers used to lurk and occasionally comment 
in the vnc-list but I haven't seen any messages from him in quite a while 
(are you still around James?). On the other hand, maybe he is hard at work 
on the next release. Who knows...

There are also many other great TightVNC features not available in WinVNC 
such as logging, user authentication (prompting the user to accept the 
connection), better data compression, local mouse and cursor and more. When 
running the server, just click on the Advanced button to see all of the 
sever enhancements. For the client, just click the "Options" button of the 
Connection Details dialogue.

By the way, there is nothing preventing you from installing WinVNC and 
TightVNC on the same machine. I don't recommend running them both at the 
same time although you can run the server from one and the client of the 
other. However to get the full benefit of TightVNC you should of course be 
running TightVNC on both the server and the client.

It would be nice if the author of TightVNC would add data encryption to the 
package. I suspect that this might (hopefully) be added in a future release.

Now for the downside of TightVNC. I have occasionally found that screen 
refreshes take a longer to happen with TightVNC than WinVNC. When it 
happens, it almost seems like the TightVNC client gets very busy doing 
something because I don't see any data coming across. Finally the screen 
update happens all of a sudden, out of the blue, usually just as I am about 
to close the connection. This happens most often when connecting to a 
WinVNC host. Unfortunately I can not reproduce the problem on demand and 
certainly not when I am trying to demonstrate the problem.

Just about as often, try as I may, I get into a situation where I am unable 
to convince the TightVNC client that the client and host screens are 
different, even if I click the Request Screen Refresh option. Disconnecting 
and reconnecting again seems to fix the problem. I haven't complained about 
it yet because I can't seem to reproduce the problem with any degree of 
reliability whatsoever. Being a programmer myself, I know that it is 
extremely difficult and most of the time impossible to fix a problem if you 
can't reproduce it. I can say that it appears to happen mostly when the 
connection is over a wireless network where the speed of the connection 
fluctuates and may occasionally disconnect briefly (I have no idea though 
if that fact is related). However this is by no means the only situation in 
which it happens.

As far as reliability is concerned, both TightVNC and WinVNC have served me 
well for a long time but these days I tend to rely more on TightVNC for my 
remote screen takeover needs.

About the only tip that I can offer is that you try to avoid a mixed 
WinVNC/TightVNC environment. Most of the reliability issues I have come 
across occurred when connecting to a WinVNC host server. If you have to run 
mixed, I would recommend TightVNC hosts across the board as it appears to 
be more stable, reliable and leaks less system resources on Win9x/ME 
machines regardless of which client, WinVNC or TightVNC, you use. 
Constantin appears to have done a great job ironing out a lot of the server 
bugs since the release R9 of WinVNC.

 Hope this helps.

 Michael Milette
-
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
-

RE: Request Authorization

[Michael Milette]

Liana, give TightVNC a try. You can download it from http://www.tightvnc.com/.

Once you have the host running, right click on the icon in the taskbar tray 
and select "Properties". Click the "Advanced" button of the host server 
options to find all the options that will allow you to accomplish this.

1) Enable the "Query console on incoming connections" option.
2) Disable the "AutoAccept (instead of Refuse) if query times out" option.
3) Enable the "Allow option to Accept without Password" option.
4) Disable the "Disable empty passwords" option.
5) Click OK and delete the Password leaving this field blank.
6) Finally, click OK and you are done!

 From then on, when ever you connect to that host, the client will not be 
prompted for a password and the host user will be given the choice of 
allowing or disallowing the client access to their machine without the need 
for prompting the client for any password.

The dialogue box that appears it's not quite the simple Yes/No box you 
asked for but never the less should do fine for your requirements. I am not 
quite sure what the difference is between accepting with or without 
password. In my testing, after completing the above instructions I was not 
prompted for a password regardless of which button was clicked.

 Hope this helps...

 Michael Milette

At 04:02 PM 2002-02-11, you wrote:
>Hi Steve,
>
> Does adding the client in this manner allow the customer to have the
>option of accepting a remote control session versus providing a password?
>We will only be remoting on this side of the firewall, so is opening a port
>still an issue?
>
>Thank you,
>
>Liana
-
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
-

Re: Scrolly mouse support

[Michael Milette]

Great news Constantin! Looking forward to it.

 Michael Milette

At 12:50 AM 2002-02-12, you wrote:
>Mouse wheel is not supported in current Win32 version of VNC, neither
>in viewer nor in server. However, next TightVNC release will include
>support for mouse wheel under 98/NT4/2000/XP.
>
>--
>With Best Wishes,
>Constantin
-
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
-

ZNC based on TightVNC

[Michael Milette]

Hi Dave,

I don't suppose you might consider using TightVNC instead of WinVNC as your 
base code, would you? TightVNC is actively being developed, has many more 
features, less bugs and is more stable than WinVNC.

Alternatively, you might try offering Constantin the opportunity of 
integrating your changes into TightVNC for you. I know he has been toying 
with the idea of adding encryption to TightVNC and he might be interested 
in implementing your changes. Can't hurt to ask.

 Michael

At 01:52 AM 2002-02-26, you wrote:
>  Since at&t is playing domain name games, ZNC is moving to a new home.
>  Find it at:
>
>  http://home.attbi.com/~davedyer/znc/zvnc.html
>
>The is no change (except from the location) from the version you may already
>be using.
-
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
-

Re: TightVNC

[Michael Milette]

 From the TightVNC web site ( http://www.tightvnc.com/ ):

=

TightVNC Features

Local cursor handling. Cursor movements do not generate screen updates any 
more, remote cursor movements are processed locally by the viewer, so you 
do not see remote cursor pointer moving too slow behind the local cursor.

Efficient compression algorithms. New Tight encoding is optimized for slow 
and medium-speed connections and thus generates much less traffic as 
compared to traditional VNC encodings. At the same time, TightVNC supports 
all the standard VNC encodings, so it can be easily configured to operate 
efficiently in fast network environments too.

Configurable compression levels. You can choose any appropriate level of 
compromise between compression ratios and coding speed, depending on the 
your connection speed and processor power.
Optional JPEG compression. If you don't care too much about perfect image 
quality, you can enable JPEG coder which would compress color-rich screen 
areas much more efficiently (and image quality level is configurable too).

Web browser access. TightVNC includes greatly improved Java viewer with 
full support for Tight encoding, local cursor feature, 24-bit color mode, 
and more. The Java viewer applet can be accessed via built-in HTTP server 
as in the standard VNC.

Operating under Unix and Windows. All new features listed above are 
available in both Unix and Win32 versions of TightVNC.

Advanced Properties dialog in WinVNC. Unlike the standard VNC, TightVNC 
gives you a possibility to set a number of advanced settings directly from 
the WinVNC GUI, and to apply changed settings immediately. There is no need 
to launch regedit to set query options, connection priority, to allow 
loopback connections, disable HTTP server etc.

Automatic SSH tunneling on Unix. Unix version of TightVNC viewer can tunnel 
connections via SSH automatically using local SSH or OpenSSH client 
installation.

And more. A number of other improvements, performance optimizations and 
bugfixes.

=

Personally, I have found it to be much more stable, especially when used on 
Windows 9x/ME systems. The stalk WinVNC has a flaw that causes it to eat up 
system resources during the initial connection over a slow connection such 
as dial-up modem. In this situation, chances are your PC will run out of 
system resources and crash before the initial connection has been 
established. That was enough for me to switch over to TightVNC and I highly 
recommend it to anyone considering VNC. The developer, Constantin 
Kaplinsky, is also actively developping TightVNC which means that if you 
actually uncover a bug in the software, chances are Constantin will try to 
fix it in his next release. WinVNC development appears to be currently on 
hold as there hasn't been a new release in over two years.

Disadvantages of TightVNC vs VNC? Probably the support for operating other 
than Unix, Windows and Java. The documentation is also incomplete though 
you can cetainly use AT&T's VNC docs for most things. I think it's hard to 
find reasons why anyone would consider VNC over TightVNC at this point in 
time. Perhaps one day when VNC development resumes things will change but 
for now, I would suggest you consider TightVNC.

         Michael Milette

At 05:57 PM 2002-04-05, you wrote:
>I keep hering about TightVNC but what are the advantages vs disadvantages to
>the regular VNC found on the AT&T site?
-
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
-

Re: Dropping connections

[Michael Milette]

Sorry, I haven't been following the thread.

If you are Windows 9x/ME, try switching to TightVNC. WinVNC has a problem 
that causes it to deplete system resources if the connection is too slow, 
resulting in a system crash.

If you are using any other OS, please disregard.

 Michael

At 10:07 PM 2002-04-08, you wrote:
>OK, I finally got VNC working, and was able to connect through my network.
>So I was playing around with it, but it then froze. I tried to reconnect,
>but it acted like the server didn't exist (even though it's still running).
>So I reboot the server, and it works for a while, then stops, and I need to
>restart again. Anyone have any ideas how to fix this?
-
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
-

Re: Citrix v. VNC

[Michael Milette]

As soon as the number of users increases though, 
so do your support costs.

Don't get me wrong, I use VNC and firmly believe that VNC does have its 
place. It's just not for remote access by more than a few users a corporate 
environment. On the other hand, software like Terminal Server or MetaFrame 
are not the right kind of tools to use for supporting users or servers.

In the long run, you will find that you can cut your costs and increase 
user satisfaction by using the right technology in the first place. Isn't 
that what IT is all about?

 Michael Milette

At 10:41 AM 2002-04-11, you wrote:
>A major figure in our Medical School (Sr. Vice President for Health
>Sciences) sent the memo below to all of our faculty this morning.  The
>gist of the memo is that Citrix was considered for use by physicians in
>the Med School but it was found to be too expensive.  I'm wondering if VNC
>could do the job.  Does Citrix do the same thing as VNC or is it entirely
>different?
>
>Mike
>
>--
>Michael B. Miller, Ph.D.
>Assistant Professor
>Division of Epidemiology
>University of Minnesota
>http://taxa.epi.umn.edu/~mbmiller/
-
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
-

RE: Citrix v. VNC

[Michael Milette]

WINFRAME
   PC to PC SERVER, UNIX to PC SERVER
   MULTI USER on NT 3.51 based server

The server is a modified version of Windows NT 3.51 Server.

The clients are the same ones used by MetaFrame so any client platforms
supported by MetaFrame are also supported by WinFrame.

METAFRAME
   PC/UNIX/OTHER to PC SERVER or to UNIX
   MULTI USER

The server runs on top of Windows NT4/2000/XP/Unix servers.

The clients run on a multitude of platforms including Windows and WBT
Clients (Win32 for Windows 2000, Windows NT. 4.0, Windows 95, Windows 98,
Win16 for Windows 3.1, Windows 3.11, Windows for Workgroups,
Windows CE), Handheld Devices (WinCE,PocketPC,EPOC), DOS Clients
(DOS32,DOS16), Web Clients (ActiveX. Control, Netscape Plugin, Java), UNIX
Clients, Linux, Solaris SPARC and X86, Compaq Tru64, HP-UX, IBM.
AIX.,SGI, IRIX., SCO., Sun Workstations, Macintosh Client, and OS/2.

Both WinFrame and MetaFrame are licensed on a concurrent user basis. If you
have 1000 users but only 15 at a time, you only need 15 licenses. That's
it. That's all... at least as far as Citrix is concerned. However, in the
case of MetaFrame on Windows NT based technology, Teminal Server licensing
conditions apply on top of the MetaFrame licenses (see below).

WINDOWS TEMINAL SERVER
   PC/MAC/LINUX/DOS to PC SERVER
   SINGLE USER on XP Professional
   MULTI USER on NT4/2000/XP servers

The server is available as a modified version of Windows NT 4.0 Server. As
of Windows 2000 and including Windows XP (server editions of both), this
feature is now included although you need licenses to use them. Licensing
is on a per user AND per machine basis. For example, if one user uses two
machines to access the server, you need two licenses. If the user is not
connecting from a Windows NT family workstation, you will need a Windows NT
workstation license for each user. Then you need the client access license
(CAL) on top of that.

The clients run on a few platforms, but is only supported for Windows
(32-bit) by Microsoft. Support for Macintosh is available from
http://www.hobsoft.com, Linux/Unix from http://www.rdesktop.org/, DOS from
http://www.terminal-services.NET and Linux from
http://www.thincomputinginc.com/winconnect/ (added from Alex and Glen's
posts). There used to be a VNC to RDP proxy called rdp2vnc which would make
VNC clients work with RDP hosts however I can't seem to find it any more.

A good overview comparison between Terminal Server ICA and Teminal Server
RDP is available at
http://www.microsoft.com/windows2000/server/evaluation/features/rdp.asp. Be
sure to read all the footnotes. Keep in mind that this only includes
features up to Windows 2000.  I could not find a similar page on Windows XP
(ok, I only spent about 30 seconds looking).


VNC
   *ALMOST* ANYTHING to ANYTHING
   SINGLE USER on most platforms
   MULTI USER on UNIX.

There are so many platforms supported, officially by AT&T and unofficially
by other, that I would rather send you to the following two pages. Keep in
mind that the server is not necessarily available on all platforms:

VNC download page
http://www.uk.research.att.com/vnc/download.html

VNC on other platforms & environments
http://www.uk.research.att.com/vnc/platforms.html

NOTES:

SERVER, also known as HOST, is the machine you are taking over.
CLIENT, also known as VIEWER, is the machine being used to view the host
screen.

 Hope this helps...

         Michael Milette

At 01:48 PM 2002-04-11, you wrote:
>Michael,
>   Can you clarify the types of connections you are describing below
>when using Citrix?
>
>Are they:
>
>PC to PC
>UNIX to PC
>PC to UNIX
>UNIX to UNIX
>
>Thanks
>tj
-
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
-

Re: print redirection

[Michael Milette]

Upgrade the remote PC to WindowsXP - A single user terminal server is built 
right in and can be accessed from any 32 bit version of Windows including 
your Windows 2000 Pro machine. It's cheaper than going out and buying 
Terminal Server.

Just one note. I recently saw something that said that printing is still 
done though Microsoft Networking and not though the Terminal Services. I am 
not positive on this point as I wasn't really paying attention to that part 
of the article so you might want to look into that before you put out the cash.

        Michael Milette

- Original Message -
 > win2k pro is the platform
-
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
-

RE: print redirection

[Michael Milette]

Whether it is VNC or RDP, assuming you have some kind of firewall, you need 
only configure it to forward the RDP port 3389 to the IP address that you 
want to access. Port 3389 is the only port you need to open. For VNC it 
would be 5900. Sound will attempt to be streamed through User Datagram 
Protocol (UDP) first. If no port is available for UDP, sound will stream 
through a virtual channel in Remote Desktop Protocol, which uses port 3389.

See "Remote Desktop Web Connection" for more information at:
http://www.microsoft.com/windowsxp/expertzone/columns/russel/02January14.asp

Don't forget that XP has its own built in firewall that you will have to 
disable to get the whole thing running. To do this, in the Network 
Connections window, right-click the connection through which you will use 
Remote Desktop, and then click Properties. Click the Advanced tab, and then 
select the checkbox for Protect my computer and network by limiting or 
preventing access to this computer from the Internet. Click the Settings 
button. In the Services list, select the checkbox for Remote Desktop. (I 
think this last part is covered in the above link.)

Regardless of whether you are going with a Remote Desktop Connection or 
VNC, I would recommend that you change the default port.

Have you ever considered simply running your application remotely instead 
of printing over the Internet? I am sure you have. It was just a thought.

You should also consider Julius' suggestion about using Windows 2000's 
Internet Printing Protocol. Of course it requires a Windows 2000 or XP 
server with IIS running which in itself can me a pain to manage not to 
mention the security issues. Additional information is available at 
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q248344.

Again, keep in mind that XP will not support printing over the Internet. 
Alex and other sources have confirmed it.

 Hope this helps,

         Michael Milette

At 07:40 PM 2002-04-14, you wrote:
>thanks for your reply Michael, how would i access the computer behind a lan
>when the computer i want to access is 192.168.0.6 and the only public ip for
>the lan is 203.453.XXX.XXX
>thanks, i hope you can help or point me in the right direction
>
>Jon
-
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
-

RE: print redirection

[Michael Milette]

I would not worry about that for two reasons:

1) Like I said, XP only supports one user, whether it be local or remote at 
any given time. If someone is using the computer locally when a remote user 
tries to connect, they will be asked to relinquish control of the computer. 
I never really tried accessing XP as a second remote user while the first 
was already connected but I would assume that you will either be prompted 
to relinquish control as with the local user or you will be told that you 
can not connect.

2) Unlike VNC which uses port number (5900 + the display number), the port 
allocation for ICA and RDP is dynamic. With most servers, the "well known" 
port number is typically only used for the initial negotiation of an 
alternate dynamic port, much in the same way as http web servers, which 
work on port 80, can accommodate hundreds if not thousands of connections 
at the same time.

These "dynamic" port range is usually between 49152 and 65535 and is not 
blocked by the firewall. This isn't usually a security problem since there 
should not be any services running in that range of ports. The only time 
there is a service showing up in that range is when it has been 
pre-arranged by a server and client. I am sure there must be some kind of 
negotiation that goes on with most protocols to ensure that the connection 
is actually being made by the client who originally requested the 
connection and not someone else who got lucky. DISCLAMER: Note that I 
haven't actually read any RFC's on this. I am just assuming that this is 
the way it works based on my observations and experiences.

As for dns2go, it won't help you here because dns2go won't give your 
network more IP addresses than you have. It's like the address on the front 
of your home. You can get lots of post office box numbers as aliases for 
your home address but you will still only have one number on the front of 
your home.

 Michael Milette

At 02:24 AM 2002-04-15, you wrote:
>thanks michael if i go with the port forwarding using xp what happens if
>there are going to be 2 users trying to access it at the same time, if i
>setup a dns server on 2 computers behind the ics like dns2go would i just be
>able to plug in the address and all should be fine
-
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
-

Re: DOS VNC Server

[Michael Milette]

Keep in mind that there is no standard TCP/IP stack for DOS so you may have 
a bit of a hard time finding remote take over software that will work over 
the Internet.

If you want to dial-up, there is a free solution from PC Magazine (I think 
it was called something like PCREMOTE).

 Michael

At 12:52 AM 2002-04-16, you wrote:
>I saw in the ports area there is a VNC Viewer for DOS... but is there a
>Server for DOS?
>
>I have two machines running MS-DOS 6.2.2 that I would like to have remote
>access to so I can issue commands to the software running from off site.
>
>Is this even possible with DOS? (can VNC run as a TSR and still be able
>to do its thing while other software is running?)
>
>-chris
-
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
-

Re: DOS VNC Server

[Michael Milette]

It would be possible if you connected the two PC's using a null modem 
serial cable. I think PCREMOTE (or REMOTEPC not sure what it was called) 
can work without a modem as long as the cable is made properly.

The client should be able to run in a DOS box on a TCP/IP enabled Windows 
machine.

Of course this is all very theoretical and I haven't tried it myself 
(although I think I used to use it with a null serial cable). Since all the 
software is free, you have only the cost of a null modem cable to loose if 
it doesn't work (assuming you don't have one around).

Just out of curiosity, is there a reason you can't run your DOS application 
in a Windows environment? It is sometimes easier to get your application 
running than to work out some convoluted solution (sorry if this is too 
personal of a question).

         Michael Milette

At 10:18 PM 2002-04-16, you wrote:
>yes, i need to use carbon copy to run on dos in LAN environment...is this 
>possible to view the remote pc that is currently running on other software 
>and i am able to control and use the software remotely?
-
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
-

RE: Exchanging IP addresses (was: Connecting to another computer via dialup)

[Michael Milette]

Actually, if you are talking on the phone to the person with the dial-up 
connection and you have a DSL or Cable connection, just check your IP 
address before hanging up with them. Chances are pretty good that your IP 
address won't change in the next few minutes and they will be able to 
connect right up to your system.

If you are both on dial-up, here are a few alternatives you can use to 
exchange IP addresses:

- Email the IP address. Actually, users don't even need
   to know their IP address. Just have them send you an
   email. You can locate their the IP address in the
   header information. It is typically hidden but usually
   still accessible.

- An IP poster like Post-It Dynamic IP Poster (freeware)
   Note: Requires access to a web site to upload a
   web page containing the IP address (all automated though).
   http://www.knology.net/~cartersoftware/ip.html

- Use ICQ, MSN, or AOL Instant Messenger. You still need to find
   out what your the IP address so as to tell the other person.

- DNS2GO. May not work if you are behind a firewall or router.

NOTE: There are a many ways to find out your current IP address. Here are a 
few:

1) Click Start, Run, and enter WINIPCFG (Win9x/ME only)
2) Run IPCONFIG from a command prompt in Win NT/2K/XP
3) If you are running VNC Server, just place your mouse
over the VNC icon on your task bar (near the clock).

TIP for NT4/2000/XP users: WNTIPCFG, a GUI version of the IPCONFIG command 
is available for free from Microsoft at 
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/wntipcfg-o.asp. 
If you miss the WINIPCFG tool from Windows 9x/ME, you will love having this 
official replacement.

         Michael Milette

At 06:35 AM 2002-04-17, you wrote:
>To: [EMAIL PROTECTED]
>Subject: RE: Connecting to another computer via dialup
>
>Jon,
>
>do YOU have a static IP address or can YOU setup a dns2go for your dynamic
>IP address? If yes, then perhaps the following solution might work:
>- when you need to get to the remote users's Win98, start vncviewer in
>listening mode ("vncviewer.exe /listen")on your computer
>- let the remote user start winvnc on his Win98 and connect it to your
>listening vncviewer. You can prepare an icon on his desktop for this.
>
>This procedure requires YOU to know your IP address and it's probably not a
>problem for you to find it out if it's dynamic or setup dns2go.
>
>Just my $0.02.
>
>Regards,
>
>Miro
-
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
-

RE: how to hide the VNC logo ?

[Michael Milette]

You are right about one thing. People are curious about the icon. So save 
yourselves a lot of trouble and just explain to them what it is. In all of
the different organizations I have worked in, I have yet to meet anyone
who likes to be spied upon. Sure you can take away the icon, but I wouldn't
want to be ya the day that someone discovers you are spying on them.

However, if you explain to people that this is a tool that you use to assist
them and that they will know when someone is peeking at their work, you may
have a chance at acceptance. People I have dealt with in the past have
accepted this situation reluctantly. What they would much rather have is
something that would prompt them, actually getting their permission for
you to look at their screen.

As I see it, you have 3 choices:

1) Explain it to them. (Takes just a minute or two and people will be that
   much more knowledgable)
2) Recompile your own version of the program.
3) Use some other product.

I support the display of the icon as a very minimum standard.

Say, perhaps we could have the FAQ e-mailed to people automatically as soon
as they join the vnc-list? Hmmm. What about including an embeded number in
the FAQ that someone must enter in order to join the list. That way they
would have to read the FAQ to find the hidden number. Argh, I give up...

I appologize for this intrusion but I can't believe how often this subject 
has come up over and over again thought the years.

Michael Milette


>Whilst everyone is getting tied up with pointing people at the FAQ is anyone
>noticing how many people are asking for this facility?? The FAQ says "We
>feel that there would be few legitimate uses of VNC where you would need to
>conceal its operation." - maybe this position is due for a rethink. I
>regularly need to "dip in" to people's desktops in a training environment,
>and the distraction of the icon changing colour is unwelcome. In fact the
>icon is unwelcome as it generates lots of curiosity.
>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Fulbright
>> Sent: Tuesday, December 26, 2000 9:15 PM
>> To: [EMAIL PROTECTED]
>> Subject: Re: how to hide the VNC logo ?
>> 
>> 
>> > How is it possible to hide the VNC logo located on the 
>> taskbar (windows 98),
>> > on the right and down, even of course when VNCSERVER is 
>> enabled on the PC ?
>> > If the logo is hidden, so nobody knows that Vncserver is 
>> working ...!
>> 
>> PLEASE read the FAQ before posting to this list.
>> 
>> Dan Fulbright
>> -
>> To unsubscribe, send a message with the line: unsubscribe vnc-list
>> to [EMAIL PROTECTED]
>> See also: http://www.uk.research.att.com/vnc/intouch.html
>> -
>> 
>
>
>**
>Any views expressed in this message are the sender's own, and do not
>represent the views of Nailsea Family Practice or Woodspring Healthcare
>Limited except where the sender specifically states them to be the
>views of one or both of those organisations. This e-mail should only be
>read by those persons to whom it is addressed. Accordingly, we disclaim
>all responsibility and accept no liability (including in negligence) for
>the consequences of any person other than the intended recipients acting,
>or refraining from acting, on such information. If you have received this
>e-mail in error, please accept our apologies and we simply request that
>you delete this document. Any form of reproduction, dissemination,
>copying, disclosure, modification, distribution and/or publication of
>this e-mail is strictly prohibited.
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: "ethical" to hide the VNC logo ...

[Michael Milette]

I have seen this when running it as a service on NT. Try connecting to that 
machine. The icon should appear.

 Michael Milette

At 03:35 PM 2000-12-29 -0500, you wrote:
>Umm, okay.
>
>I belive you, but it's just not there.
>I recognise everything in the tray, and there
>isn't that much there, and nothing new.
>
>Maybe it will be there when the machine reboots?
>
>I'm running it as a service, not an app.
>
>Steve Bostedor wrote:
> >
> > It's a little white icon that sits on the tray until someone connects, then
> > it turns black.
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: "ethical" to hide the VNC logo ...

[Michael Milette]

I have to wonder why people feel the need to hide in shadows in order to 
catch people in the act when it might actually be easier to eliminate the 
act altogether.

It sounds to me like you are in a tough situation. I want to make it clear 
that this is the only reason I am willing to present some non-VNC related 
alternatives at this time.

The following is a non-technical people-oriented plan that should reduce, 
if not eliminate any related issues you are experiencing within a 
relatively short period of time:

1) Get permission first - Make everyone sign an acceptable use policy. This 
should include their acknowledgement and acceptance of the consequences for 
breaking the rules which should be listed. Make sure they accept the fact 
that they can be monitored anytime. If they don't read what they sign, it's 
their problem. You can justify this new out-of-the-blue requirement by 
stating that you need to deal with problems immediately or else risk 
increasing tuitions and fees for students and decreasing take-home pay for 
employees.

2) Publicize - Make sure everyone knows it when someone gets caught for 
purposefully breaks the agreement. Be *sure* it was done on purpose and not 
just an accident. Failure to follow though with this particular step is the 
main cause for ongoing abuse.

3) Raise awareness - Stop trying to hide your efforts to monitor people. In 
fact, I would suggest that if anything, you try to make it at least appear 
that they are being monitored all the time. If they know they are being 
watched, they will be less likely to do anything wrong. It also means less 
work for you since a) you don't have to deal with them after their caught 
and b) you don't have to repair the damage. If you can't monitor everyone 
at the same time, why not forget VNC all together and just stick little 
fake active VNC icons on all your task bars? Make sure that your 
employees/students know just how much of their potential pay raise or 
tuition is going towards constantly fixing and maintaining the computer 
systems.

4) Enlist Help - Offer incentives and rewards for people blowing the 
whistle on offenders. If there is a reduction in costs after implementing 
this plan, offer some kind of financial bonus for overall system cost 
reduction. After all, if it's not costing you as much to maintain the 
system, you won't loose anything by simply reallocating the money you would 
have spent. On the other hand, if it's not costing you enough to make it 
worthwhile (keep in mind the psychological factor as well), maybe you just 
didn't really need VNC to monitor in the first place. If people are getting 
around your security measures, offer to enlist their help to tighten 
security *BEFORE* they break the rules. Never reward someone for breaking 
the acceptable use policy by offering them a deal.

People love to have responsibilities but hate to be responsible. Not all 
solutions involve technology. In this case, the problem isn't with the 
technology, it's with the people. So try applying people solutions to your 
problem.

 Michael Milette

At 12:45 PM 2000-12-29 +0100, you wrote:
>object : "ethical" for use of VNC
>
>I completely agree with the position of many members of this list about the
>use of VNC that forbidden to "spy" anybody on a network, of course !
>it's a look on private life as read a mail of somebody or have look to his
>neighborhood ...
>But the problem is different and we have to replace it in its own reality :
>As I said clearly, It's a school where there is a network of PC to use
>internet only for the pupils who are not authorized to create mails, or
>write personal documents.
>They are only authorized to visit with their teacher some sites for works
>with their groups that's all ...!
>But some pupils break the system, go to forbidden site (like XXX, or
>dangerous
>political site and many others ..) and of course the school cannot accept
>it.
>So in this particular case it's not "spy" to use VNC to have a look on what
>are doing the pupils.
>Allready, since 2 weeks that the network is installed, we had a lot of
>problems :
>delete of system files, try to know the password, writing of insults on
>teachers,
>It's not the objective of this network ...
>VNC is the only way to stop these desagreements.
>Last remark : in England, we read in the newpapers, that a new law has been
>voted by the British Government, authorizing the companies or administration
>and even on private PC, to have a look on what doing the employees on
>internet !
>... What answer the people in england about this "spy" ?
>I hope now that my position about "to hide vnc logo" will have a better
>comprehension.
>See You !
>Anto

Re: A Simple Problem? (with a simple solution?)

[Michael Milette]

To see exactly why your system is crashing, run the Windows Resource Meter 
on your task bar. You will notice that after you enter your password (as 
the initial screen is loading up), your system resources will drop like a 
rock. If you manage to finish downloading the initial screen before you run 
out of resources, most of your resources will come right back. However if 
the initial screen doesn't finish coming up before you run out of 
resources, the system will crash.

I have found it to be more of a problem over slow connections (like modem) 
however it can be a problem even on a high speed LAN if the machine you are 
trying to take over doesn't respond immediately (for example if the hard 
drive has to spin up).

This isn't a problem when doing the same thing on Windows NT or Windows 
2000 since you don't have the same 128k limit on resources. I have 
mentioned this issue on the list several times in the past but nothing has 
been done about it in any release over the last couple of years.

What can you do about it? Reduce the number of colours and the resolution 
of your hosts screen. It won't make the problem go away, but it will give 
you a better chance of getting that initial screen before the system 
crashes. Alternatively you could simply use one of the commercial programs 
out there like PCAnywhere or Microsoft NetMeeting. I haven't tried a recent 
version of Laplink but the one I have tried, which is a couple of years 
old, had the same problem as VNC over slow connections with Win9x.

             Michael Milette

At 10:05 PM 2001-04-17 +, you wrote:
>There is a message from p.vinten on April 6 (with no reply yet) with the 
>identical symptom with version 3.3.3.R9. I am having the same problem, and 
>details of the crash show the same dll culprit as Mr. Vinten...dibeng.dll.
>
>On that box, I am running Windows 98 SE with two network cards. One is 
>using DHCP (to my DSL modem) and the other uses a 192.168.100.xxx address. 
>Using that computer as a remote, it works great going to my Windows 2000 
>laptop. But when using it as a host, as soon as the password is entered by 
>the remote, the Win 98 system crashes.
>
>The same software version works fine as a host on my Windows 2000 system 
>(single NIC), but not on the Win98SE box.
>
>Any ideas?
>
>Thanks
>>
>>Date: Mon, 16 Apr 2001 01:35:25 -0400
>>From: "Mikhil Bopaiah" <[EMAIL PROTECTED]>
>>Subject: A Simple Problem? (with a simple solution?)
>>
>>Hey, I've searched all the faq's and documentation but I can't figure
>>this one out: I'm trying to run VNC (3.3.3r9) on my old compaq at home
>>(W95).  I installed WinVNC with the default settings and no problems.
>>Running WinVNC in App mode works fine.  When I try to access the server
>>from a web browser (http://my.ip.address:5800) I get the prompt for the
>>password, but as soon as I enter it my server machine displays the
>>message "An error has occured on your computer..." and the server shuts
>>off WinVNC.   I tried accessing from the vncviewer but the same thing
>>happens (as soon as I enter the password in the viewer, the server
>>disconnects and displays error message "An error has occurred on your
>>computer..."). The strange thing is that when I do this, the wallpaper on
>>my server desktop is removed.  I tried removing the wallpaper, and
>>changed the resolutions and color settings so that they matched on my
>>server and client machine.  I also tried accessing from different
>>computers and the same thing happens (it's obviously a problem with my
>>server machine).   If you have any suggestions I'd be much obliged.  I've
>>been tinkering with this for a while and it's driving me crazy...
>
>_
>Get your FREE download of MSN Explorer at http://explorer.msn.com
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

RE: take control without question ?

[Michael Milette]

I think he is referring to asking the host user for permission to take over 
their screen.

 Michael Milette

At 09:42 AM 2001-04-18 +0200, you wrote:
>Ben au LOGIN, on te demande un mot de passe, non?
>
>-Message d'origine-
>De : [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]De la part de Olivier LUTHIER
>Envoyi : 18/04/2001 09:01
>@ : Vnc-List (E-mail)
>Objet : take control without question ?
>
>
>Hy, sorry for my "french-english".
>
>Since several month i use vnc to take control of distant pc. And the control
>is too easy without ask something to the user.
>Is there no possibility to ask a "permission" before taking the control of
>machine ?
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: A Simple Problem? (with a simple solution?)

[Michael Milette]

Sorry about that. I was afraid it might look that way.

Anyway, the resources are being eaten up while the initial screen is 
loading. It is not an instantaneous thing. The longer it takes to get that 
initial screen, the lower the resources go until, well, there are no more 
to be had.

What I was trying to say was that the problem doesn't begin until after you 
enter your password (there is no drain happening while you are being 
prompted for a password).

 Michael Milette

At 12:29 PM 2001-04-18 +0100, you wrote:
> > To see exactly why your system is crashing, run the Windows Resource Meter
> > on your task bar. You will notice that after you enter your password (as
> > the initial screen is loading up), your system resources will drop like a
> > rock. If you manage to finish downloading the initial screen before you
>run
> > out of resources, most of your resources will come right back. However if
> > the initial screen doesn't finish coming up before you run out of
> > resources, the system will crash.
>
> > >On that box, I am running Windows 98 SE with two network cards. One is
> > >using DHCP (to my DSL modem) and the other uses a 192.168.100.xxx
>address.
> > >Using that computer as a remote, it works great going to my Windows 2000
> > >laptop. But when using it as a host, as soon as the password is entered
>by
> > >the remote, the Win 98 system crashes.
>
>The second paragraph suggests the server crashes the instant the password
>has been entered, while the first paragraph indicates there should be a
>delay while the server eats resources trying to transmit the data.
>
>These two symptoms sounds different to me.  Can you clarify whether this is
>the case?
>
>Cheers,
>
>J.N.Weatherall
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: A Simple Problem? (with a simple solution?)

[Michael Milette]

Gee if you could fix that problem, I could finally stop mucking around with 
all the other software solutions out there. Sure, WinVNC is a little slow 
over a modem but as long as it doesn't crash, it would suit my needs just 
fine. Anything you could do would be most appreciated by me as well as many 
other Win9x/ME users.

If anyone can fix it, you can James. Go James Go! Go James Go! :-)

 Michael Milette

At 04:35 PM 2001-04-18 +0100, you wrote:
>Right.  What's happening is that the hooks are continuing to post messages
>to WinVNC, even though it's temporarily gone away to send an update - it
>can't handle the incoming messages while it's transmitting the update.  The
>fix is to separate the update thread from the hook handling thread but
>that's non-trivial.  I'll have a look at it, though.
>
>Cheers,
>
>James "Wez" Weatherall
>--
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: VNC versus Citrix ICA

[Michael Milette]

or all of it's 
users. That's when you start wishing you had implemented that server farms 
(clustering/load balancing). One way to reduce the chances of this 
happening is to limit what users are able to run and not to allow them to 
run anything unauthorized.

As far as I am concerned, VNC and ICA have only one thing in common. They 
are both classified as thin clients. VNC to take over the screen of a 
single machine (or virtual screen in the case of Unix) and ICA to take over 
the screen of a virtual machine.

Sorry for making this such a long message. I guess I had a lot to say.

 Michael Milette

At 11:10 PM 2001-04-20 +0200, you wrote:
>Hello...
>
>VNC is fast but I heart the Citrix ICA protocol is faster!?
>
>Is this true?
>
>--
>Severin Olloz
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: WinVNC Version 3.3.3 R9 causes Windows 98SE server to lock up when access by viewer client

[Michael Milette]

See http://www.uk.research.att.com/vnc/archives/2001-04/0338.html posted 4 
days ago.

 Michael Milette

At 02:24 PM 2001-04-22 -0400, you wrote:
>I loaded the WinVNC Version 3.3.3 R9 on my Windows 98SE pc per all
>directions provided.  While using both the Java viewer and the [.exe]
>viewer, my [server] pc video and cpu functions freeze immediately after
>entering the password.  The client never gets past the grey screen.  The
>server still has cursor movement capabilities, but everything else is
>frozen.  The server cpu has to be physically powered down and restarted to
>restore normal operations.
>
>My server pc is a windows based Pentium III, 800 w/640 meg ram using Windows
>98SE as the operating system.  I use a cablemodem to access the net, and
>ZoneAlarm for a firewall.  The firewall has been configured to allow VNC to
>pass lock.  I ruled out the firewall as a problem by disabling the firewall.
>Same "freeze" results.
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: WinMe

[Michael Milette]

Please see http://www.uk.research.att.com/vnc/archives/2001-04/0338.html.

 Michael Milette

At 02:50 PM 2001-04-25 -0300, you wrote:
>Hello,
>
>I'm in trouble... !
>
>when i try to connect to a winme:
>
>The vnc viewer open a window (black) i can't see anything in the window and
>the winme stops and i need to restart the server.
>
>When i try do the inverse it works well !
>
>Do you know what's happen ?
>
>Thank,
>
>Rodrigo
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: NetWare Server Version

[Michael Milette]

Have you tried RCONSOLE (included with Netware)? If this doesn't meet your 
needs, perhaps taking over a workstation that can run RCONSOLE would.

 Michael Milette

At 01:47 AM 2001-04-26 -0400, you wrote:
>Anybody out there writing (or thinking of) writing a NetWare 
>implementation of VNC?
>
>Cheers!
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: WinMe

[Michael Milette]

Try reducing the number of colours on the server (host) down to 256 colours 
and/or reduce the resolution of your screen. Don't forget to reboot after 
you make the change. Also check with your video card manufacturer to see if 
there are any updated video drivers available.

 Michael Milette

At 01:59 AM 2001-04-26 -0300, you wrote:
>Thank you a lot !
>
>But the problem is that there only 2 pcs in the lan running at 10/100
>connection.
>
>What can i do ?
>
>Reduce or increase the frequency of the display ?
>   - Original Message -
>   From: Michael Milette
>   To: [EMAIL PROTECTED]
>   Sent: Thursday, April 26, 2001 1:06 AM
>   Subject: Re: WinMe
>
>
>   Please see http://www.uk.research.att.com/vnc/archives/2001-04/0338.html.
>
>Michael Milette
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: Null-Modem PPP

[Michael Milette]

Establishing a PPP connection between a Windows 9x machine and NT or 2000

You can find detailed instructions on how to do the Windows 95, 98, and ME 
part of this on the following web page:

http://support.triscend.com/triscendknowbase/root/public/90.htm

Follow the links at the bottom of the page for information on using the driver.

A link to the driver itself can be found on the following page:

http://www.cisco.com/warp/public/471/103.html

You can also try out "The Direct Connection" web site. Many have posted 
positive results in the newsgroups when using their drivers:

http://www.kevin-wells.com/net/

Null modem serial cable information can be found at:

http://support.microsoft.com/support/kb/articles/q108/2/96.asp

As for Windows 2000, I believe there is a null modem type of modem already 
included. My understanding is that you need only install that modem and 
tell RAS to use it.

But then again, this is all very theoretical as I have never personally 
done any of this myself. Try it out and let us all know how it works out. 
Good luck!

         Michael Milette
 TNG Consulting Inc.

At 09:20 PM 2001-05-23 -0500, you wrote:
>Hopefully this isn't too OT and someone can help me,
>I have a windows 2000 pro desktop, and a windows 95 laptop, I also have a
>null modem cable to connect the two.
>What I'd like to do is simply hook up the cable and having them connect via
>PPP at 115k and then go on from there. I have been able to transfer files
>via hyperterm at 115k, and I've been able to get a Direct-cable-connect
>thing going, but it runs at only 19.2k, way to slow for my needs...
>
>Of course, the saving grace that brings this back on topic.. one of my needs
>is that I'd like to connect to the laptop using vnc for remote control.
>This would be easy if I was running Linux, but I am not.
>Eventually I'll buy a secondary ethernet card for my desktop win2k machine
>and run a null ethernet cable between the two, but I'm trying to save my
>money right now :P
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: Null-Modem PPP

[Michael Milette]

Hopefully this information will also apply to Windows 2000:

1) Under Windows NT the serial cable device is installed/configured in the 
Modem utility in Control Panel and is listed under Standard Modem Types as 
"Dial-Up Networking Serial Cable between 2 PCs."

2) Make sure your all serial connection speeds match. Null modem cables 
will not auto-negotiate a connection speed like a modem will. If that 
doesn't work, try slowing down your connection speed to 9,600. Again, it 
must match everywhere

4) Make sure you are using a null modem cable that is properly wired as per 
the linked Microsoft diagram in my previous message.

5) If you don't have a complete proper null cable, try switching to 
software flow control. Either way, make sure this setting matches on both 
machines. Remember, there is no auto-negotiation that is going to happen.

6) Don't forget to start the RAS Server Service on the Windows NT computer 
and make sure the user who is connecting has RAS Dial-in permissions.

If I can think of anything else, I will let you know. Please let us know if 
you get it working and details of the solution.

         Michael Milette
 TNG Consulting Inc.

At 12:04 PM 2001-05-24 -0500, you wrote:
>That helped out some, I'm half way there now.
>I have my windows 95 computer configured, however I'm having problems making
>the actual connection.
>I have a connection setup on my win2k computer to accept incoming
>connections, altho it's limited to 56k for some reason :/ but that's not my
>problem, the computers just refuse to talk to each other now.
>My win95 computer gets to 'verifying username and password' and gives me
>this error message:
>"dial-up networking could not negotiate a compatible set of network
>protocols you specified in the server type settings.
>Check your netowrk configuration in the control panel then try the
>connection again."
>
>However, I have tcp/ip+ppp selected on both sides, as well as dhcp
>configured. Everything /should/ work, but it isn't.
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

RE: VNC DOS server

[Michael Milette]

Sorry, don't know of an implementation of VNC server for DOS.

However, depending on what your requirements are, almost 10 years ago I 
used a utility from PC Magazine called "PCRemote". It worked over a modem 
and I believe that it also worked over a null modem cable. It comes with 
both the host and the client as well as a program called ZCOPY to copy 
files. Best of all, it's free. You can find it as well as additional 
information at 
http://hotfiles.zdnet.com/cgi-bin/texis/swlib/hotfiles_zdnet/info.html?fcode=000OK5&b=pcm

         Michael Milette
 TNG Consulting Inc.


At 02:32 PM 2001-05-24 +0100, you wrote:
>Yeah, this would be extrmely useful in setting up basic OS environments
>remotely...
>
>If anyone knows anything, I'm interested too...
>
>Keith.
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 24, 2001 1:55 PM
> > To: [EMAIL PROTECTED]
> > Subject: VNC DOS server
> >
> >
> > Anyone know if any work has been done on a DOS server?  (I
> > know there is a
> > DOS viewer at: http://pobox.com/~mjy/dosvnc.html).  or any
> > hack \enviroment
> > to get one of the other server platforms to run under DOS?
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: Business use of VNC

[Michael Milette]

Don't charge for the VNC software itself and I believe you should be OK. I 
don't know how the license applies to custom packaging the software though 
(after all, you aren't really changing VNC, just the distribution 
mechanism). Check with James on this.

WARNING: Just keep in mind that there are issues relating to the Windows 9x 
over a slow connection. After all, you wouldn't want to crash the PC of the 
person you are in fact trying to help out. That wouldn't be good for your 
business.

 Michael

At 02:42 PM 2001-06-14 -0400, you wrote:
>I've tried to find a posting of this in the archives and the faq but I 
>can't find any reference to this so I'll go ahead and ask this 
>question.  Also, I am not trying to offend anyone with this posting, but I 
>want to make sure that I will not be breaking any rules or laws.
>
>Say that someone wanted to make a business that used VNC as a tool to help 
>determine what was wrong with a customers PC and fix the problem through 
>VNC.  Say also that they charged a fee for this service.  For every 
>customer that was brought aboard for this service, the customer would be 
>given an executable of VNC and they were also given a link to download the 
>source files of VNC from the businesses servers.  Would this business be 
>violating the GNU license in any way, shape, or form?
>
>Thanks for your time,
>Rick Heckadon
>-
>To unsubscribe, send a message with the line: unsubscribe vnc-list
>to [EMAIL PROTECTED]
>See also: http://www.uk.research.att.com/vnc/intouch.html
>-
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-

Re: Search tool?

[Michael Milette]

Check out the "VNC Extras, Add-ons and modifications" page at 
http://www.uk.research.att.com/vnc/extras.html for solutions, specifically 
VNC Manager, VNCScan and "Fastpush - Batch File Installer for Windows NT".

I haven't used them myself and I am not sure they whether they will tell 
you what version is currently running.

You should be able to roll out and update VNC using what ever system you 
are currently using to update the rest of your network applications. If you 
don't have one, it might be time to consider it.

If your network has grown to the point where it is becoming a major time 
consuming task to roll out applications, you might want to look into 
implementing something like SMS (Microsoft Systems Management Server). Sure 
it might seem expensive initially, but if it allows you to manage your 
network applications in half the time, it won't take long for it to pay for 
itself.

Applications like SMS can do a systems check each time the user logs on to 
make sure that the version of the installed application are the ones expected.

SMS is but one solution out there. Other packages available include (in no 
particular order): Vector LANUtil Elite, IBM Tivoli TME, Computer 
Associates Unicenter TNG, Intel LANDesk, Novell ZENworks, ON Command CCM, 
Novadigm Radia Software Management Suite, Mobile Automation 2000 Enterprise 
Edition, Marimba Castenet and Timbale. I am sure I forgot at least a few. 
But this list will get you started.

Most of these applications are designed to help you handle software 
distribution, asset management, and even remote troubleshooting in some 
cases. Not all packages are suited for every environment so look around for 
one that best satisfies your particular needs.

 Hope this helps...

     Michael Milette
 TNG Consulting Inc.

At 12:33 PM 2002-04-22, you wrote:
>Is there some kind of network search tool or possibly remote install tool for
>VNC?  I have a fairly large network and maintaining all the VNC clients is
>getting to be a chore: tracking who has it, what version, who needs it etc...
>Looking for a tool that will 1) search the network for clients 2) is possible,
>show what version is installed 3) would be very cool, do some kind of remote
>install or upgrade.  Does a such a monster exsist?
>
>-
>Joe O'Bremski, IT Manager
>Carina Corporation
>702-228-6376 x248
>-
>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
-

Re: DOS server

[Michael Milette]

Another alternative...

Say, didn't I read somewhere that someone had developed a DOS emulator for 
Linux?

Check out DOSEMU, (stands for DOS Emulation) which is a Linux application 
that enables the Linux OS to run many DOS programs - including some DPMI 
applications. You can find it at http://www.dosemu.org/. If it works for 
you, it will save you the trouble of donating yet more of your money for 
another copy of Windows or using it illegally without a valid license (of 
course none of us would ever do such a thing).

If your application is happy running in this DOS emulator, you could then 
use VNC to access it.

 Michael

At 12:35 PM 2002-04-23, you wrote:
>2: Run some form of Windows, and then do your DOS stuff in a windows DOS
>session. This will let you use a Win version of VNC Server. (This is the
>route I am looking to go, I am just waiting to upgrade my DOS 486's I
>wanted to control. Once I can move them to Pentium class machines, I will
>install Win NT 4 Workstation, and use VNC with that).
-
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
-

Re: DOS server

[Michael Milette]

I suppose that there isn't any way to kill the time sync and just assume 
that the PC clock is reporting the right time. If you could do that, then 
you could simply run a Windows or Linux app to keep the PC clock in sync.

 Michael

At 10:44 PM 2002-04-24, you wrote:
>Thanks for the info all-
> My application is a remote seismic data acquisition program run under
>DOS. I wish to monitor this remote station from inside my house. The DOS
>acquisition program  uses an interrupt to USGS to keep the time accurate
>therefore the interupt is screwed up if the program is run in a DOS window.
>I am not as yet familiar with Linux but this seems like an option.
>Barry
-
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
-

Re: Can VNC and TightVNC coexist on the same machine?

[Michael Milette]

I have personally had both installed on the same machine and even run both 
clients at the same time.

The only problems you might encounter are:

1) If you try to uninstall one or the other, the common registry entries 
will most likely also be removed.

2) If you try to run both hosts (a.k.a. Server) at the same time, chances 
are one of the two will fail. I haven't done this myself and, unless there 
are DLL conflicts, you might be able to get them to run on different 
display numbers (a.k.a. port offset of 5900).

3) As both share many registry entries, if you change the settings in one, 
these settings will also affect the other (as long as the feature exists). 
Not really a problem, just something to keep in mind.

Worse case scenario is that, in the end, you might have to either 
re-configure or reinstall the one you decide to keep.

Best case scenario is that you will discover additional stability and enjoy 
the enhancements included with TightVNC, regardless of whether you are over 
a slow or fast connection.

But what ever you do, don't install them both in the same directory.

This has been my humble perls of wisdom (a.k.a. opinion). Hope it helps.

 Michael

At 07:34 PM 2002-04-30, you wrote:
>Hi,
>
>I've already installed VNC on  a friend's machine to help me do remote 
>troubleshooting/maintenance for him. We're both on cable modems so the 
>speed is not bad, but I'd like to try TightVNC to see if there's any room 
>for improvement. The problem is he's about an hour away so I can't go back 
>and forth too easily to tweak it,
>
>What I'm thinking of trying is leaving the existing, working VNC install 
>on his machine and installing TightVNC when I'm there this Friday, thus 
>having the option of reverting to the known good ATT VNC if I bugger up 
>the TightVNC install.
>
>However I don't know if this is possible, or if registry entries etc. will 
>be overwritten by the second install.
>
>Anybody done something similar and have any pearls of wisdom to share?
-
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
-

Re: VNC and Opera

[Michael Milette]

Though I haven't seen this with Linux or Opera, I have seen this with 
Netscape on Windows. If you haven't already, try using TightVNC viewer 
instead. I have found the problem harder to reproduce with TightVNC.

 Let us know if it helps...

 Michael

At 06:24 PM 2002-05-15, you wrote:
>I just installed the latest opera web browser on my OpenLinux 3.1.1
>server, but when I run it from a VNC session it kills my VNC session (or
>the window) before the browser pages have even loaded completely.  Has
>anyone experienced anything similar?  I haven't found anything on a list
>search yet.
>
>The VNCViewer is running on Win2K sp2.
-
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
-

Re: Windows 98

[Michael Milette]

Question 1:

Not that I have ever experience.

Question 2:

You could check to see if it does the same thing when you close it from the 
task bar icon. Also try using TightVNC instead. Many bugs have been 
squashed in recent versions.

Also, try uninstalling WinVNC. Then shutdown, reboot and then reinstall WinVNC.

It might just be a matter of the sequence in which it was or you may have a 
conflict with another application. You can test this by running 
MSCONFIG.EXE (included with 98) or Startup Control Panel 
(http://www.mlin.net/StartupCPL.shtml) and disabling all of the startup 
stuff except for VNC. If everything is OK when you shut down, try adding 
them back in one at a time, shutting down and rebooting.

Does it happen all the time or only after having run a certain application? 
Or does it happen only after someone has taken over the screen at least once.

You can also try this: Make sure the WinVNC server (a.k.a. Host) doesn't 
startup automatically either using one of the above steps or what ever 
method works for you. Shutdown and reboot your PC. If everything is still 
working fine, launch WinVNC host manually by clicking on it using your 
startup menu. Once it is running, shutdown your computer. Report your 
findings back here.

Just two more areas that I can think of. These are more last resort in my 
opinion. 1) Update your video drivers to the latest versions available on 
your manufacturers web site. 2) Reinstall TCP/IP.

Of course if you need help doing any of the above, please post another 
message. Either way, let everyone know  how it turns out as the information 
you provide may one day help someone else.

 Michael

PS. To those without any sense of humour, I apologize in advance for the 
following...

***
PLEASE-READ: Legal Disclaimer (FAQ below)
***

Any views or opinions expressed or implied in this email may or may not 
represent those of the author and may or may not necessarily represent 
those of any particular company. Email may be susceptible to data 
corruption, interception, unauthorized amendment, viruses and unforeseen 
delays, and we may not be held liable for any damages directly or 
indirectly related to the use the above information should it or should it 
not be legally proven that such information could be shown to be corrupted, 
intercepted, contain unauthorized amendment, viruses and/or delays or any 
possible, or even remotely possible consequences thereof. Please be aware 
that messages sent over the Internet may not be secure and should never be 
seen as forming a legally binding contract, especially but not limited to 
when otherwise clearly or unclearly stated. Accordingly, this email and all 
attachments are opened at your own risk.

This email and any attachments are private, intended solely for the use of 
the addressee(s). If you are not listed amongst the intended recipient, it 
has been sent to you in error and therefore any use of information herein 
contained is strictly prohibited. If you are not the intended recipient, 
PLEASE DO NOT notify us immediately at the above address unless you believe 
you would like to be amongst the intended recipients in which case you may 
fill out a form in triplicate requesting written permission. However, 
please note that such forms should be written using a pre-treated form made 
from recycled holographic parchment especially designated for such purpose 
and which may be obtained from the author should it one day be made available.

Should any employer be directly or indirectly involved in any such email 
transactions, they may elect at their own discretion, assuming their rights 
are legally binding, to reserves the right to monitor the content of the 
message and any reply received. However they must first disclose to any 
intended recipients the fact that such monitoring is in effect or otherwise 
possibly be liable for personal privacy infringements.

Anyone sniffing the network may not under any condition capture or save 
such said packets of information without prior written concern of all 
parties directly, indirectly or remotely involved.

This legal disclaimer is Copyright 2002. All rights may be reserved by the 
author who may not be reproduced or cloned in any way without prior written 
consent by family, relatives AND friends. Any use in whole or in part of 
this email including but not limited to this legal disclaimer may or may 
not be reproduced with or without prior written authorization unless it is 
strictly for personal or recreational use. Any other use is strictly 
prohibited at the authors sole discretion and may only be sold for profit 
should said profits be immediately and completely forwarded to the author.

You may not read, use, reproduce or manipulate the information contained in 
this email in any way, shape or form if you live in a home, office, 
building, hut, cave, vill

Re: Windows 98

[Michael Milette]

Certainly. See the third issue in the "Legal Disclaimer FAQ".

(Sorry, someday I will number the questions and answers in the next revision).

 Michael

> > Legal Disclaimer FAQ:
: :  : :
> > Q: Can I use it too?
> > A: H... OK. Just don't complain to me when
> > people flame you for the size of your
> > disclaimer... please.

At 05:42 AM 2002-05-18, you wrote:
>Thanks guys for the helpful responses. My initial disclaimer was indeed
>added by our system admin and is not under user control. However, I am now
>at home so this will be almost free of disclaimers! However, I would really
>love to rip off the one below for home use. As it is copyright can I have
>the author's permission please?
>
>John
-
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
-

RE: Off topic, virus activity

[Michael Milette]

All this talk about viruses makes me wonder if listserv type mail lists 
such as this vnc-list contribute to the distribution of viruses. Though I 
personally use Eudora, I understand that Microsoft Outlook automatically 
adds all email addresses included in the headers of incoming email to the 
recipients Outlook/Express address book. Anyone who contributes messages to 
a list such as this would be contributing their email address to the 
address books of most recipients. All it takes is for any recipient on the 
list to get infected by one of these email viruses and all of the 
contributors (people who have posted messages) would receive an infected 
email message.

I would therefore urge anyone who is subscribed to this list to please 
ensure that they are using an up to date AntiVirus program and to regularly 
update their virus signatures. I know of several people who have gotten 
into the habit of immediately downloading any virus signature updates the 
first time they sign onto the Internet each day.

For those of you who are still using that copy of PC-Cillin, Norton 
AntiVirus, McAfee AntiVirus, etc that came bundled with your computer, this 
software is not effectively protecting you, your friends, colleagues, 
associate, or even strangers (anyone in your email address book) unless it 
is regularly updated. Virus signatures need to be downloaded and applied to 
your computer every few days, and certainly no less than once a week. Also 
note that the software itself needs to be replaced once every year or two 
as the viruses become more and more sophisticated. AntiVirus software 
publishers may like to sell you software but they also release new versions 
of their software to keep your computer safe. Notice Microsoft is not a 
publisher of AntiVirus software? 'Nuf said.

Don't kid yourself. An outdated anti virus program is not going to protect 
your computer from anything these days, especially not todays viruses. You 
would probably be better off with no anti virus program running. At least 
that way, beside not protecting your system, it would also avoid any 
performance impact on your computer.

Can't afford to update your anti virus software? At least consider 
replacing it with one of many FREE offerings. For example, Although I have 
not personally tested it, I have read good things about AVG AntiVirus 6.0 
Free Edition for Windows from Grisoft Inc. at http://www.grisoft.com/. It 
seems to installed well, and the company offers free automated updates no 
less than once a week. The catch? You need to give them some registration 
info. To my knowledge I have not heard of anyone who has been added to any 
junk email list as a result of the registration process (read all check 
boxes carefully though). You can also visit 
http://www.hackfix.org/software/antivirus.html and 
http://www.firewallguide.com/anti-virus.htm for more elaborate lists and 
reviews of commercial, shareware and freeware anti virus software for 
Windows and other operating systems. DISC LAMER: I have no affiliations, 
interests or time invested in any of these companies or their product. This 
is simply a public service message.

Please feel free to correct me if I am wrong however make sure your anti 
virus system is up to date before you do. Thanks.

 Michael

> >-Original Message-
> >From: [EMAIL PROTECTED]
> >[mailto:[EMAIL PROTECTED]] On Behalf Of
> >[EMAIL PROTECTED]
> >Sent: Wednesday, May 22, 2002 12:06 PM
> >To: [EMAIL PROTECTED]
> >Subject: Re: Off topic, virus activity
> >
> >
> >As I understand it, the Klez goes into the MS address book in a
> >computer, and sends copies of itself out to every name in the book using
> >it's own built in SMTP engine.  It sure is being a pain in the ass
> >lately!  I am not usually a violent person, but if we ever catch the
> >person/people behind it, we should stone them in the town square!  At
> >least a thief has a real motive.  This is just destructive meanness.
> >
> >
> >Have a Good Day,
> >
> >Michael L.
-
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
-

RE: Off topic, virus activity

[Michael Milette]

I am not saying that the virus would spread via the listserv. I realize 
attachments are removed by the listserv and I am assuming that vbScript and 
most HTML is hopefully stripped out too.

However, I am saying that the email distribution lists in outlook can be 
populated by email messages delivered from a listserv.

Each of us received a countless number of messages each day from this and 
possibly other listservs. If you are using any version of Microsoft Outlook 
or Outlook express, each time you receive an email message, the addresses 
in the "from" field of the email header are automatically added to your 
outlook address book. In the future, should your PC ever become infected 
with one of those email viruses that spread using your outlook address 
book, the virus would then be sent out to anyone from whom you have ever 
received an email message including those who have contributed to vnc-list.

 Michael

At 03:04 PM 2002-05-22, you wrote:
>To: <[EMAIL PROTECTED]>
>Subject: RE: Off topic, virus activity
>
>Virus from the VNC listserv cannot happen because all attachments are
>stripped by "demime".  At most we would see an empty email...
-
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
-

RE: Off topic, virus activity

[Michael Milette]

As I said in my original message, I don't use Outlook myself so I am doing 
this from memory and I am sure my knowledge is much more limited in that 
respect than yours.

About a year or so ago I installed Outlook Express for a user. After a 
couple of weeks, the address auto complete buffer (you know, the thing that 
tries to guess who the recipient might be) had all kinds of addresses in it 
and I seem to recall finding all kinds of email addresses in the address 
book, most of which were unknown to the user of the machine. I seem to also 
remember having found an option or read something to the effect that 
Outlook will search the addresses of all its incoming messages when trying 
to guess the address you are typing. All this is according to my vague 
recollection.

Now for a fact. What I can tell you for sure is that in Outlook Express, 
under Tools, Options, "Send" tab, there is an check box called 
"automatically put people I reply to in my Address Book".

I never really gave it much though after that as I quickly whisked the user 
away from Outlook Express and migrated them to Eudora with the option to 
use Internet Explorer as a viewer disabled.

 Michael

At 04:41 PM 2002-05-22, you wrote:
>Hello Michael. I have (to my knowledge which may be limited) never seen this
>action by Outlook. But then I usually turn off all extraneous options and
>crap! More info please?
-
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
-