Welcome to ISAserver.org

VNC Connection Not Working

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 General] >> Server Publishing >> VNC Connection Not Working

Page: [1]

Message

<< Older Topic Newer Topic >>

VNC Connection Not Working - 23.Oct.2002 5:38:00 AM

JBraun

Posts: 9
Joined: 23.Oct.2002
Status: offline

Hi All,
I've been experiencing problems making an internal server available to VNC externally.

I have configured a Protocol Definition that allows inbound traffic on 5900. I also have configured an IP Filter for 5900 that allows traffic in both directions on 5900 and will talk to all remote ports.

In addition I have published the server so it should be available.

VNC fails to connect but not all the time. Out of 10 tries, I might be able to connect once or twice. I have tried to review the logs, but I don't know which log I should be reviewing exactly, and I don't quite know how to make sense of all the information.

Any help would be appreciated.

~Justin

Post #: 1

Featured Links*

RE: VNC Connection Not Working - 23.Oct.2002 8:54:00 PM

spouseele

Posts: 12782
Joined: 1.Jun.2001
From: Belgium
Status: offline

Hi Justin,

to get the most information out of the logfiles, I strongly recommend to enable the logging of all fields. In the MMC, go to the node Monitoring Configuration, then select Logs. In the details pane, right-click the applicable service and then click Properties. On the Fields tab, click Select All.

To better understand what is logged, check out the ISA helpfile. There is a section called Firewall and Web Proxy log fields, a must read. Additional information can be found in the knowledge base article Q284818.

You shouldn't have created a packet filter. The server publishing rule will take care of that. So, get rid of it. Also, don't forget that for server publishing to work, the client must be setup as SecureNAT client, not as Firewall client.

HTH,
Stefaan

(in reply to JBraun)

Post #: 2

RE: VNC Connection Not Working - 24.Oct.2002 12:33:00 AM

JBraun

Posts: 9
Joined: 23.Oct.2002
Status: offline

Hi Stefaan,
I have removed the packet filter as you recommeneded below. I think there may be some confusion as to what I am trying to accomplish. I am on a PC outside of my network trying to access a server on the inside of the network using VNC. I'm not sure if that was understood correctly. Does this change anything or what you would recommend?

~Justin

(in reply to JBraun)

Post #: 3

RE: VNC Connection Not Working - 24.Oct.2002 12:48:00 AM

tshinder

Posts: 47663
Joined: 10.Jan.2001
From: Texas
Status: offline

Hi J,

Check this out:

Songpol
Junior Member
Posts: 2
Registered: Jun 2001
posted 27 June 2001 06:20
--------------------------------------------------------------------------------
create protocal definition like this:
TCP
inbound
port: 95xx

xx is your display number
e.g. your display number is 0
must set to 9500

==========================
HTH,
Tom

(in reply to JBraun)

Post #: 4

RE: VNC Connection Not Working - 30.Oct.2002 2:50:00 AM

khobbs_uk

Posts: 13
Joined: 27.Jun.2002
Status: offline

just thought ill pop in on this one as i cant get vnc working externally but can internal, 95xx? i thought vnc is 58xx.
ill shut up if iam wrong

(in reply to JBraun)

Post #: 5

RE: VNC Connection Not Working - 30.Oct.2002 5:17:00 AM

Win2k

Posts: 108
Joined: 2.Feb.2002
From: Atlanta, GA USA
Status: offline

port 5900 for the vnc listener program, and 5800 for the java applet/server (http://machine:5800 on windows machine, Linux Redhat 7.x 8.0 both use 5801 & 5901 for display 1 and so on.

(in reply to JBraun)

Post #: 6