It was only an IE issue! I re-installed IE by right clicking ie.inf-->install and after that everything worked fine!
My next mission is to try and use TSweb but re-direct the RDP port so it's not on 3389. I dont like the idea of someone using RDP straight through the firewall. Am i wasting my time?? anyway i will let you know how it goes.
I followed the articles and have run into a proble. I can get to my terminal services logon page at http://ts.pennoni.com/tsweb but once I enter the server name of what I want to connect to I get an error saying the server is not available. The rdp server and and remote desktop web connection is one and the same server.
Any ideas why this would happen?
Just some info...I have my isa 2004 box set up in a pix-isa (one nic going to dmz nic on the pix and the other on internal lan)
It was only an IE issue! I re-installed IE by right clicking ie.inf-->install and after that everything worked fine!
My next mission is to try and use TSweb but re-direct the RDP port so it's not on 3389. I dont like the idea of someone using RDP straight through the firewall. Am i wasting my time?? anyway i will let you know how it goes.
regards
RS
Hi RS,
Great! I figured it had to be something other than an ISA firewall issue.
Thanks so much RS. This is what I see through live logging
Destination ip 192.168.54.x (internal ip of ts box) Protocol 3389 RDP (terminal Services) Action is Denied Rule is Default Rule Source Network is external and Destination is localhost?
Why would it be denying it? I thought my server publishing rule would allow it?
Your also wrote - Make sure you publish RDP server so it listens in on the ip address of ts.pennoni.com. I am not sure I understamd..where and how to do this?
I'm not sure if it has been covered but everytime I have to install OWA after a long period of time I have problems. For me it is an easy fix but remebering what to do is what gets me. Anyway here is my little bit of advice:
If you have IIS installed on the ISA server make sure you do not use the default of Port 80 and Port 443 in IIS. IIS was claiming these ports before ISA so everytime I tried to OWA in it would fail. I noticed here on the board that Tom said look at the Alerts tab in Monitoring on ISA and there I found that the web proxy filter failed to bind to port 443. The error message said that this usually happens when another application uses the port... With this piece of information I stopped and thought about it and whammo it hit me.
If I understand all this correctly...RDP has its own encryption (I read this on Microsoft site) so using the TSAC is no different than using TSWEB because RDP does not tunnel inside of the HTTP/HTTPS. Basically TSWEB initiates the connection but RDP then makes its own independent connection.
The only purpose of the TSWEB is so that you can use the ActiveX client and do not have to use the TSAC.
if anyone can take a look at https://ts.pennoni.com/tsweb you will see the remote desktop web page loads up. If you put in the servername of ts.pennoni.com and click connect it seems to hang for awhile like it is trying to do something but then I get an error saying it could not connect to the rremote computer.
I figure I have the the web publishing rule set up correctly if I can get this far. And I have published the actual terminal server correctly. Any ideas of where I am going wrong?
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [ISA Server 2004 General ] >> Server Publishing >> Discussion about part 3 of article on publishing TSAC sites 
Discussion about part 3 of article on publishing TSAC s... - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread