RE: VPN Client cannot RDP to server on LAN
- From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Thu, 5 Jan 2006 13:56:16 -0600
Why the rule that denies the connection doesn't show up the logs is
knowledge so powerful, that the general public is not allowed to know
why.
Your rule sounds correct. If you figure out what the problem is, let me
know. I've heard other people mention that problem, and it never made
sense. I've never encountered by problem myself, so I don't have any
insight into what configuration issue might cause this issue.
Tom
Thomas W Shinder, M.D.
Site: www.isaserver.org
Blog: http://spaces.msn.com/members/drisa/
Book: http://tinyurl.com/3xqb7
MVP -- ISA Firewalls
**Who is John Galt?**
> -----Original Message-----
> From: Danny [mailto:nocmonkey@xxxxxxxxx]
> Sent: Thursday, January 05, 2006 1:52 PM
> To: [ISAserver.org Discussion List]
> Subject: [isalist] RE: VPN Client cannot RDP to server on LAN
>
> http://www.ISAserver.org
>
> On 1/5/06, Thomas W Shinder <tshinder@xxxxxxxxxxx> wrote:
> > Is there a rule that allows VPN clients access to the RDP server?
>
> Allow all outbound protocols, from VPN Clients, to All protected
> networks, all users. I thought that was decent enough to start.
>
> Why would the ISA log not include what Rule has denied access?
>
> Thanks,
>
> ...D
>
> ------------------------------------------------------
> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
> ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
> ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
> ------------------------------------------------------
> Visit TechGenix.com for more information about our other sites:
> http://www.techgenix.com
> ------------------------------------------------------
> You are currently subscribed to this ISAserver.org Discussion
> List as: tshinder@xxxxxxxxxxxxxxxxxx
> To unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=isalist
> Report abuse to listadmin@xxxxxxxxxxxxx
>
>
Other related posts:
