From: "David Blair" 

This is a multi-part message in MIME format.

------=_NextPart_000_000D_01C314F0.8F163650
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I just discovered the issue, and it is something which really ticks me = off.=20

I have a Sygate software firewall installed on the machine, but it is =
disabled at the moment because it was causing some issues I haven't had =
the time (or inclination) to deal with for now. I set it to be disabled =
at startup, assuming that was that- it wouldn't start at boot time = unless
I manually started it.

Wrong.


I noticed suddenly all my drive mappings went awry on my other machines.

I started looking at the server and tried restarting the Server service, =
and looking at everything in there, when I noticed... Sygate service was =
started. After I had told it NOT to start at boot.=20

Nasty email to Sygate to follow. What really is irksome is I = specifically
recall having manually set that service not to start = previously.

Thanks for having been there trying to help. It's hard to debug a = problem
when someone else's product isn't doing what they say it will = do.

By the way, I'm not sure if I installed NetMon or not. I usually try to =
install everything I can find to install on the CD. And I do have =
multiple adaptors, but only 1 is employed.

I wasted 4 hours on this and missed half of a baseball game. I'm REALLY =
pissed. I don't mind chasing problems when they're legit, but I really =
don't like it when I disable something and it doesn't really disable =
itself.=20

(Unfortunately, I expect the reply will be "unsupported on
pre-released = platforms.")

Ack! Thanks, again, Rich. I always appreciate the help.
  "Rich"  wrote in message news:3eb9d1d5$1{at}w3.nls.net...
     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_000D_01C314F0.8F163650
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








I just discovered the issue, and it is =
something=20
which really ticks me off. 
 
I have a Sygate software firewall =
installed on the=20
machine, but it is disabled at the moment because it was causing some = issues I=20
haven't had the time (or inclination) to deal with for now. I set it to = be=20
disabled at startup, assuming that was that- it wouldn't start at boot = time=20
unless I manually started it.
 
Wrong.
 
 
I noticed suddenly all my drive =
mappings went awry=20
on my other machines.
 
I started looking at the server and =
tried=20
restarting the Server service, and looking at everything in there, when = I=20
noticed... Sygate service was started. After I had told it NOT to start = at boot.=20

 
Nasty email to Sygate to follow. What =
really is=20
irksome is I specifically recall having manually set that service not to = start=20
previously.
 
Thanks for having been there trying to =
help. It's=20
hard to debug a problem when someone else's product isn't doing what = they say it=20
will do.
 
By the way, I'm not sure if I
installed =
NetMon or=20
not. I usually try to install everything I can find to install on the = CD. And I=20
do have multiple adaptors, but only 1 is employed.
 
I wasted 4 hours on this and missed =
half of a=20
baseball game. I'm REALLY pissed. I don't mind chasing problems when = they're=20
legit, but I really don't like it when I disable something and it = doesn't really=20
disable itself. 
 
(Unfortunately, I expect the
reply will =
be=20
"unsupported on pre-released platforms.")
 
Ack! Thanks, again, Rich. I always =
appreciate the=20
help.

  "Rich" <{at}> wrote in message news:3eb9d1d5$1{at}w3.nls.net...
     If you
have Network =
Monitor=20
  installed on the client you can capture the network traffic on the =
client to=20
  see what if anything is returned by the server.  If you don't =
have NetMon=20
  installed on the server, install it.  It's a Windows =
component. =20
  Capture the traffic there and see if anything is coming from the=20
  client.
   
     If you
have multiple =
network=20
  adapters check if you have Terminal Services configured to listen only =
on=20
  specific 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=20
    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=20
    is wrong. I can start a TS session back to it's own TS server, by =
the way=20
    (which 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=20
      server and clear the event logs then attempt to connect.  =
Look to see=20
      if the logs have anything interesting.
       
      Rich
       
      
 

------=_NextPart_000_000D_01C314F0.8F163650--

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