Hi smerf,
A bit off topic but ....
I find UltraVNC SC (single-click) very useful for the situation described.
The client
makes the connection directly from their desktop to yours via TCP. If they
have
internet access then usually that's enough.
http://sc.uvnc.com/index.php?section=19
Paul
"smerf" <smerf@shroom.comwrote in message
news:UirIg.26674$j8.25189@bignews7.bellsouth.net.. .
Quote:
>I like UltraVNC for helping remote users, and the authors have a server
>called Nat2Nat that you can hook up to to get thru firewalls without having
>to set up ports and such.
>
Problem is that thier Nat2Nat is not exactly reliable and they ignore any
questions about its source code.
>
It looks like they are simply starting a UDP connection from each
client/server VNC combo to the Nat2Nat server and handing off the UDP
connection once established.
>
That would be fine except some office firewalls do not allow UDP
connections.
>
I'd like to build a packet relay server that would work over HTTP or SOCKS
proxies. It should accept incoming connections with a GUID and friendly
name from the "servers" and allow a "client" to connect to a server while
relaying the packets between them.
>
This is relatively easy to do for a normal TCP connection, but what is
involved in getting thru HTTP and SOCKS proxies?
>
I am using VB.Net 2005 so any code examples in .Net 2005 would also be
helpful.
>
Any help you could provide would be greatly appreciated. Thanks!
>