Terminal Service (web and RD client) through FVS318

  • Thread starter Thread starter Terry G
  • Start date Start date
T

Terry G

I have a FVS318 in my office that performs firewall / routing / nat
for the machines in my office.

We share our DSL line with a building company that isn't behind this
particular brand of firewall though.

Here is my problem though. I have a Win2k SBS at my home running
Terminal Server over the web. I can connect up to it without fail
from any machine I use EXCEPT the ones behind the FVS318. By this I
mean, I can go to one of our neighbors computers (same DSL line and
such, just not behind the FVS) and connect up without a problem.

Anyone have any insights to this? I know the machine is up and
running. I can connect up to the Terminal Services web page but when
I hit connect I get the error message that would lead you to believe
the server is busy. Yet .. go to a different machine and can pop in
np.

-T
 
Cool. Someone else who is probably seeing the same
problem, I just posted in the Termserv.apps NG.

Try using the old Win32 RDP client, you may find it works.
If your machine was just upgraded with SP4, I think the SP
did something to TSWeb through a firewall, but still
permits its use behind a firewall.

If you see the same thing, then the problem is <not> the
firewall, it's some kind of permissions hand-off between
IIS and TS. Pure speculation, am considering variables
like trusted machine, logged in with Domain Account (or
other trusted account instead of logging into Windows with
one name and TS with another).

But, at this early stage just wondering if this has been
encountered by people before.

Tony Su
Su Network Consulting
 
-----Original Message-----


I can ping the Terminal Services server but cannot telnet to port
3389. Actually I had read quite a few of the messages that you had
put out asking if people were able to do that but hadn't posted it in
my original message.
Click to expand...

If you are unable to telnet to port 3389, then that is why
your terminal services connection is failing. TS works
over 3389, so not having that port open for connects is a
big problem. I would verify that the port is open on your
firewall and being forwarded to the terminal server.

-M
 
Back
Top