Solved

Remote Desktop won't connect on second IP address

Posted on 2009-07-08
4
885 Views
Last Modified: 2012-05-07
Have a second IP address on NIC card that we use for a specific application on the server.  After a server reboot, we can still RDP into the first IP address, but the second one no longer works.  Have tried  <telnet IP Address 3389> and get no connection.  The error message says "This computer can't connect to the remote computer."  Can ping the second IP address with no problem.  Running <netstat -an> shows the first ip address listening to RDP port 3389, but not the second one.  Is there a way to get the second ip address working with RDP again?
0
Comment
Question by:rstorm1
  • 2
  • 2
4 Comments
 
LVL 6

Expert Comment

by:ahmad2121
ID: 24810532
its a mistake in the first place that RDP is only listening on that one IP.

did you restart the computer after you added that IP?

or you could disable remote desktop and enable it again (computer > properties > remote)
0
 
LVL 4

Author Comment

by:rstorm1
ID: 24810648
I have tried both restarting and disabling/re-enabling remote desktop with no effect.
0
 
LVL 6

Accepted Solution

by:
ahmad2121 earned 500 total points
ID: 24810699
ok something changed your connection then.

go to Administrative Tools > Terminal Services Configuration > Connections > Right click on the connection > Properties > Network adapters > All network adapters

If that doesn't work, delete it and create a new one.
0
 
LVL 4

Author Comment

by:rstorm1
ID: 24813426
There were actually 2 connections in the Connections window.  Had to delete them both and recreate the RDP-TCP connection.  I deleted them both, rebooted the server, then recreated the connection and rebooted again.  That seems to have it back up and working.  Thanks for your help!
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

821 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