[isapros] Re: RDP Issue
- From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
- To: <isapros@xxxxxxxxxxxxx>
- Date: Fri, 26 Jan 2007 13:27:58 -0600
Except for Web Publishing Rules, where it's Web listener specific.
Thomas W Shinder, M.D.
Site: www.isaserver.org <http://www.isaserver.org/>
Blog: http://blogs.isaserver.org/shinder/
Book: http://tinyurl.com/3xqb7 <http://tinyurl.com/3xqb7>
MVP -- Microsoft Firewalls (ISA)
________________________________
From: isapros-bounce@xxxxxxxxxxxxx
[mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of John T (Lists)
Sent: Friday, January 26, 2007 11:47 AM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: RDP Issue
Changing the listener port is rule specific, not protocol
specific?
John T
eServices For You
"Life is a succession of lessons which must be lived to be
understood."
Ralph Waldo Emerson (1802-1882)
-----Original Message-----
From: isapros-bounce@xxxxxxxxxxxxx
[mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Harrison
Sent: Friday, January 26, 2007 9:17 AM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: RDP Issue
With ISA 2004 / 2006, you don't even need a custom protocol.
You simply change the listener port in the rule itself and use
the standard protocol def.
From: isapros-bounce@xxxxxxxxxxxxx
[mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of John T (Lists)
Sent: Friday, January 26, 2007 9:10 AM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: RDP Issue
You could also change the RDP port for the other server that he
is connecting to and then publish that port by creating a new protocol
in ISA.
John T
eServices For You
"Life is a succession of lessons which must be lived to be
understood."
Ralph Waldo Emerson (1802-1882)
-----Original Message-----
From: isapros-bounce@xxxxxxxxxxxxx
[mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Moffat
Sent: Friday, January 26, 2007 6:25 AM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: RDP Issue
It would also need to be a direct connection to the Internet.
I.E a pair of public addresses, rather than a Linksys as the ports are
the same.
S
From: isapros-bounce@xxxxxxxxxxxxx
[mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Harrison
Sent: Friday, January 26, 2007 10:16 AM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] Re: RDP Issue
Policy details are always useful in cases like this; y'no -
ISAInfo, ISABPAPack, etc?
For instance, "new server publishing rules so that RDP traffic
on IP1 goes to the SBS, and RDP traffic on IP2 goes to the TS" sounds
like two server publishing rules, since access rules aren't
localhost-IP-specific.
Since the default SBS policy uses an access rule for SBS-local
RDP, he could easily create a policy conflict.
From: isapros-bounce@xxxxxxxxxxxxx
[mailto:isapros-bounce@xxxxxxxxxxxxx] On Behalf Of Amy Babinchak
Sent: Friday, January 26, 2007 6:15 AM
To: isapros@xxxxxxxxxxxxx
Subject: [isapros] RDP Issue
Got this question and don't know the answer. I've never used
this configuration. Any suggestions?
Hey Amy -
I've got a quick question for you when you get a moment. I have
a couple sites where I have a terminal server sitting behind SBS Premium
w/ ISA. Ideally what I'd like to do is be able to RDP directly into
both the SBS and the TS. I have tried this at our office - binding a
second IP to the external nic, and setting up new server publishing
rules so that RDP traffic on IP1 goes to the SBS, and RDP traffic on
IP2 goes to the TS. This works initially - but always breaks within a
few days when all RDP traffic in and out of the SBS stops (even from the
LAN). I end up disabling the RDP server publishing rules I created,
restarting ISA services and then RDP is back. At this point, I can
re-enable the server publishing rules and be good to go for a few more
days. I've tried leaving the default RDP access rule enabled (external
to localhost), as well as disabling it, and no change. I'm wondering if
you have seen something like this, or if you have any tips for getting
this to work consistently.
Amy Babinchak
Harbor Computer Services
All mail to and from this domain is GFI-scanned.
All mail to and from this domain is GFI-scanned.
All mail to and from this domain is GFI-scanned.
Other related posts:
