>"You obviously can't run a VNC server on a port that's already being used
>for other things. "
>This is less than useful on a live webserver!
The fundamental nature of TCP/IP says that you CANNOT have two different
services listening on the same port. Which service would respond to
connection requests?
You'll either have to configure VNC to use port 25 (assuming IIS doesn't
have a Telnet service there) or you'll have to open another port on the
firewall.
If you attempt to put a second server on an existing, in-use port, the
second server will receive an error from the TCP/IP system (WinSock, in the
case of Windows), and will be unable to bind to that port. Even if it did
work, you would get interesting behavior. Some people who tried to web
browse to that machine would receive the VNC protocol welcome ("RFB 3.3", I
think...), and other people who tried to use VNC would get a "Unable to
connect to server" when IIS jumped in and handed out "HTTP 1.0"...
_____________________________ /"\
Mac Reiter \ / ASCII Ribbon Campaign
Nomadics, Inc. X Against HTML 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
---------------------------------------------------------------------
