From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_096B_01C314D9.58811860
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   If you have Network Monitor installed on the client you can capture =
the network traffic on the client to see what if anything is returned by =
the server.  If you don't have NetMon installed on the server, install =
it.  It's a Windows component.  Capture the traffic there and see if =
anything is coming from the client.

   If you have multiple network adapters check if you have Terminal =
Services configured to listen only on specific adapters.

   Finally, try telnet from the same client to a different port on the =
server, say 445.

Rich

  "David Blair"  wrote in message =
news:3eb9cfc8{at}w3.nls.net...
  Here's what happened:

  E:\Documents and Settings\David R. Blair>telnet 192.168.0.54 3389
  Connecting To 192.168.0.54...Could not open connection to the host, on =
port 3389
  : Connect failed


  So, I take it there is something I need to look at in the network =
layers. I didn't change anything, but something obviously is wrong. I = can
start a TS session back to it's own TS server, by the way (which is = too
bizarre for me!) What should I look at?=20

  By the way, this machine is the only one on a wireless adapter.
    "Rich"  wrote in message news:3eb9c324{at}w3.nls.net...
       Test if you can telnet from the problem client to port 3389 on =
the server.  If not, the problem is in the network layers and not =
Terminal Services.

       If telnet works, go to the server and clear the event logs then =
attempt to connect.  Look to see if the logs have anything interesting.

    Rich


------=_NextPart_000_096B_01C314D9.58811860
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   If you
have Network =
Monitor installed=20
on the client you can capture the network traffic on the client to see = what if=20
anything is returned by the server.  If you don't have NetMon =
installed on=20
the server, install it.  It's a Windows component. 
Capture = the=20
traffic there and see if anything is coming from the =
client.
 
   If you
have multiple =
network adapters=20
check if you have Terminal Services configured to listen only on = specific=20
adapters.
 
   Finally,
try telnet from =
the same=20
client to a different port on the server, say 445.
 
Rich
 

  "David Blair" <drb{at}u-spam-u-die.com>">mailto:drb{at}u-spam-u-die.com">drb{at}u-spam-u-die.com>
=
wrote in=20
  message news:3eb9cfc8{at}w3.nls.net...
  Here's what
happened:
   
  E:\Documents and Settings\David R.=20
  Blair>telnet 192.168.0.54 3389Connecting To =
192.168.0.54...Could not=20
  open connection to the host, on port 3389: Connect =
failed
   
  So, I take it there is something I =
need to look=20
  at in the network layers. I didn't change anything, but something =
obviously is=20
  wrong. I can start a TS session back to it's own TS server, by the way =
(which=20
  is too bizarre for me!) What should I look at? 
   
  By the way, this machine is the only =
one on a=20
  wireless adapter.
  

    "Rich" <{at}> wrote in message news:3eb9c324{at}w3.nls.net...
       Test
if you can telnet =
from the=20
    problem client to port 3389 on the server.  If not, the problem =
is in=20
    the network layers and not Terminal Services.
     
       If
telnet works, go to =
the server=20
    and clear the event logs then attempt to connect.  Look to see =
if the=20
    logs have anything interesting.
     
    Rich
     
    
 

------=_NextPart_000_096B_01C314D9.58811860--

--- BBBS/NT v4.01 Flag-4