Added a second ip to the external (wan) NIC to publish a Terminal Server.

Works great....... until the server is rebooted. Then an internal Remote Desktop connection to the server fails.

Running EICW shows garbage in the NIC selection windows.

 

Now every time I reboot the server I must:

 

    Remove the second IP from the WAN NIC

    Run EICW

    Add the second IP

 

There may not be a solution to this apart from this work around. 

(If nothing else, I can search for this if I ever forget)

 

    Tom

I have the same configuration and if the server is rebooted remotely, then there is no way to get back in.

 

Consequently, whenever I need to reboot the server, i manually remove the second IP first, then reboot, then add it back in again manually.  This allows you to keep the remote connection and you don't need to rerun the wizard.  Still kind of a pain, particularly if you forget to remove the second IP before rebooting.

 

If anyone has another way to publish a TS without the second IP on the WAN nic, that would be a great time and trouble saver.

 

Steve

It's easier for users to have an icon that they click on and rdp directly to the TS in two seconds.  Harder for the admin, but easier for the user.

 

Steve