• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1522
  • Last Modified:

RDC Windows 7 to Server2003 - 'Your Computer could not connect to another console session on the remote computer because you already have a console session in progress.'


Getting this error when i try to connect to a server today.

Your Computer could not connect to another console session on the remote computer because you already have a console session in progress.

When i try logon to the server via UNC Path i get the following error.
Logon Failure: The target account name is incorrect

I have checked the following things

I have ensure not remote sessions are open on the remote PC.
I do have permission.
I can RDP to the server from another other machine.
I have restarted the server.
I have restarted my machine.
I have tried it in Safe Mode with Networking.
I have changed my PC name.
I have changed my IP.
I have cleared the Hosts File.
I have turned off all the file walls.
I have cleared the cache information in regedit todo with remote desktop.

So i am currently stuck RDPing onto the mainserver then RDPing onto this server.
Right pain, and i can run one of the Apps that sits on this server from my PC also.

Any ideas would be very very helpful.
Kind Regards
  • 5
  • 4
2 Solutions
Are you connecting to server with IP address or with name? Have you tried both methods? Have you any errors on server side?
MPJHornerAuthor Commented:
Yeh, have tried both methods. Both give me the same problem.
Its a server so the IP wouldn't change, but to answer you question, tried both and DNS working.
What about any errors on server side?
Are both computers (server and workstation in one domain)? Are you logged into workstation with domain account (It should not be concerned with RDP, but with access to UNC path)?
Can you remove workstation from domain and rejoin it?
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

MPJHornerAuthor Commented:
Have removed and re joined to domain.
Have tried loggin in this pc as another user and it doesnt work.
no obvious errors appear on server.
I can logon as myself on a different PC on the domain and it works.
All under the same domain, simple domain no subdomains etc
If you are not using IP v6 in your network - disable it.

Last idea - try to reset winsock and IP:
netsh winsock reset
netsh int ip reset c:\resetlog.txt

If it also will not work, try to change (add) LAN adapter and cable (may be it should be first point).
MPJHornerAuthor Commented:
Fantasic, that worked a treat.

*running those two cmds from cmd prompt.

What exactly do they do, then Accepted coming your way!
These commands repair errors in TCP/IP protocol and Winsock. Usually after virus attack (written by low qualification programmers, when incorrect modifications are made in registry). Usual behaviour - you can't access other computers at all. In your case there were something more complicated.
MPJHornerAuthor Commented:
Great thanks for the all the help - was seriously considering reinstalling the OS!
You are welcome

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now