adamf Posted November 28, 2007 Posted November 28, 2007 We have a strange problem here where sometimes remote desktop to our fileserver just stops working. When you try and log on you get prompted for the username/password then a connection is attempted but is not sucessful. There are no error messages displayed, it simply just doesn't connect. The solution we've found is to turn off and turn back on Remote Desktop, but i'd like to establish the cause if possible. The server is running Windows Server 2003 Standard R2 with SP2. Has anybody else experience this? Cheers Adam.
PEO Posted November 28, 2007 Posted November 28, 2007 maximum remote desktop connections is 2, sounds like a time out issue. has all the remote patches been applied to the server? If sessions have been disconnected with-out being logged off, the server may consider its concurrent connection limit reached even though there are not two human users connected at the time. An administrator might, for example, close a remote session without logging off. If two more administrators attempt to connect to the server, only one will be allowed to connect before the limit of two concurrent connections is reached.
maniac Posted November 28, 2007 Posted November 28, 2007 Try connecting as the console user (in fact this is the only way you should connect to administer a server!) Type 'mstsc /console' in the run box then connect as normal. This logs you in as session 0, which behaves as if you were actually sitting at the machine. Mike.
apeo Posted November 28, 2007 Posted November 28, 2007 Cant say i have had this problem. The only time i get this is when theres a network issue or the target computer is shutdown or computer name is wrong. Does the file server have anything logged in the Eventlogs? EDIT: @MrHappy: Doesnt it popup with a message saying you have too many terminal sessions.
PEO Posted November 28, 2007 Posted November 28, 2007 Yep DNS, IP, computer turned off etc can send things ass over tit. I updated my grandads server using remote assistance, went to do a restart and i clicked shut down by mistake. couldnt reconect lol
charliecooper Posted October 29, 2008 Posted October 29, 2008 I have had this problem recently. All I had to do is update the video drivers and everything was fine.
gshaikh Posted October 29, 2008 Posted October 29, 2008 a few times but i restart my laptop and after that is fine, no problem at all..
theriver Posted October 29, 2008 Posted October 29, 2008 Cant say i have had this problem. The only time i get this is when theres a network issue or the target computer is shutdown or computer name is wrong. Does the file server have anything logged in the Eventlogs? EDIT: @MrHappy: Doesnt it popup with a message saying you have too many terminal sessions. Yes. Logging on via /console switch is your get out of jail free card in this instance.
dtakias Posted October 30, 2008 Posted October 30, 2008 Also in case anyone is not aware of, to check what sessions are established to the Server use the commands "query session" or "qwinsta" and to reset them, use "reset session" or "rwinsta"
ScottLogan Posted January 31, 2012 Posted January 31, 2012 have you got firewall gpo's on the server. turning rdp off and on again ativates the firewall settings. then if another gpo overwrites it it can all of a sudden stop working.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now