I have set up a win2000 server box and a windows xp box and I use terminal services to use the win2000 server. well my problem is i lost connection with my terminal and it has happened a few times and when i try to reconnect it doesnt let me. is this because the port thinks im still connected? or what...so what can i do? is it my computer or the other computer or what? now the reason i dont just simply get up and re-set both pc's is bcuz i run a huge network and i use this to get things done. so if anyone can help that would be great...
thx ahead of time
(Gh0stSheLL's Friend)

Could anything have interferred with Terminal Services? Are you running any programs on Windows 2000 server that may conflict? I don't know of any, but this may be an issue.

Is is hard to manually reset Terminal Services on the server box? I'm not sure what would be causing this loss of connection. Are your network cables in alright condition?

As for reconnecting, it depends on the error message. It may think you're still connected, but we'd need more information to discern this.

everything should be hooked up properly...
not sure of any services that could be messing it up port 3389.
and the error i get just says connection lost. It only happens like when i minimise it for a sec to go do something. I could only think that maybe its timing out. I think most likely it thinks I am still connected. Is there a way to send a keep alive signal like when you are on ftp. Is there a different remote desktop client that is better built? I could only think it is timing out on my side or something and stying up on the other side. If my session on the other side is still running could this keep me out?

heres the error i get after i loose my connection with it and try to connect...
the only possible thing i can think of in that error that could be true is the busy part...

If it maintains a previous session, and doesn't know to drop it when you try connecting again from the same IP, then yes, it wouldn't allow you back on.

You could try other remote connection software, such as Remote Administrator or PCAnywhere.

Hmm, looking at your screen, it mentions that it is busy. From what you've said, that most likely means it is hanging on your previous connection.

as said, it would appear that your connection is timeing out, and then the win2k box is not dropping that session so it becomes "full". to stop this, just set up remotedesktop to accept connections from your ip to kick anyother connection from that ip, its in the server settings somewhere.

I am going to try what buzzons has said will tell ya how it goes
I will set up some more remote connection software. Thx for the replys if anyone else has had this prob and would like to comment please do so bcuz I am open to any solution .

I have also found this http://www.microsoft.com/technet/prodtechn...fcb4d1c55b.mspx

I dont remember the exact error but this is close...

The remote connection has timed out. Please try connecting to the remote computer again.

Cause: The terminal server disconnected your session because you did not send a response within the time limit set for responses.

Solution: Try connecting to the terminal server again. If you receive this error message, try to reconnect at a later time. If you continue to receive this error message, contact the server administrator.

Cause: A slow network connection, caused by excessive network traffic, has delayed your response to the terminal server.

Solution: Try connecting to the terminal server again. If you receive this error message, try to reconnect at a later time. If you continue to receive this error message, contact the server administrator.



hmmm the only prob is that i dont wanna have to wait a couple of days to log back on lol. I would think maybe this is happening bcuz i run this network and I am on vacation so I am away from it and it is really really far away. The connection to it is slow yes but I didnt think that matters but I guess that could cause a time out...
Well any help would be fine. I thought it would be better if you could get an idea of my errors.

hmm another question...
if it is hanging on my last session and i did a port scan would it be open?
I just did a scan and it shows the port to be closed. Usually by now i would have contacted someone to reset the server but in this case i am leaving the problem there to see if i can resolve it. hmm anyone else here ever got disconnected from there session and couldnt connect back?

I think this is the error i get when i loose the connection.

well it happened to me only 2 times.
I have came up with the idea to enable telnet and use it to kill the terminal service (since you cannot stop the service).
just kill the instance of svchost that owns port 3389 and restart the terminal service afterwards.
you should be able to logon to you session again and noone needs to reset the server for you.
or use radmin it does not have this kind of problems and offers both remote desktop and telnet and is sometimes faster on slow connections if you chose the right settings.

cool so all i have to do for right now is wait for the computer to restart? well ok atleast i know it isnt something else now aight well i will wait to do this and see what happens thx for all the replys guys.

hmm check this out this might tell you what the problem is i dont know...ok i tried to connect and i got an error saying something abou the license...then i tried again and it brought up a black screen like it was trying to load then it disconnect...then i tried it again and it gave me this error(i attached picture...and then tried again and it goes back to the old error from the posts above...any help would be fine...

[EDIT]
problem seems to be fixed now the server was re-set and it has no probs now
[/EDIT]