TIP: Click on subject to list as thread! ANSI
echo: nthelp
to: All
from: David Blair
date: 2003-05-07 22:33:54
subject: Re: Terminal services/other

From: "David Blair" 

This is a multi-part message in MIME format.

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

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_000A_01C314E8.BE7A2530
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








Here's what
happened:
 
E:\Documents and Settings\David R. =
Blair>telnet=20
192.168.0.54 3389Connecting To 192.168.0.54...Could not open =
connection to=20
the host, on port 3389: Connect failed
 
So, I take it there is
something I need =
to look at=20
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 is=20
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 the=20 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_000A_01C314E8.BE7A2530-- --- BBBS/NT v4.01 Flag-4
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/1.45)
SEEN-BY: 633/267 270
@PATH: 379/1 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.