How difficult would this be?

[smerf]

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!

[PGC]

Re: How difficult would this be?

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.c omwrote in message
news:UirIg.2667 4$j8.25189@bign ews7.bellsouth. net...

>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!
>

[Mike Lowery]

Re: How difficult would this be?


"smerf" <smerf@shroom.c omwrote in message
news:UirIg.2667 4$j8.25189@bign ews7.bellsouth. net...

>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!

Many people tunnel VNC connections over SSH since VNC traffic by itself is
unencrypted. I believe you can also specify a proxy server in the SSH client
when you do this.

[smerf]

Re: How difficult would this be?

I also use uvnc SC. It's great for 1st contact.

But, I also need access after hours - when nobody is in the office. I try
and work when they are not there whenever possible to lessen the impact on
thier work days. I guess I could write an app that queries a web service
and connects to me using SC whenever I needed it to......but.... .the project
would be useful for things other than VNC - like a company-specific IM
client or P2P app that keeps files synchronized between PCs.

So, although VNC is a big part of why I need this - it is not the only
reason.

Thanks for your post!

"PGC" <Paul.Remove@Re move.Aten.ie.UC ELesswrote in message
news:OM1atJoyGH A.1304@TK2MSFTN GP05.phx.gbl...

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.c omwrote in message
news:UirIg.2667 4$j8.25189@bign ews7.bellsouth. net...

>>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!
>>

>
>

[smerf]

Re: How difficult would this be?

Ahhhh! A proxy server! That's another thing I'd like to know how to do in
VB.Net or even in old VB6.

I have a cool idea for a business internet filter that could use a proxy
server - but I am lost when it comes to coding one of those too.

Thx for the post!


"Mike Lowery" <selfspam@mou se-potato.comwrote in message
news:Ozd4$csyGH A.1936@TK2MSFTN GP04.phx.gbl...

>
"smerf" <smerf@shroom.c omwrote in message
news:UirIg.2667 4$j8.25189@bign ews7.bellsouth. net...

>>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!

>
Many people tunnel VNC connections over SSH since VNC traffic by itself is
unencrypted. I believe you can also specify a proxy server in the SSH
client when you do this.
>
>
>