http://www.uk.research.att.com/vnc/virus.html
Could this be the problem? Check what version of McAfee you're running,
whether it has been updated (the engine as well as the dat).
-Original Message-
From: Island Snow [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 28, 2002 3:30 PM
To: [E
Why would the machines be there without the users?
For us tech admins to be able to play Quake must faster over the network, of
course. ;)
-Original Message-
From: Scott Yarbrough [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 22, 2002 10:09 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Hi
I think it's better to use the XP's Terminal Services (Micro$oft calls it
"Remote Desktop Control") than VNC if you have multiple logged on computers.
The Terminal service is already started on the XP machine, and when you use
a terminal client to connect to that machine, it locks up the existing
How well I know...yet I'm not sure how to remove the reference to the
VNCServer service in startup. Ya know, when someone logs in, it tries to
start the service, can't find the link.
Know where that would be in the terminal server registry to remove it?
-
J.Dylan McNeill
Technolo
Great points!
Do you find it just a coincidence that the only NAT'ing firewall that can
easily support Netmeeting is (tada!): Micro$oft Internet Security and
Acceleration (ISA) server?
It's an option in the ISA install for H323 support.
It is better than MS' Proxy 2(you shoulda seen the look on my
Folks,
Help me enumerate the ways that VNC (and its various flavors such as
tightvnc, tridiavnc, etc.) is better for remote desktop admin (mostly
troubleshooting, some admin stuff) on a LAN (WindowsNT4 Servers and
Workstations, Win2K) running 100Mb (10 mb in a couple places) than
Microsoft's NetMe
