Solved

Windows Server 2003 RDP not connect

Posted on 2011-02-11
11
533 Views
Last Modified: 2012-05-11
I have a Windows Server 2003 Enterprise Edition server as one of my
domain controllers. I have Remote Desktop enabled on it for the domain
admin account. Port 3389 is opne and I also enable the options for RDP. It has two Ip address and i can ping both on server name and the IPs and its showing reply.

But I am not able to connect it from  a XP system which is on different domain. I receive the error

--------------------------------------
Remote Desktop Disconnected

The computer can not connect to the remote computer.

The connections was lost due to a network error. Try connecting again. if the problem continues, contact your network administrator or technical support

--------------------------------------

Is it not possible to connect the server from a XP system which is on a different domain. i do not want to add the XP system on Server's domain.

Please suggest.

Thanks
0
Comment
Question by:technicalsys
  • 5
  • 2
  • 2
  • +2
11 Comments
 
LVL 12

Expert Comment

by:enachemc
ID: 34868886
try to do a telnet to those IPs on port 3389
If it connects, it's not a network problem.
0
 

Author Comment

by:technicalsys
ID: 34868910
Hi enachemc,

When I telnet both the IP from the command prompt it is not showing anything. Only it is showing connecting to Ip and then disappears.

Thanks
0
 
LVL 5

Expert Comment

by:danubian
ID: 34868980
It is unusual to have a multi-homed DC.

Try open Terminal Services Configuration - RDP-TCP Properties - Network adapter tab
Select here the right network adapter, and from client side connect to this enabled IP.
0
 
LVL 8

Expert Comment

by:afthab
ID: 34869661
hi,

1. RDP should be enabled
2. Make sure Firewall disabled on server.
3.Check your TCP/IP settings (* subnet mask)
4. Try to connect through console (mstsc.exe /console)
5.Check event viewer for detaild error


If you need to access any resources from different domain, you should have trust relation to be created between the domains. If you already have trust relation created, then you should get both the domain option (Under logon to) while you are log in to the server.
0
 
LVL 19

Expert Comment

by:PeteJThomas
ID: 34870153
It is absolutely possible to do this. In fact, you don't NEED a trust relationship either, unless you want to be able to RDP on to a server in DomainB using an account in DomainA - We don't do this, we just connect to the 'other domains' using credentials from that domain (so we connect FROM DomainA, to servers in DomainB, by just providing valid credentials from DomainB).

Regardless, it sounds as if you're not even reaching that stage? Have you configured default credentials in the RDP connection, or are you doing this manually, and not even being prompted for credentials before the error appears?

The telnet command you tried was SUCCESSFUL - That is what telnet does when it successfully connects, if it failed it would give you an 'Unable to connect to xxxx on port xx' type error. If it just sits at a blank screen with a flashing cursor, it has connected successfully, so the port IS open.

Pete
0
Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

 

Author Comment

by:technicalsys
ID: 34887436
Hi,

I have done the manual configuration of RDP console. I can still connect to the second server through run command by typing the server's ip address but not able to connect through RDP.

0
 
LVL 5

Expert Comment

by:danubian
ID: 34887491
Any related events on the target server's event viewer ?
0
 

Author Comment

by:technicalsys
ID: 34903565
Hi,
There was no error reported on the event viewer related to RDP.
0
 
LVL 8

Expert Comment

by:afthab
ID: 34903631
I hop you are using proper tcp/ip settings, did u tried my suggestions on above post ?

* did you restarted the server ?
* Enable and disable all tcp/ip and rdp settings, Then try

have a look
http://www.windowsnetworking.com/articles_tutorials/Troubleshooting-Remote-Desktop.html

AtB
0
 

Accepted Solution

by:
technicalsys earned 0 total points
ID: 34948691
Hi,

Resolved the issue by deleting the Certifica key from HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters.

Thanks for your help.
0
 

Author Closing Comment

by:technicalsys
ID: 34986626
Resolve the issue after editing the Registry
0

Featured Post

What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

Join & Write a Comment

I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
Learn about cloud computing and its benefits for small business owners.
This video discusses moving either the default database or any database to a new volume.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now