I need to get Terminal services over the Web to work. Initially I
installed Terminal services (configured for Remote Admin) on a server.
Then installed the TSWeb files to the server thus creating the TsWeb
virtual directory. Do I need to enable any specific security that is
not configured by the TsWeb exe?

I was able to get to a machine on the LAN from a sep machine on the
LAN via web browser by entering the serverName/Tsweb into the Ie web
address. When asked for the server name (within the TSWeb logon box) I
entered the name of the system I want to control. This proved that it
could work.

I then opened ports 3389 and 80 and routed them to the server. Tried
to connect ti my client's workstation via the internet and the WAN ip
address followed by a "/tsweb." This retunred an error message of
"The specified remote computer could not be found. Verify that you
have
typed the correct computer name or IP address, and then try
connecting
again."

I figured maybe it was due to the fact I had TSWeb running on the same
machine as SBS 2k. Split it onto a new system and lo and behold same
issue. I tried to open ports 1234 (had IIS listen on the port) and
3389 and routed them to the new server, same result. I tried the user
internal ip, the users full name Machine.domain.com. No good.

I now need major help and need it fast because my client is beginning
to get upset.

Re: Getting TSWEb to work. Need help badly. by SuperGumby

SuperGumby
Tue Dec 09 06:21:44 CST 2003

it's going wrong in several places, read on.

"Ronrf1" <Ronrf1@yahoo.com> wrote in message
news:cf3b20bf.0312082123.20d0dd9d@posting.google.com...
> I need to get Terminal services over the Web to work. Initially I
> installed Terminal services (configured for Remote Admin) on a server.
> Then installed the TSWeb files to the server thus creating the TsWeb
> virtual directory. Do I need to enable any specific security that is
> not configured by the TsWeb exe?

OK, I believe you are talking about SBS, so I hope you have only enabled TS
in in Admin mode, SBS is not well suited to being an Application Mode TS.

But as your real objective sems to be to give Internet users access to
machines behind SBS the fact you do/don't have TS enabled on the SBS is
irrelevant (sort of).

> I was able to get to a machine on the LAN from a sep machine on the
> LAN via web browser by entering the serverName/Tsweb into the Ie web
> address. When asked for the server name (within the TSWeb logon box) I
> entered the name of the system I want to control. This proved that it
> could work.

Yep, once the control from http://server/tsweb is loaded it can connect to
any TS.

> I then opened ports 3389 and 80 and routed them to the server. Tried
> to connect ti my client's workstation via the internet and the WAN ip
> address followed by a "/tsweb." This retunred an error message of
> "The specified remote computer could not be found. Verify that you
> have
> typed the correct computer name or IP address, and then try
> connecting
> again."

Here we start to need info about your network topology. You have a router.
One NIC or two in SBS? is the router in front of or behind SBS? If you're
using one NIC ISA can be ignored and if you're using two NICs we will assume
the router is connected to your 'external' NIC, until advised otherwise.

> I figured maybe it was due to the fact I had TSWeb running on the same
> machine as SBS 2k. Split it onto a new system and lo and behold same
> issue. I tried to open ports 1234 (had IIS listen on the port) and
> 3389 and routed them to the new server, same result. I tried the user
> internal ip, the users full name Machine.domain.com. No good.

This par is of little use till we know what's asked above.

> I now need major help and need it fast because my client is beginning
> to get upset.

He didn't have the facility yesterday.
He didn't have the facility last week.
He didn't have the facility a month ago.
He didn't have the facility a year ago.
He didn't have the facility ten years ago.
Just why is he getting upset because he can't have it tomorrow?



Re: Getting TSWEb to work. Need help badly. by Ronrf1

Ronrf1
Tue Dec 09 19:23:51 CST 2003

The network is configured as follows. The SBS server is only running
Exchange, DNS and of course as a DC. The server is connected to the Gb
ethernet port on a DELL 24-port switch. The switch is connected to an
Asante firewall/Router, the router is connected to the VerizonDSL
modem. The router has the following ports open and routed to the SBS
server (80, 25 and 3389).

ISA is not being used and and the server only has one NIC.


"SuperGumby" <not@your.nellie> wrote in message news:<OZz6R8kvDHA.684@TK2MSFTNGP09.phx.gbl>...
> it's going wrong in several places, read on.
>
> "Ronrf1" <Ronrf1@yahoo.com> wrote in message
> news:cf3b20bf.0312082123.20d0dd9d@posting.google.com...
> > I need to get Terminal services over the Web to work. Initially I
> > installed Terminal services (configured for Remote Admin) on a server.
> > Then installed the TSWeb files to the server thus creating the TsWeb
> > virtual directory. Do I need to enable any specific security that is
> > not configured by the TsWeb exe?
>
> OK, I believe you are talking about SBS, so I hope you have only enabled TS
> in in Admin mode, SBS is not well suited to being an Application Mode TS.
>
> But as your real objective sems to be to give Internet users access to
> machines behind SBS the fact you do/don't have TS enabled on the SBS is
> irrelevant (sort of).
>
> > I was able to get to a machine on the LAN from a sep machine on the
> > LAN via web browser by entering the serverName/Tsweb into the Ie web
> > address. When asked for the server name (within the TSWeb logon box) I
> > entered the name of the system I want to control. This proved that it
> > could work.
>
> Yep, once the control from http://server/tsweb is loaded it can connect to
> any TS.
>
> > I then opened ports 3389 and 80 and routed them to the server. Tried
> > to connect ti my client's workstation via the internet and the WAN ip
> > address followed by a "/tsweb." This retunred an error message of
> > "The specified remote computer could not be found. Verify that you
> > have
> > typed the correct computer name or IP address, and then try
> > connecting
> > again."
>
> Here we start to need info about your network topology. You have a router.
> One NIC or two in SBS? is the router in front of or behind SBS? If you're
> using one NIC ISA can be ignored and if you're using two NICs we will assume
> the router is connected to your 'external' NIC, until advised otherwise.
>
> > I figured maybe it was due to the fact I had TSWeb running on the same
> > machine as SBS 2k. Split it onto a new system and lo and behold same
> > issue. I tried to open ports 1234 (had IIS listen on the port) and
> > 3389 and routed them to the new server, same result. I tried the user
> > internal ip, the users full name Machine.domain.com. No good.
>
> This par is of little use till we know what's asked above.
>
> > I now need major help and need it fast because my client is beginning
> > to get upset.
>
> He didn't have the facility yesterday.
> He didn't have the facility last week.
> He didn't have the facility a month ago.
> He didn't have the facility a year ago.
> He didn't have the facility ten years ago.
> Just why is he getting upset because he can't have it tomorrow?

Re: Getting TSWEb to work. Need help badly. by SuperGumby

SuperGumby
Tue Dec 09 19:45:13 CST 2003

OK. Houston, we have a problem, but only a slight one.

You have one public IP address so any request to FQDN:3389 has to be
forwarded to a single internal IP, at this time it is SBS, but you want it
to go to another server. Easy, change the forwarding in the firewall. But
you lose external access to SBS for management, again, easy, from outside
you can establish a TS on the TS App server, then TS to the SBS from there.
Perfectly valid.

or you run a VPN and then TS to either box through the VPN.

It's even reasonable to have http://FQDN/tsweb pointing to the SBS yet
FQDN:3389 pointing to the application server.

"Ronrf1" <Ronrf1@yahoo.com> wrote in message
news:cf3b20bf.0312091723.38c070e4@posting.google.com...
> The network is configured as follows. The SBS server is only running
> Exchange, DNS and of course as a DC. The server is connected to the Gb
> ethernet port on a DELL 24-port switch. The switch is connected to an
> Asante firewall/Router, the router is connected to the VerizonDSL
> modem. The router has the following ports open and routed to the SBS
> server (80, 25 and 3389).
>
> ISA is not being used and and the server only has one NIC.
>
>
> "SuperGumby" <not@your.nellie> wrote in message
news:<OZz6R8kvDHA.684@TK2MSFTNGP09.phx.gbl>...
> > it's going wrong in several places, read on.
> >
> > "Ronrf1" <Ronrf1@yahoo.com> wrote in message
> > news:cf3b20bf.0312082123.20d0dd9d@posting.google.com...
> > > I need to get Terminal services over the Web to work. Initially I
> > > installed Terminal services (configured for Remote Admin) on a server.
> > > Then installed the TSWeb files to the server thus creating the TsWeb
> > > virtual directory. Do I need to enable any specific security that is
> > > not configured by the TsWeb exe?
> >
> > OK, I believe you are talking about SBS, so I hope you have only enabled
TS
> > in in Admin mode, SBS is not well suited to being an Application Mode
TS.
> >
> > But as your real objective sems to be to give Internet users access to
> > machines behind SBS the fact you do/don't have TS enabled on the SBS is
> > irrelevant (sort of).
> >
> > > I was able to get to a machine on the LAN from a sep machine on the
> > > LAN via web browser by entering the serverName/Tsweb into the Ie web
> > > address. When asked for the server name (within the TSWeb logon box) I
> > > entered the name of the system I want to control. This proved that it
> > > could work.
> >
> > Yep, once the control from http://server/tsweb is loaded it can connect
to
> > any TS.
> >
> > > I then opened ports 3389 and 80 and routed them to the server. Tried
> > > to connect ti my client's workstation via the internet and the WAN ip
> > > address followed by a "/tsweb." This retunred an error message of
> > > "The specified remote computer could not be found. Verify that you
> > > have
> > > typed the correct computer name or IP address, and then try
> > > connecting
> > > again."
> >
> > Here we start to need info about your network topology. You have a
router.
> > One NIC or two in SBS? is the router in front of or behind SBS? If
you're
> > using one NIC ISA can be ignored and if you're using two NICs we will
assume
> > the router is connected to your 'external' NIC, until advised otherwise.
> >
> > > I figured maybe it was due to the fact I had TSWeb running on the same
> > > machine as SBS 2k. Split it onto a new system and lo and behold same
> > > issue. I tried to open ports 1234 (had IIS listen on the port) and
> > > 3389 and routed them to the new server, same result. I tried the user
> > > internal ip, the users full name Machine.domain.com. No good.
> >
> > This par is of little use till we know what's asked above.
> >
> > > I now need major help and need it fast because my client is beginning
> > > to get upset.
> >
> > He didn't have the facility yesterday.
> > He didn't have the facility last week.
> > He didn't have the facility a month ago.
> > He didn't have the facility a year ago.
> > He didn't have the facility ten years ago.
> > Just why is he getting upset because he can't have it tomorrow?



Re: Getting TSWEb to work. Need help badly. by Ronrf1

Ronrf1
Wed Dec 10 19:50:45 CST 2003

I have not been using SBS management. I will re-route the the port
back to the SBS server. Could you please help me climb out?


"SuperGumby" <not@your.nellie> wrote in message news:<eLVMF9rvDHA.2460@TK2MSFTNGP10.phx.gbl>...
> OK. Houston, we have a problem, but only a slight one.
>
> You have one public IP address so any request to FQDN:3389 has to be
> forwarded to a single internal IP, at this time it is SBS, but you want it
> to go to another server. Easy, change the forwarding in the firewall. But
> you lose external access to SBS for management, again, easy, from outside
> you can establish a TS on the TS App server, then TS to the SBS from there.
> Perfectly valid.
>
> or you run a VPN and then TS to either box through the VPN.
>
> It's even reasonable to have http://FQDN/tsweb pointing to the SBS yet
> FQDN:3389 pointing to the application server.
>
> "Ronrf1" <Ronrf1@yahoo.com> wrote in message
> news:cf3b20bf.0312091723.38c070e4@posting.google.com...
> > The network is configured as follows. The SBS server is only running
> > Exchange, DNS and of course as a DC. The server is connected to the Gb
> > ethernet port on a DELL 24-port switch. The switch is connected to an
> > Asante firewall/Router, the router is connected to the VerizonDSL
> > modem. The router has the following ports open and routed to the SBS
> > server (80, 25 and 3389).
> >
> > ISA is not being used and and the server only has one NIC.
> >
> >
> > "SuperGumby" <not@your.nellie> wrote in message
> news:<OZz6R8kvDHA.684@TK2MSFTNGP09.phx.gbl>...
> > > it's going wrong in several places, read on.
> > >
> > > "Ronrf1" <Ronrf1@yahoo.com> wrote in message
> > > news:cf3b20bf.0312082123.20d0dd9d@posting.google.com...
> > > > I need to get Terminal services over the Web to work. Initially I
> > > > installed Terminal services (configured for Remote Admin) on a server.
> > > > Then installed the TSWeb files to the server thus creating the TsWeb
> > > > virtual directory. Do I need to enable any specific security that is
> > > > not configured by the TsWeb exe?
> > >
> > > OK, I believe you are talking about SBS, so I hope you have only enabled
> TS
> > > in in Admin mode, SBS is not well suited to being an Application Mode
> TS.
> > >
> > > But as your real objective sems to be to give Internet users access to
> > > machines behind SBS the fact you do/don't have TS enabled on the SBS is
> > > irrelevant (sort of).
> > >
> > > > I was able to get to a machine on the LAN from a sep machine on the
> > > > LAN via web browser by entering the serverName/Tsweb into the Ie web
> > > > address. When asked for the server name (within the TSWeb logon box) I
> > > > entered the name of the system I want to control. This proved that it
> > > > could work.
> > >
> > > Yep, once the control from http://server/tsweb is loaded it can connect
> to
> > > any TS.
> > >
> > > > I then opened ports 3389 and 80 and routed them to the server. Tried
> > > > to connect ti my client's workstation via the internet and the WAN ip
> > > > address followed by a "/tsweb." This retunred an error message of
> > > > "The specified remote computer could not be found. Verify that you
> > > > have
> > > > typed the correct computer name or IP address, and then try
> > > > connecting
> > > > again."
> > >
> > > Here we start to need info about your network topology. You have a
> router.
> > > One NIC or two in SBS? is the router in front of or behind SBS? If
> you're
> > > using one NIC ISA can be ignored and if you're using two NICs we will
> assume
> > > the router is connected to your 'external' NIC, until advised otherwise.
> > >
> > > > I figured maybe it was due to the fact I had TSWeb running on the same
> > > > machine as SBS 2k. Split it onto a new system and lo and behold same
> > > > issue. I tried to open ports 1234 (had IIS listen on the port) and
> > > > 3389 and routed them to the new server, same result. I tried the user
> > > > internal ip, the users full name Machine.domain.com. No good.
> > >
> > > This par is of little use till we know what's asked above.
> > >
> > > > I now need major help and need it fast because my client is beginning
> > > > to get upset.
> > >
> > > He didn't have the facility yesterday.
> > > He didn't have the facility last week.
> > > He didn't have the facility a month ago.
> > > He didn't have the facility a year ago.
> > > He didn't have the facility ten years ago.
> > > Just why is he getting upset because he can't have it tomorrow?