Solved

Remote Desktop won't connect on second IP address

Posted on 2009-07-08
4
897 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

The HP utility "HP Lights-Out Online Configuration Utility for Windows Server 2003/2008" could be of great use when it comes to remotely configure a HP servers ILO WITHOUT rebooting the server. We would only need to create and run scripts using thi…
Many of us need to configure DHCP server(s) in their environment. We can do that simply via DHCP console on server or using MMC snap-in on each computer with Administrative Tools installed in a network. But what if we have to configure many DHCP ser…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

751 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