Cannot Connect via Remote Desktop for Server w/ Multipe IP's

[Guest Elroyskimms]

In the course of typing this cry for help, I was able to resolve the

issue. However I stumbled on the solution accidentally and couldn't

find much help online. So, for future generations, in case someone

else experiences this same issue, here is the solution.

 

Problem:

Server 2003 (x64) w/ multiple IP addresses on one NIC:

192.168.1.2

192.168.1.117

....

192.168.1.125

 

Remote Desktop, although configured correctly, did not respond to

connection attemps at 192.168.1.117. The gateway router was directing

the traffic for RDP to that IP address.

 

The 192.168.1.2 address was leftover from an old configuration which I

had forgotten about.

 

What was happening is that the server was listening for RDP

connections ONLY on 192.168.1.2 (the TOP IP address in the list of

IP's assigned to the NIC). By removing that IP, 117 was moved to the

top and the server responded as expected.

 

The moral of the story... you can only use Remote Desktop to connect

to the FIRST IP address assigned to a NIC. There may be a way around

this but I didn't find it. Lucky for me, the top IP wasn't being used

by anything useful so removing it was easy.

 

-E

[Guest Soo Kuan Teo [MSFT]]

Re: Cannot Connect via Remote Desktop for Server w/ Multipe IP's

 

If you try to ping or tracert your server, i.e. ping ServerName or tracert

ServerName, what ip address do you get?

To set which network adapter to use for which RDP-Tcp connections (note: if

your machine has multiple nics, you can have multiple rdp-tcp connections),

goto:

Terminal Services Configurations (tscc.msc)->RDP-Tcp->Network Adapter.

 

Thanks

Soo Kuan

 

 

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"Elroyskimms" <elroyskimms@yahoo.com> wrote in message

news:4832d80e-4756-488f-a060-7ea1e7174e55@e4g2000hsg.googlegroups.com...

> In the course of typing this cry for help, I was able to resolve the

> issue. However I stumbled on the solution accidentally and couldn't

> find much help online. So, for future generations, in case someone

> else experiences this same issue, here is the solution.

>

> Problem:

> Server 2003 (x64) w/ multiple IP addresses on one NIC:

> 192.168.1.2

> 192.168.1.117

> ...

> 192.168.1.125

>

> Remote Desktop, although configured correctly, did not respond to

> connection attemps at 192.168.1.117. The gateway router was directing

> the traffic for RDP to that IP address.

>

> The 192.168.1.2 address was leftover from an old configuration which I

> had forgotten about.

>

> What was happening is that the server was listening for RDP

> connections ONLY on 192.168.1.2 (the TOP IP address in the list of

> IP's assigned to the NIC). By removing that IP, 117 was moved to the

> top and the server responded as expected.

>

> The moral of the story... you can only use Remote Desktop to connect

> to the FIRST IP address assigned to a NIC. There may be a way around

> this but I didn't find it. Lucky for me, the top IP wasn't being used

> by anything useful so removing it was easy.

>

> -E