Problem with Terminal Services

Discussion in 'Microsoft Windows 2000' started by Guest, Oct 28, 2004.

  1. Guest

    Guest Guest

    I am having an issue with Terminal Services on 2000. I have XP
    clients that cannot connect through a firewall. To be specific, I
    have 2 clients that can connect, and all others can't. As far as I
    can tell the 2 clients have no different settings.

    TS on the server is version 5.0. All clients are 5.1. We even tried
    changing the port on the server but have still been unsuccessful,
    except for the two XP laptops.

    I put a sniffer on the network, and it doesn't appear that traffic
    even occurs between clients and the server. All clients can ping the
    server and can hit the admin share on the c drive. I even put a pc on
    the DMZ with the server and will still unable to connect, so it does
    not appear to be the FW.

    The only thing I can think of is maybe the certificates are screwed
    up. I tried the MS link on how to repair certificates (delteing a
    registry key) but it still didn't work.

    Does anyone have a suggestion on how I can get this to work?

    --
    Network Engineer
    MCSE, Network+
     
    Guest, Oct 28, 2004
    #1
    1. Advertisements

  2. "Andrew McGraw" <> wrote in message
    news:...
    > I am having an issue with Terminal Services on 2000. I have XP
    > clients that cannot connect through a firewall. To be specific, I
    > have 2 clients that can connect, and all others can't. As far as I
    > can tell the 2 clients have no different settings.
    >
    > TS on the server is version 5.0. All clients are 5.1. We even tried
    > changing the port on the server but have still been unsuccessful,
    > except for the two XP laptops.
    >
    > I put a sniffer on the network, and it doesn't appear that traffic
    > even occurs between clients and the server. All clients can ping the
    > server and can hit the admin share on the c drive. I even put a pc on
    > the DMZ with the server and will still unable to connect, so it does
    > not appear to be the FW.
    >
    > The only thing I can think of is maybe the certificates are screwed
    > up. I tried the MS link on how to repair certificates (delteing a
    > registry key) but it still didn't work.
    >
    > Does anyone have a suggestion on how I can get this to work?
    >
    > --
    > Network Engineer
    > MCSE, Network+


    What happens when you use telnet.exe (with the appropriate
    port) instead of the TS client?
     
    Pegasus \(MVP\), Oct 28, 2004
    #2
    1. Advertisements

  3. Guest

    Guest Guest

    If we attempt to telnet to the server using the new port (or the old port) we
    get teh connection attempt failed message. (Sorry, should have specified this
    earlier)

    "Pegasus (MVP)" wrote:

    >
    > "Andrew McGraw" <> wrote in message
    > news:...
    > > I am having an issue with Terminal Services on 2000. I have XP
    > > clients that cannot connect through a firewall. To be specific, I
    > > have 2 clients that can connect, and all others can't. As far as I
    > > can tell the 2 clients have no different settings.
    > >
    > > TS on the server is version 5.0. All clients are 5.1. We even tried
    > > changing the port on the server but have still been unsuccessful,
    > > except for the two XP laptops.
    > >
    > > I put a sniffer on the network, and it doesn't appear that traffic
    > > even occurs between clients and the server. All clients can ping the
    > > server and can hit the admin share on the c drive. I even put a pc on
    > > the DMZ with the server and will still unable to connect, so it does
    > > not appear to be the FW.
    > >
    > > The only thing I can think of is maybe the certificates are screwed
    > > up. I tried the MS link on how to repair certificates (delteing a
    > > registry key) but it still didn't work.
    > >
    > > Does anyone have a suggestion on how I can get this to work?
    > >
    > > --
    > > Network Engineer
    > > MCSE, Network+

    >
    > What happens when you use telnet.exe (with the appropriate
    > port) instead of the TS client?
    >
    >
    >
     
    Guest, Oct 28, 2004
    #3
  4. Since telnet fails too, the problem does obviously not relate
    to terminal services. Something is preventing your packets
    from geting through, either a firewall or a router. Put on a sniffer
    (e.g. Ethereal) and start analysing your traffic.


    "Andrew McGraw" <> wrote in message
    news:...
    > If we attempt to telnet to the server using the new port (or the old port)

    we
    > get teh connection attempt failed message. (Sorry, should have specified

    this
    > earlier)
    >
    > "Pegasus (MVP)" wrote:
    >
    > >
    > > "Andrew McGraw" <> wrote in

    message
    > > news:...
    > > > I am having an issue with Terminal Services on 2000. I have XP
    > > > clients that cannot connect through a firewall. To be specific, I
    > > > have 2 clients that can connect, and all others can't. As far as I
    > > > can tell the 2 clients have no different settings.
    > > >
    > > > TS on the server is version 5.0. All clients are 5.1. We even tried
    > > > changing the port on the server but have still been unsuccessful,
    > > > except for the two XP laptops.
    > > >
    > > > I put a sniffer on the network, and it doesn't appear that traffic
    > > > even occurs between clients and the server. All clients can ping the
    > > > server and can hit the admin share on the c drive. I even put a pc on
    > > > the DMZ with the server and will still unable to connect, so it does
    > > > not appear to be the FW.
    > > >
    > > > The only thing I can think of is maybe the certificates are screwed
    > > > up. I tried the MS link on how to repair certificates (delteing a
    > > > registry key) but it still didn't work.
    > > >
    > > > Does anyone have a suggestion on how I can get this to work?
    > > >
    > > > --
    > > > Network Engineer
    > > > MCSE, Network+

    > >
    > > What happens when you use telnet.exe (with the appropriate
    > > port) instead of the TS client?
    > >
    > >
    > >
     
    Pegasus \(MVP\), Oct 28, 2004
    #4
    1. Advertisements

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Jose R. Ilabaca

    Terminal Services can't start

    Jose R. Ilabaca, Jul 10, 2003, in forum: Microsoft Windows 2000
    Replies:
    0
    Views:
    2,090
    Jose R. Ilabaca
    Jul 10, 2003
  2. Hadi H.

    Terminal Services Licenses

    Hadi H., Aug 1, 2003, in forum: Microsoft Windows 2000
    Replies:
    0
    Views:
    228
    Hadi H.
    Aug 1, 2003
  3. Ricardo M. Urbano - W2K/NT4 MVP

    MS03-026/823980 over SP4 breaking Terminal Server/Services

    Ricardo M. Urbano - W2K/NT4 MVP, Aug 5, 2003, in forum: Microsoft Windows 2000
    Replies:
    5
    Views:
    273
    Ricardo M. Urbano - W2K/NT4 MVP
    Aug 7, 2003
  4. Pete

    What ports to open for Terminal Services

    Pete, Aug 19, 2003, in forum: Microsoft Windows 2000
    Replies:
    1
    Views:
    202
    Marc Reynolds [MSFT]
    Aug 19, 2003
  5. Jeremy

    Terminal Services

    Jeremy, Sep 8, 2003, in forum: Microsoft Windows 2000
    Replies:
    1
    Views:
    143
    Mark V
    Sep 10, 2003
  6. Darren

    Slow Loggoff in for Terminal Services

    Darren, Sep 15, 2003, in forum: Microsoft Windows 2000
    Replies:
    1
    Views:
    210
    Steve Parry [MVP]
    Sep 15, 2003
  7. Guest

    Problem with Terminal Services on 2003

    Guest, May 3, 2005, in forum: Microsoft Windows 2000
    Replies:
    3
    Views:
    148
    codigo
    May 4, 2005
  8. Guest

    Problem with Terminal Services auto login

    Guest, Nov 28, 2005, in forum: Microsoft Windows 2000
    Replies:
    3
    Views:
    382
    Dave Patrick
    Nov 28, 2005
Loading...