Re: VNC in reverse connection from clients. Canīt put protocol to work
From: Troy (troy_at_engenetec.com)
Date: 10/02/04
- Next message: Troy: "Re: Question about 2 NICs!"
- Previous message: Troy: "Re: Which Anti-virus for ISA 2004 ?"
- In reply to: Edgar Santos: "VNC in reverse connection from clients. Canīt put protocol to work"
- Next in thread: Edgar Santos: "Re: VNC in reverse connection from clients. Canīt put protocol to work"
- Reply: Edgar Santos: "Re: VNC in reverse connection from clients. Canīt put protocol to work"
- Messages sorted by: [ date ] [ thread ]
Date: 1 Oct 2004 22:47:28 -0700
I personally would not use tight VNC for remotely connecting to XP
machines. Itsa great for 9X and 2000 machines but I would use tsweb or
remote desktops for the xontrol of XP machines. Are you familiar with
this?
Troy
MCSA MCP CIW A+ Network+ I-Net+
http://www.engenetec.com
"Edgar Santos" <e.santos@titus.pt> wrote in message news:<#gOt0GwpEHA.1816@TK2MSFTNGP09.phx.gbl>...
> Hi,
>
> we have several customers with SBS 2000 and SBS 2003, wich need support on
> the client machines. For that I've found that VNC is pretty good: easy and
> free.
>
> I installed the VNC (TightVNC) on the clients PC's and created a protocol
> definition:
>
> VNC, TCP Outbound, Port 5500
>
> Created a Protocol Rule:
>
> Name: VNC
> Action: Allow
> Schedule: allways
> Applies to: any request
>
> Why Port 5500, may you ask? Because I installed the VNC server on the client
> PC's and want them to start the connection, called reverse connection.
> (Normal direct connections to VNC would use Port 5800, and HTTP connections
> Port 5900). To do that I go to the proprities of the WinVNC.exe icon and in
> the command line add -connection <my office ip>. Tryed this on remote
> machines connect directly to the Internet, and it works fine.
>
> Behind ISA I'm having problems because I can't make the connection. After
> examined the FW logs I found this:
>
> #Fields: c-ip cs-username c-agent date time s-computername r-host r-ip
> r-port time-taken cs-bytes sc-bytes cs-protocol cs-transport s-operation
> sc-status sessionid connectionid
>
> 192.168.16.10 inacia WinVNC.exe:3:5.1 2004-09-30 11:50:40 SERVIDOR01
> titus.myserver.org 81.193.173.137 - - - - - - GHBN 0 6 0
> 192.168.16.10 inacia WinVNC.exe:3:5.1 2004-09-30 11:50:40 SERVIDOR01 -
> 81.193.173.137 5500 - - - 5500 TCP Connect 13301 4 8
> 192.168.16.10 inacia WinVNC.exe:3:5.1 2004-09-30 11:51:04 SERVIDOR01
> titus.myserver.org 81.193.173.137 - - - - - - GHBN 0 7 0
> 192.168.16.10 inacia WinVNC.exe:3:5.1 2004-09-30 11:51:04 SERVIDOR01 -
> 81.193.173.137 5500 - - - 5500 TCP Connect 13301 4 9
>
> As you can see I have a sc-status of 13301, which I found it means
> connection refused.
>
> One of my customers network, have Win9x and WinXP as clients, all with the
> MSP firewall client installed, but the Win9X machines can connect to me, the
> WinXP don't (!?!?!?)
>
>
> But why? What I have done wrong on the Protocol Definition and Protocol
> Rule? Where can I found more abou this. I don't want to publish the server
> and make connections from my office to the customers. I prefer them calling
> me in reverse connection.
>
>
>
> Thanks in advance,
> Edgar Santos
>
>
> P.S. Sorry my english.
- Next message: Troy: "Re: Question about 2 NICs!"
- Previous message: Troy: "Re: Which Anti-virus for ISA 2004 ?"
- In reply to: Edgar Santos: "VNC in reverse connection from clients. Canīt put protocol to work"
- Next in thread: Edgar Santos: "Re: VNC in reverse connection from clients. Canīt put protocol to work"
- Reply: Edgar Santos: "Re: VNC in reverse connection from clients. Canīt put protocol to work"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
