Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Ok, I am running a domain off of Small Business Server 2003. I am trying to connect to the server via RDP but I get the message
"Remote Desktop Disconnected:The client could not connect to the remote computer..."
Now, in system/advanced/remote, allow remote connections is checked. Terminal services is running in remote administration mode (by default), any remote desktop permissions in GPO are modified for allow. I can ping the server (1.100) and can use remote desktop FROM the server, my user name is in remote admins group(although it doesnt matter- I cant even get to a point where authentication takes place), firewall is off, server has connectivity, client has connectivity, every single post I have read here or on M$ I have attempted to no avail. Someone help! Thank you in advance.
Make sure your account has a complex password set. :-)
Also, if you are trying to RDP to the server over the net through a firewall/router, make sure port 3389 is forwarded to the server.
"...but in my defense, it was dark, I was drunk, and it was delicious!"
0 
As an update, I am on the lan, connected by a switch to the server. I have password complexity requirements truned off, although as a rule I always have a password that will meet those requirements. No software firewalls are on either machines, although the same result happens from many clients, not just one, and the server in question can RDP to all clients involved. Thanks.
0
do you have the SBS Remote Operaters added in the "select remote users" in System Properties/ Remote? Might want to add your username in there for access even if you do have that added...
yup!
0
Make sure the username is a member of the Admin group. You must use a password to connect with RDP. So...ensure the username is part of the Admin group and has a password.
0
Yes, my user is in the Remote Operators group. And if Mike had read any of the posts, he would see that there is indeed a password set. I failed to mention that I was in the admin group only because that is the first thing one would check. It goes without saying that if I installed and set up the server, and am now trying to administer it REMOTELY that I would be an administrator....
0
yes, but is the remote operators group added "select remote users" windows?? and have you tried adding your user that you are trying to log in with in that "select remote users" i know you have the username added to remote operators but for giggles i would add the user direct to select "remote users" and see what happens
yup!
0
Type "mstsc /console" in the run line, then try to remote into your server. This is different than the normal RDP.
I get this message on one of my 2003 servers, but not my 2000 servers. All indications point to an expired terminal services license. We do not have a terminal license server, so I expect this message and use the command listed above for access. If you have a terminal license server, check to make sure the license has not expired for this server. There is a way to change the type of terminal server license from PC to user, (or something like that, it's early here), so check that also. The temporary license only lasts around 90 to 120 days. You can remote out from the server, but not into it. And yes I saw that in your earlier posts...
BTW, I did read the earlier posts, and by your response about me, it sounds like you get out of the server room much...Don't take these responses so personal...
0
CRAP. I told you it was early here...
I meant to say you sound like you "DON'T" get out of the server room much...
Hope the above suggestion helps...
0
Yes, my name is in the user selection window for remote users. Mike, the expired terminal servers licensing issue takes place when you install terminal services licening server, and you have a 120 period before which you have to buy licenses, after that is when you have to cennect to the console session using the commmand line interface, ie mstsc -v:server -console. That is not the issue here. And I responded in such because the answer was there yet you chose to ignore it. Not working smarter, working harder. I prefer NOT to be in the server room, espicially when I go to a professional forum where someone tells me not to take the posts personally, yet that same person takes my replies personally. If there is someone who is experienced with RDP, by all means, reply. If you are guessing, save us all some time and refrain from posting. If you will look at the characteristics of the problem, user rights/passwords are not even an issue. The server is not even getting to a handshake/authentication point in the procedure. It is getting dropped somewhere before terminal services even picks it up...
0
You are right and I was wrong to answer you that way. Sorry.
However, that does not fix your problem...
We use RDP all day long to service servers and user's computers. The "mstsce /console" command I refered you to is the one I'm familiar with, not your version above.
When you post here, you are asking for "guesses" because your earlier post said Microsoft and other posts here didn't help. Normally, I would take your error message to the MS Knowledgebase and search for a fix. But you shut down that option by saying you had already tried them all. The other options are for you to check your security settings for the server and user, or look at your event logs to see what may have happened around the time you could no longer access the server with RDP. Did you install software or hardware around the time it stopped working? If you still can't find the problem, you should start your troubleshooting over from scratch and see if you missed anything. Could be something as simple as a corrupted registry key, especially if the OS is set up properly.
Again, I apologize for my earlier posts, but you need to remember when you post here, a lot will be guesses trying to help you. Otherwise you might be better off paying Microsoft for support. While hard to get through sometimes, I've heard they know their product.
0
Try this website: http://www.mcse.ms/message1159487.html
or this one: http://www.chicagotech.net/rdesktop.htm
or this one: http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/83ddcc90-4409-4063-8bac-f5fcb4d1c55b.mspx
There were many more websites out there about this problem. Just plug your error message into a search engine and see what shows that may apply to your problem.
The first suggested website actually sounded like it was you. Their problem was fixed, so I hope it will help you, too.
0
Problem solved, although the exact cause of the problem is still unknown. I reset all the GPO's and built them back up (not too hard with the new way MS handles gpos with the Group Policy Manager) via the dcgpofix command. I understand what you mean Mike, about the guesses, my point was if you had any experience with a similar problem, not, oh, check the network cable genre of "help". Thank you all.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
