RE: remote desktop after sp1
- From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Thu, 30 Jun 2005 11:34:59 -0500
Hi Ara,
If that worked, the most likely reason for the problem is that the
Terminal Services listener was bound to the external interface of the
ISA firewall. You can fix that by binding the listener to the internal
interface using Terminal Services Configuration.
HTH,
Tom
www.isaserver.org/shinder
Tom and Deb Shinder's Configuring ISA Server 2004
http://tinyurl.com/3xqb7
MVP -- ISA Firewalls
> -----Original Message-----
> From: Ara [mailto:ara@xxxxxxxxxxxxx]
> Sent: Thursday, June 30, 2005 11:23 AM
> To: [ISAserver.org Discussion List]
> Subject: [isalist] RE: remote desktop after sp1
>
> http://www.ISAserver.org
>
> 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
>
> ------------------------------------------------------
> 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
> ------------------------------------------------------
> Other Internet Software Marketing Sites:
> World of Windows Networking: http://www.windowsnetworking.com
> Leading Network Software Directory: http://www.serverfiles.com
> No.1 Exchange Server Resource Site: http://www.msexchange.org
> Windows Security Resource Site: http://www.windowsecurity.com/
> Network Security Library: http://www.secinf.net/
> Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.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:
