I can see that, but for the benefit of the OP, we should clarify that. Put that way ("you need one web and server rule per server") it makes it sould like you have to load IIS on each box that he wants people to connect to with RDP. In reality, it is better to use an existing web server and leave IIS off of both of the tservers, particulalrly the one in application mode... t ----- Original Message ----- From: "Jim Harrison" <jim@xxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Tuesday, December 09, 2003 8:22 AM Subject: [isalist] Re: Terminal Services Installation > http://www.ISAserver.org > > I'm just anal (rectal? colonial?) that way. > I prefer to separate all my publishing rules per-server whenever possible. > This way, a change in one is less likely to affect another. > > Jim Harrison > MCP(NT4, W2K), A+, Network+, PCG > http://www.microsoft.com/isaserver > http://isaserver.org/Jim_Harrison > http://isatools.org > > Read the help, books and articles! > ----- Original Message ----- > From: "Thor" <thor@xxxxxxxxxxxxxxx> > To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> > Sent: Tuesday, December 09, 2003 08:14 > Subject: [isalist] Re: Terminal Services Installation > > > http://www.ISAserver.org > > Why the two web publishing rules? He only needs one web rule for the > clients to get to the server hosting the control, and then as you said, a > server rule for each internal server for the actual RDP connection. He > could have 1 web server, and change the connect.asp file to have a thousand > different "connect" buttons for different tservers if he wanted to (or of > course just have multiple different asp files) . Can you elaborate? > > t > > ----- Original Message ----- > From: "Jim Harrison" <jim@xxxxxxxxxxxx> > To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> > Sent: Tuesday, December 09, 2003 6:21 AM > Subject: [isalist] Re: Terminal Services Installation > > > > http://www.ISAserver.org > > > > As I stated before: > > For each TSAC server that is to be externally-accessible, you need two > > rules: one web publishing rule and a server publishing rule. > > You should avoid "grouping" web published servers under a single rule. > > > > Jim Harrison > > MCP(NT4, W2K), A+, Network+, PCG > > http://www.microsoft.com/isaserver > > http://isaserver.org/Jim_Harrison > > http://isatools.org > > > > Read the help, books and articles! > > ----- Original Message ----- > > From: "Raji Arulambalam" <rajia@xxxxxxxxxxxxxx> > > To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> > > Sent: Monday, December 08, 2003 19:45 > > Subject: [isalist] Re: Terminal Services Installation > > > > > > http://www.ISAserver.org > > > > Thanks Jim > > > > I was wondering what to do when you have multiple TS servers. Would one > set > > of rules do or need multiple rules. That's why I asked. > > I've got it working now with one web publishing rule and three server > > publishing rules, as we wanted another TS server. > > Remote users can connect either using a browser or Remote Desktop > > Connection. > > > > Cheers > > > > Raji > > > > -----Original Message----- > > From: Jim Harrison [mailto:jim@xxxxxxxxxxxx] > > Sent: Tuesday, December 09, 2003 3:23 PM > > To: [ISAserver.org Discussion List] > > Subject: [isalist] Re: Terminal Services Installation > > > > > > http://www.ISAserver.org > > > > For each TSAC server that is to be externally-accessible, you need two > > rules: one web publishing rule and a server publishing rule. > > > > All this is discussed in several articles at www.isaserver.org and also in > > the Microsoft Knowledge Base at support.microsoft.com. > > > > I bet you get there a lot faster if you read them... > > ;-) > > > > Jim Harrison > > MCP(NT4, W2K), A+, Network+, PCG > > http://isaserver.org/Jim_Harrison/ > > http://isatools.org > > Read the help / books / articles! > > > > > > On Tue, 9 Dec 2003 14:49:32 +1300 > > Raji Arulambalam <rajia@xxxxxxxxxxxxxx> wrote: > > http://www.ISAserver.org > > > > Sorry Jim, was in a hurry when I replied. > > > > Raji > > > > Hi Tom > > > > Would you need the second Web or Server Publishing rule then?? > > > > Cheers > > > > Raji > > > > > > -----Original Message----- > > From: Jim Harrison [mailto:jim@xxxxxxxxxxxx] > > Sent: Tuesday, December 09, 2003 9:21 AM > > To: [ISAserver.org Discussion List] > > Subject: [isalist] Re: Terminal Services Installation > > > > > > http://www.ISAserver.org > > > > No, you don't "need" to install TSAC and IIS. > > It depends on whether or not you want to allow someone to use a browser to > > access your terminal servers. > > > > Jim Harrison > > MCP(NT4, W2K), A+, Network+, PCG > > http://www.microsoft.com/isaserver > > http://isaserver.org/Jim_Harrison > > http://isatools.org > > > > Read the help, books and articles! > > ----- Original Message ----- > > From: "Raji Arulambalam" <rajia@xxxxxxxxxxxxxx> > > To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> > > Sent: Monday, December 08, 2003 11:43 > > Subject: [isalist] Terminal Services Installation > > > > > > http://www.ISAserver.org > > > > Hi > > > > I want to install 2 Terminal Services Server internally, one is for Remote > > Administration only and the other in Application mode. Both on Windows > 2003 > > member servers. Both servers are S-Nat clients. I have a TS license server > > internally. > > My questions are, > > do I need to install IIS and the TS Web package on both machines ? > > If I need 2 IIS servers then on ISA server, do I need two Web and Server > > publishing rules or one would do.? > > I have 2 IP numbers bound to the external interface of the ISA server for > > these two servers. > > > > I have read Tom's tutorial on this, but want clarification on the above. > > > > Any help would be appreciated. > > > > Cheers > > > > --------------------------------------------- > > Raji Arulambalam > > Senior Systems Administrator > > Environment Bay of Plenty - Regional Council > > 5 Quay Street, P O Box 364, Whakatane, New Zealand > > -------------------------------------------- > > Murphy's Fifth Law: If anything just cannot go wrong, it will anyway. > > > > > > > > > > Email disclaimer: This email and any attachments are confidential. If you > > are not the intended recipient, do not copy, disclose or use the contents > in > > any way. If you receive this message in error, please let us know by > return > > email and then destroy the message. Environment Bay of Plenty is not > > responsible for any changes made to this message and/or any attachments > > after sending. > > ****************************************************** > > This e-mail has been checked for viruses and no viruses were detected. > > > > ------------------------------------------------------ > > 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: > > 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: > > jim@xxxxxxxxxxxx > > To unsubscribe send a blank email to $subst('Email.Unsub') > > > > > > ------------------------------------------------------ > > 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: > > 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: > thor@xxxxxxxxxxxxxxx > > To unsubscribe send a blank email to $subst('Email.Unsub') > > > > > ------------------------------------------------------ > 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: > 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: > jim@xxxxxxxxxxxx > To unsubscribe send a blank email to $subst('Email.Unsub') > > > ------------------------------------------------------ > 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: > 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: thor@xxxxxxxxxxxxxxx > To unsubscribe send a blank email to $subst('Email.Unsub') >