Accessing SBS 2000 TS from Internet

I am attempting to set up Terminal Server on my SBS 2000
machine to allow remote administration of the SBS from my
home. I have worked through configuring an ISA protocol
definition for port 3389, publishing the TS using the
defined protocol, binding to the internal network
adapter, and restarting server. I am still unable to
connect to the server from a remote PC running XP and
using the Remote Desktop Connection.

The SBS has 2 NICs with 1 connected directly to the DSL
modem. The remote XP box is on a LAN behind a Linksys
router connected to a cable modem. I can ping the SBS
box from home, but cannot ping the Linksys from the SBS
(maybe to be expected).

I am sure I have read a dozen knowledge base articles,
but to no avail.

This is giving me a headache, any help?

Thanks,
Mike

Cris
Wed Nov 19 22:08:19 CST 2003

if you are trying to connect from the internet to the TS server you should
just use the TS client

--
Cris Hanna [SBS-MVP]
-------------------------
Please do not directly to me but rather reply to the newsgroup so that all
may benefit from the information.
"Mike" <anonymous@discussions.microsoft.com> wrote in message
news:06dc01c3af14$d10d6ab0$a401280a@phx.gbl...
> I am attempting to set up Terminal Server on my SBS 2000
> machine to allow remote administration of the SBS from my
> home. I have worked through configuring an ISA protocol
> definition for port 3389, publishing the TS using the
> defined protocol, binding to the internal network
> adapter, and restarting server. I am still unable to
> connect to the server from a remote PC running XP and
> using the Remote Desktop Connection.
>
> The SBS has 2 NICs with 1 connected directly to the DSL
> modem. The remote XP box is on a LAN behind a Linksys
> router connected to a cable modem. I can ping the SBS
> box from home, but cannot ping the Linksys from the SBS
> (maybe to be expected).
>
> I am sure I have read a dozen knowledge base articles,
> but to no avail.
>
> This is giving me a headache, any help?
>
> Thanks,
> Mike

Rick
Wed Nov 19 22:40:00 CST 2003

I use Windows XP Remote Desktop without any issues.
Mike, remove what you tried to do in ISA and just run the ICW and check the
box to allow Terminal Services. That is all you need to do.

Rick in the Midwest

"Cris Hanna (SBS-MVP)" <crishannanospam@mindspring.com> wrote in message
news:OFtgbvxrDHA.2360@TK2MSFTNGP09.phx.gbl...
> if you are trying to connect from the internet to the TS server you should
> just use the TS client
>
> --
> Cris Hanna [SBS-MVP]
> -------------------------
> Please do not directly to me but rather reply to the newsgroup so that all
> may benefit from the information.
> "Mike" <anonymous@discussions.microsoft.com> wrote in message
> news:06dc01c3af14$d10d6ab0$a401280a@phx.gbl...
> > I am attempting to set up Terminal Server on my SBS 2000
> > machine to allow remote administration of the SBS from my
> > home. I have worked through configuring an ISA protocol
> > definition for port 3389, publishing the TS using the
> > defined protocol, binding to the internal network
> > adapter, and restarting server. I am still unable to
> > connect to the server from a remote PC running XP and
> > using the Remote Desktop Connection.
> >
> > The SBS has 2 NICs with 1 connected directly to the DSL
> > modem. The remote XP box is on a LAN behind a Linksys
> > router connected to a cable modem. I can ping the SBS
> > box from home, but cannot ping the Linksys from the SBS
> > (maybe to be expected).
> >
> > I am sure I have read a dozen knowledge base articles,
> > but to no avail.
> >
> > This is giving me a headache, any help?
> >
> > Thanks,
> > Mike
>
>

Chad
Thu Nov 20 01:50:31 CST 2003

Hi Mike -

As Rick indicated, the easiest solution is to re-run the ICW and select to
allow Terminal Services. But I thought I'd add a little info on why your
method wasn't working. Protocol rules apply to machines behind ISA, whereas
packet filters apply to the ISA server itself. If you want to have the ISA
server itself accept incoming traffic, you create an inbound packet filter.
If you want to have ISA accept incoming traffic and forward that traffic to
an internal machine, you create a server publishing rule. Since you want to
remotely administer the ISA server itself (that just so happens to be SBS
;^), you want to create a packet filter to allow your SBS to accept TS
connections. When you run the ICW and select to allow Terminal Services, the
ICW creates the necessary packet filter for you, so it just works.

HTH!

--
Chad A Gross [SBS-MVP]

SBS ROCKS!!!

Mike wrote:
> I am attempting to set up Terminal Server on my SBS 2000
> machine to allow remote administration of the SBS from my
> home. I have worked through configuring an ISA protocol
> definition for port 3389, publishing the TS using the
> defined protocol, binding to the internal network
> adapter, and restarting server. I am still unable to
> connect to the server from a remote PC running XP and
> using the Remote Desktop Connection.
>
> The SBS has 2 NICs with 1 connected directly to the DSL
> modem. The remote XP box is on a LAN behind a Linksys
> router connected to a cable modem. I can ping the SBS
> box from home, but cannot ping the Linksys from the SBS
> (maybe to be expected).
>
> I am sure I have read a dozen knowledge base articles,
> but to no avail.
>
> This is giving me a headache, any help?
>
> Thanks,
> Mike

Mike
Thu Nov 20 21:32:03 CST 2003

OK, I removed the configuration I had, and ran ICW and
specified TS. It all worked successfully but I am still
not able to connect from home using RDC. Am I missing
something like permissions? I do notice it now rejects
my connection much faster that previously. I am guessing
it is now finding the server but not accepting the
connection?

Thanks for the help.
Mike

>-----Original Message-----
>Hi Mike -
>
>As Rick indicated, the easiest solution is to re-run the
ICW and select to
>allow Terminal Services. But I thought I'd add a little
info on why your
>method wasn't working. Protocol rules apply to machines
behind ISA, whereas
>packet filters apply to the ISA server itself. If you
want to have the ISA
>server itself accept incoming traffic, you create an
inbound packet filter.
>If you want to have ISA accept incoming traffic and
forward that traffic to
>an internal machine, you create a server publishing
rule. Since you want to
>remotely administer the ISA server itself (that just so
happens to be SBS
>;^), you want to create a packet filter to allow your
SBS to accept TS
>connections. When you run the ICW and select to allow
Terminal Services, the
>ICW creates the necessary packet filter for you, so it
just works.
>
>HTH!
>
>--
>Chad A Gross [SBS-MVP]
>
>SBS ROCKS!!!
>
>Mike wrote:
>> I am attempting to set up Terminal Server on my SBS
2000
>> machine to allow remote administration of the SBS from
my
>> home. I have worked through configuring an ISA
protocol
>> definition for port 3389, publishing the TS using the
>> defined protocol, binding to the internal network
>> adapter, and restarting server. I am still unable to
>> connect to the server from a remote PC running XP and
>> using the Remote Desktop Connection.
>>
>> The SBS has 2 NICs with 1 connected directly to the DSL
>> modem. The remote XP box is on a LAN behind a Linksys
>> router connected to a cable modem. I can ping the SBS
>> box from home, but cannot ping the Linksys from the SBS
>> (maybe to be expected).
>>
>> I am sure I have read a dozen knowledge base articles,
>> but to no avail.
>>
>> This is giving me a headache, any help?
>>
>> Thanks,
>> Mike
>
>
>.
>

Don
Fri Nov 21 13:34:51 CST 2003

Make sure you have ticked the box that allows you to
logon to the terminal server in your user account under
Terminal Services Profile.

Don
>-----Original Message-----
>OK, I removed the configuration I had, and ran ICW and
>specified TS. It all worked successfully but I am still
>not able to connect from home using RDC. Am I missing
>something like permissions? I do notice it now rejects
>my connection much faster that previously. I am
guessing
>it is now finding the server but not accepting the
>connection?
>
>Thanks for the help.
>Mike
>
>>-----Original Message-----
>>Hi Mike -
>>
>>As Rick indicated, the easiest solution is to re-run
the
>ICW and select to
>>allow Terminal Services. But I thought I'd add a
little
>info on why your
>>method wasn't working. Protocol rules apply to
machines
>behind ISA, whereas
>>packet filters apply to the ISA server itself. If you
>want to have the ISA
>>server itself accept incoming traffic, you create an
>inbound packet filter.
>>If you want to have ISA accept incoming traffic and
>forward that traffic to
>>an internal machine, you create a server publishing
>rule. Since you want to
>>remotely administer the ISA server itself (that just so
>happens to be SBS
>>;^), you want to create a packet filter to allow your
>SBS to accept TS
>>connections. When you run the ICW and select to allow
>Terminal Services, the
>>ICW creates the necessary packet filter for you, so it
>just works.
>>
>>HTH!
>>
>>--
>>Chad A Gross [SBS-MVP]
>>
>>SBS ROCKS!!!
>>
>>Mike wrote:
>>> I am attempting to set up Terminal Server on my SBS
>2000
>>> machine to allow remote administration of the SBS
from
>my
>>> home. I have worked through configuring an ISA
>protocol
>>> definition for port 3389, publishing the TS using the
>>> defined protocol, binding to the internal network
>>> adapter, and restarting server. I am still unable to
>>> connect to the server from a remote PC running XP and
>>> using the Remote Desktop Connection.
>>>
>>> The SBS has 2 NICs with 1 connected directly to the
DSL
>>> modem. The remote XP box is on a LAN behind a Linksys
>>> router connected to a cable modem. I can ping the SBS
>>> box from home, but cannot ping the Linksys from the
SBS
>>> (maybe to be expected).
>>>
>>> I am sure I have read a dozen knowledge base articles,
>>> but to no avail.
>>>
>>> This is giving me a headache, any help?
>>>
>>> Thanks,
>>> Mike
>>
>>
>>.
>>
>.
>

Mike
Fri Nov 21 15:05:18 CST 2003

It works!

Thanks to all those who helped, it is much appreciated.
Mike

>-----Original Message-----
>Make sure you have ticked the box that allows you to
>logon to the terminal server in your user account under
>Terminal Services Profile.
>
>Don
>>-----Original Message-----
>>OK, I removed the configuration I had, and ran ICW and
>>specified TS. It all worked successfully but I am
still
>>not able to connect from home using RDC. Am I missing
>>something like permissions? I do notice it now rejects
>>my connection much faster that previously. I am
>guessing
>>it is now finding the server but not accepting the
>>connection?
>>
>>Thanks for the help.
>>Mike
>>
>>>-----Original Message-----
>>>Hi Mike -
>>>
>>>As Rick indicated, the easiest solution is to re-run
>the
>>ICW and select to
>>>allow Terminal Services. But I thought I'd add a
>little
>>info on why your
>>>method wasn't working. Protocol rules apply to
>machines
>>behind ISA, whereas
>>>packet filters apply to the ISA server itself. If you
>>want to have the ISA
>>>server itself accept incoming traffic, you create an
>>inbound packet filter.
>>>If you want to have ISA accept incoming traffic and
>>forward that traffic to
>>>an internal machine, you create a server publishing
>>rule. Since you want to
>>>remotely administer the ISA server itself (that just
so
>>happens to be SBS
>>>;^), you want to create a packet filter to allow your
>>SBS to accept TS
>>>connections. When you run the ICW and select to allow
>>Terminal Services, the
>>>ICW creates the necessary packet filter for you, so it
>>just works.
>>>
>>>HTH!
>>>
>>>--
>>>Chad A Gross [SBS-MVP]
>>>
>>>SBS ROCKS!!!
>>>
>>>Mike wrote:
>>>> I am attempting to set up Terminal Server on my SBS
>>2000
>>>> machine to allow remote administration of the SBS
>from
>>my
>>>> home. I have worked through configuring an ISA
>>protocol
>>>> definition for port 3389, publishing the TS using the
>>>> defined protocol, binding to the internal network
>>>> adapter, and restarting server. I am still unable to
>>>> connect to the server from a remote PC running XP and
>>>> using the Remote Desktop Connection.
>>>>
>>>> The SBS has 2 NICs with 1 connected directly to the
>DSL
>>>> modem. The remote XP box is on a LAN behind a
Linksys
>>>> router connected to a cable modem. I can ping the
SBS
>>>> box from home, but cannot ping the Linksys from the
>SBS
>>>> (maybe to be expected).
>>>>
>>>> I am sure I have read a dozen knowledge base
articles,
>>>> but to no avail.
>>>>
>>>> This is giving me a headache, any help?
>>>>
>>>> Thanks,
>>>> Mike
>>>
>>>
>>>.
>>>
>>.
>>
>.
>