PC Review


Reply
Thread Tools Rate Thread

Can't connect via TermServ nor RDP

 
 
=?Utf-8?B?VFRpbWU=?=
Guest
Posts: n/a
 
      12th Sep 2005
For some reason simple RDP or Terminal Services will not connect to one
particular server (not running licensed TermServ - just std version) whereas
I could before. I can terminal serv to another server from this one
unavailable server but cannot connect to it from any other server on the
network, nor remotely from home.

The knowlege base doesn't give any good answers whatsoever.

Connecting via Terminal Services get "The Terminal Server has ended the
connection"

Trying with Remote Desktop I get "The connection was ended because of a
network error"

All TCP/IP is correct, DNS is correct, and all network connectivity with
applications, etc. are all just fine. Everything works and has worked
without issues with the exception of simply trying to TermServ to this
particular server in question.

I had this problem long ago and fixed it but cannot for the life of me
recall what I did nor did I document it (shame on me I know!!!)

Any help would be appreciated.


 
Reply With Quote
 
 
 
 
Vera Noest [MVP]
Guest
Posts: n/a
 
      15th Sep 2005
Is there anything in the EventLog on the Terminal Server?
Is the server listening on port 3389? Check with netstat -an
Can you telnet to port 3389?

Which OS is the server running? And which ServicePack?
What do you mean with "not running licensed TermServ - just
std version"? Is the server running in Remote Administration mode
or Application Server mode (if W2K)?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"=?Utf-8?B?VFRpbWU=?=" <(E-Mail Removed)> wrote on
13 sep 2005 in microsoft.public.win2000.termserv.apps:

> For some reason simple RDP or Terminal Services will not connect
> to one particular server (not running licensed TermServ - just
> std version) whereas I could before. I can terminal serv to
> another server from this one unavailable server but cannot
> connect to it from any other server on the network, nor remotely
> from home.
>
> The knowlege base doesn't give any good answers whatsoever.
>
> Connecting via Terminal Services get "The Terminal Server has
> ended the connection"
>
> Trying with Remote Desktop I get "The connection was ended
> because of a network error"
>
> All TCP/IP is correct, DNS is correct, and all network
> connectivity with applications, etc. are all just fine.
> Everything works and has worked without issues with the
> exception of simply trying to TermServ to this particular server
> in question.
>
> I had this problem long ago and fixed it but cannot for the life
> of me recall what I did nor did I document it (shame on me I
> know!!!)
>
> Any help would be appreciated.

 
Reply With Quote
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't connect via RDP or TermServ =?Utf-8?B?VFRpbWU=?= Microsoft Windows 2000 Terminal Server Clients 1 24th Sep 2005 08:54 AM
Can't connect via TermServ nor RDP =?Utf-8?B?VFRpbWU=?= Microsoft Windows 2000 Networking 4 14th Sep 2005 09:56 PM
can i use termserv to connect an internal pc from home? ken Microsoft Windows 2000 Terminal Server Applications 2 31st Mar 2004 04:32 AM
Termserv.exe Won't Run RF Microsoft Windows 2000 Terminal Server Clients 1 12th Dec 2003 08:25 PM
TermServ 2003 CAL Jocab Microsoft Windows 2000 Terminal Server Applications 1 14th Nov 2003 07:18 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 11:05 AM.