Javier
Fri Feb 27 14:32:58 CST 2004
Hello!
If you want to do the SBS box... it is much simpler than that. Just disable
whatever you created before and rerun ICW... on the packet filter screen you
will get an option for terminal server (i think) which you need to enable.
Or simply create a packet filter manually for TCP 3389 inbound.
Just remember that you don't use server publishing rules for the SBS itself.
Have a good one!
--
Javier [SBS MVP]
<< SBS ROCKS !!! >>
"nic" <anonymous@discussions.microsoft.com> wrote in message
news:389301c3fd65$6e263db0$a101280a@phx.gbl...
> Thanks for the help. To simplify things I'm trying to
> just connect to the terminal server on the SBS box. Once
> I get that up, I'll try to connect to the 2nd server
> (change the server publishing rule to point to the other
> computer.)
> I also followed all the steps on this article:
>
http://support.microsoft.com/default.aspx?scid=kb;en-
> us;294720
>
> I can't move hubs/switches right now but I will try this
> weekend. I will let you know what happens. (I didn't want
> you wondering why I didn't respond.)
>
> Thanks once again for your help and I'll let you know what
> happens on Monday.
>
>
> >-----Original Message-----
> >Hi!
> >
> >Do you have the firewall client installed on the 2nd
> server? I think you
> >need it in order it to work.
> >
> >Let's see if ISA is the problem-> Can you connect a
> computer to the external
> >NIC of the server (i.e put a hub/switch between the
> Router and ISA to
> >connect the computer there). Now using the IP of the
> external NIC try to
> >connect from the workstation... if you are not able to
> then you have an ISA
> >problem. Let me know so we can proceed to work the
> problem out.
> >
> >Cheers,
> >
> >--
> >Javier [SBS MVP]
> >
> ><< SBS ROCKS !!! >>
> >
> >"nic" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:32f301c3fd5d$a8767ff0$a501280a@phx.gbl...
> >> I called our service provider and the router sitting
> >> infront of ISA allows all ports through. There is no
> >> blocking due to the router.
> >>
> >> >-----Original Message-----
> >> >Hi,
> >> >I'm trying to get terminal server up and running in
> >> remote
> >> >admin mode. It works fine internally but when I try to
> >> >access it externally I get an "The specified remote
> >> >computer could not be found." error. I published the
> >> >server through ISA by creating a protocol definition
> >> using
> >> >TCP, port 3389, inbound. I server published the
> >> >definition by supplying the external and internal nics
> (2
> >> >nic setup). We do have a router sitting in front of
> our
> >> >ISA server. We have dsl and this router was installed
> by
> >> >our service provider. All traffic should route through
> >> >the router. I have server/web published a number of
> >> >protocols on the server so I'm fairly comfortable with
> >> >ISA. I just don't see what could be the issue. I
> tried
> >> >to telnet to port 3389 and it said connection could not
> >> be
> >> >established. But I don't know if you can even use
> telnet
> >> >to test terminal server. Any ideas on how I can find
> out
> >> >where the bottleneck is? I can't even tell if the
> >> request
> >> >is even making it to the server. Any help would be
> >> >appreciated.
> >> >.
> >> >
> >
> >
> >.
> >