When you hit the remote desktop page, if you don't type in any ip it will
connect to the machine its running on or any other machine on the internet.
You cannot connect to machine2 in your LAN using the web connector. If you
need to access multiple machines on your LAN, set each machine to listen on
a different port, 3390, 3391, etc, and use the true RDP Client and specify
yourWANip:3391 and it will take you to that machine. Of course you have to
have separate NAT and rules for each machine. The web connector would work
like you want if it were not in your LAN by specifying the port as it's just
a client like the other person said.

Dave

> -----Original Message-----
> From: Chris Buechler [mailto:cbuechler at gmail dot com] 
> Sent: Thursday, April 06, 2006 5:19 PM
> Cc: m0n0wall at lists dot m0n0 dot ch
> Subject: Re: [m0n0wall] m0n0wall and MS Windows Remote 
> Desktop Connection
> 
> >
> > In other words, if the user is on the WAN, then they'll 
> need to type 
> > in a public IP (they won't be able to use 192.168.1.110 
> unless they're 
> > trying to connect to a box on their own LAN), and your 
> firewall rules 
> > (and NAT settings) must allow WAN users to establish TCP-3389 
> > connections to the target box.
> >
> 
> oh, that's a good point.  it's probably trying to connect the 
> users to the private IP.
> 
> not sure how to correct that though.  to check out what it's 
> attempting, run a packet sniffer (like Ethereal) on the 
> client machine attempting connections from the Internet.
> 
> -Chris
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
> 
>