Re: SBS ISA 2004 + Publishing Terminal Server

Although it doesn't answer your question, it might take care of your
problem.

In the SBS world the recommended way of doing this would be to leave the SBS
at its standard ports. Then you join your application TS into the domain
with ConnectComputer. After you ran the CEICW your users would connect to
RWW and then select the TS box to connect to. This works with a 2000 box as
well as a 2003 box.

--
Claus
<jdr.smith@xxxxxxxxxx> wrote in message
news:978853ef-7431-46a4-be78-a152ec5c97bb@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

OK this has got me a bit puzzled.

I've disabled the default SBS RDP Server Access Rule in ISA 2004.

I have then published a new server by creating a server publishing
rule to point RDP on the default port 3389 to the internal Terminal
Server. This works fine.

Now...what I'd also like to do is to publish the SBS 2003 server on a
different non-standard port.

So I create another server publishing rule to do this and save the
changes..voila..works just fine.

I can now access the Terminal Server directly on the default port and
I can also access the SBS 2003 server on the same public IP but
specifiying the non standard port at the end.

..until I reboot the SBS 2003 server...then it no longer works....

This always and **ONLY** seems to happen when I have a Windows 2000
Terminal Server in the mix, if it was a Windows 2003 Terminal Server
then I know for certain that this would not play me up.

Anyone any ideas why this happens ? and why does it work OK up until
the point the SBS 2003 server is retarted.

I've tested this on a test rig as well, exactly the same thing
happens.

Its OK with a Windows 2003 TS, but falls over after a restart of the
SBS 2003 server if the TS is Windows 2000. ie access to the Windows
2000 TS still works but can no longer access the SBS 2003 on the non-
standard port.
If I delete the rule and recreate it it still doesn't work. It only
works first time out and up until the SBS 2003 server is restarted.
I'm just a bit puzzled why this happens.

Jim.


.

Relevant Pages

  • RE: Service Pack 1 on SBS 2003 Premium
    ... reinstalled the SP1 from CD again, ... Restart Windows Management Instrumentation service. ... Close the registry editor and restart the server at a non-business time ... Have you applied the whole SBS SP1 successfully? ...
    (microsoft.public.windows.server.sbs)
  • RE: Service Pack 1 on SBS 2003 Premium
    ... reinstalled the SP1 from CD again, ... Restart Windows Management Instrumentation service. ... Close the registry editor and restart the server at a non-business time ... Have you applied the whole SBS SP1 successfully? ...
    (microsoft.public.windows.server.sbs)
  • Re: The list of servers for this workgroup is not currently availi
    ... Select Windows Small Business Server 2003 and then click Change/Remove. ... You may prompt to inset SBS installation CD. ... Our only problem w/ connecting to the branch office is mapping ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Standard - Update to SP 1 fails
    ... order to prepare SBS server to deploy Windows XP SP2 to client computers ... that are running Windows XP Professional. ... The SBS SP1 launcher need copy ... please install it and then ...
    (microsoft.public.windows.server.sbs)
  • RE: Service Pack 1 on SBS 2003 Premium
    ... You can monitor your server for some time to the Companyweb ... This newsgroup only focuses on SBS technical issues. ... >reinstalled the SP1 from CD again, ... Stop Windows Management ...
    (microsoft.public.windows.server.sbs)
Loading