RE: remote desktop after sp1
- From: "Ara" <ara@xxxxxxxxxxxxx>
- To: isalist@xxxxxxxxxxxxx
- Date: Thu, 30 Jun 2005 10:23:21 -0600
Tom,
This trick worked perfectly on my system. Changing the defauly port to
33389 did the job with a new rule. That is strange. Thank you
> Hey guys,
>
> I don't that's it, as I've published dozens of RDP servers behind the
> ISA firewall, all listening on different ports, and there isn't any
> issues that I"ve encountered.
>
> Tom
> www.isaserver.org/shinder
> Tom and Deb Shinder's Configuring ISA Server 2004
> http://tinyurl.com/3xqb7
> MVP -- ISA Firewalls
>
> =20
>
> > -----Original Message-----
> > From: Ara [mailto:ara@xxxxxxxxxxxxx]=20
> > Sent: Wednesday, June 29, 2005 1:09 PM
> > To: [ISAserver.org Discussion List]
> > Subject: [isalist] RE: remote desktop after sp1
> >=20
> > http://www.ISAserver.org
> >=20
> > Thank you very much for your input. Since I believe changing the
> > registry for port settings will require reboot, I have to stay till
> > everyone leaves and try. Will let you know
> >=20
> > -----Original Message-----
> > From: Talley, Scott [mailto:stalley@xxxxxxxxxxxxxxxxx]=20
> > Sent: Wednesday, June 29, 2005 11:00 AM
> > To: [ISAserver.org Discussion List]
> > Subject: [isalist] remote desktop after sp1
> >=20
> > http://www.ISAserver.org
> >=20
> > I hate to jump into the middle of this thread, but I've=20
> > always had this
> > problem.. back to Win2000/ISA2000. If you try to both publish a
> > Terminal Server and use RDP to access the ISA box itself, one or the
> > other will work after a reboot, but not both, and the results are
> > random.
> >=20
> > Simply changing the ISA box to listen for local RDP requests on a port
> > other than 3389 is all you need to do to resolve the "conflict".
> >=20
> > Thank you,
> >=20
> > Scott Talley
> > IT Manager, The Combined Group
> >=20
Other related posts:
