Remote access via VNC

[Julian Brett]

Hi.

I'm trying to obtain remote access to a customer's W2K server which is
running VNC behind a firewall.

I have installed VNC on the machine and configured the firewall to accept
connections on port 5901, and redirect them to port 5900 on the W2K server.

From outside of their lan, I cannot connect to IPADDRESS:1, but can connect
internally to the IP Address or Server Name.

I've tried this on a number of different W2K and WXP boxes at this site, but
cannot connect to any of them from outside of the lan.


They also have a NT 4 server on the lan as well, also configured with VNC.
Configured the same as above, but I've told the firewall to accept
connections on 5902, and forward to 5900 on the NT box. This works OK.

Am I missing something on the W2K boxes?


Thanks,

Julian Brett.

 

[Herb Martin]

I'm trying to obtain remote access to a customer's W2K server which is

running VNC behind a firewall.

I have installed VNC on the machine and configured the firewall to accept
connections on port 5901, and redirect them to port 5900 on the W2K server.

From outside of their lan, I cannot connect to IPADDRESS:1, but can connect
internally to the IP Address or Server Name.

One never expects to connect by name if connecting by address fails.

I've tried this on a number of different W2K and WXP boxes at this site, but
cannot connect to any of them from outside of the lan.

Do you have the XP "local firewall" enabled? Or any similar third party
tools,
especially on the Win2000 boxes which don't have the XP firewall?

They also have a NT 4 server on the lan as well, also configured with VNC.
Configured the same as above, but I've told the firewall to accept
connections on 5902, and forward to 5900 on the NT box. This works OK.

Am I missing something on the W2K boxes?

No (Based on your description.) but obviously something is being missed or
you
wouldn't be posting.

I take it you have configured the remote client to use the proper ports
(5901) for
reaching this Win2K server?

Presumubly you have tried it locally (or had someone try it) to prove that
it is really
a firewall issue?