RDP (Terminal Services) on a Windows 2000 stoped working after P2V

[Very_Lost]

Group,

It seems like everytime I P2V a Windows 2000 Server (SP4), Remote desktop (TS) services stop working. I found in the TS Manager states that the port is "down". We were able to use RDP from our XP boxes to admin the server before the convert. Any thoughts?

Just to be clear. This is not a TS Server or some special remote box. It is a standard Windows 2000 Server with SP4 running some applications.

Thanks

[Very_Lost]

WOW.. I must have been more tired than I thought...

That should read "Windows 2000 Server stopped working". Geez

I still have this as an open issue and is really holding up our migrations, so, any assistance would be appricated.

THX

[asatoran]

Have you checked the RDP-TCP Properties, Network Adapters tab in the Terminal Services Configuration Control Panel? When you P2V, the virtual machine will get a new NIC, so perhaps RDP is not listening on the correct NIC anymore.

[Very_Lost]

Yes, I verified that it was set to "All network adapters configured with this protocol", with unlimited connections.

[AndreTheGiant]

Which related error do you have in Event Viewer?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[TomHowarth]

Have you checked the Groups membership for the RDP protocol

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts

[Very_Lost]

I am a domain admin... I granted my account specific permissions and it did not work.

I believe the issue is around the port not being available. I just don't know how to get it to listen.

[cainics]

Try this. Change your NIC from "VMXNET" to "AMD" in the adapter options.

Enable the NIC, provide an IP and make sure the NIC status shows connected in VI client (not on the virtual machine itself).

Let us know of the status afterwards.

Thanks

“Your intelligence is measured by those around you; if you spend your days with idiots you seal your own fate.”

[TomHowarth]

have you removed remote access, rebooted the server and then re activated remote access to the machine?

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts

[Very_Lost]

Yes, I have completely uninstalled Terminal Services from the box, rebooted serveral times. And reinstalled the component.

No Joy!

[Very_Lost]

No related events in the event viewer. The only thing that was in error, was an HP service that I forgot to turn off...

It is off now.

[Very_Lost]

I am not sure what you mean...

Can you clairify?

Thanks

[cainics]

Well.. in the virtual machine console, change the network adapter (in network settings) to AMD. The default adapter that VMWare selects after P2V is VMXNet.

I have run into a funky issue in the past where an application would not work with the network no matter what. The network adapter was functioning properly and everything was ok. Changing to AMD resolved the issue. Do not worry about the adapter speed that is shown (10Mbps). It's just that this adapter used to run in the past at 10Mbps so that speed is listed. Actual throughput is the speed of your blade adapter (which is usually 1 Gbps). This is just a test for you to verify that there is nothing related to the network adapter itself.

Hope this helps.

“Your intelligence is measured by those around you; if you spend your days with idiots you seal your own fate.”

[Very_Lost]

So.. Here is what I know at this point.

1. I have rebooted the box serveral times

2. I have uninstalled, rebooted, installed the TS service again

3. There are no events in the event log either on the client or the server

4. In the Terminal Service Manager, it states that the RDP-TCP (65537) is down

5. The Terminal Service Process is started and running in automatic

6. VMWare tools are installed and up-to-date

7. The client gets the "This computer can't connect to the reomte computer" error message

8. Clents were able to RDP from their XP boxes to this Windows 2000 SP4 server prior to the P2V

9. I have removed it from the domain and re-added it to the domain

I think that about covers it.

Thanks to all in helping to resolve this issue

[Very_Lost]

Oh.. I guess I forgot to say.. I have been bitten by network cards or hidden interfaces during previous migrations. I, now, remove the network card from the P2V process. I then re-add it manually to the image after everything is complete. I put in all of the IPs, etc... after the convert.

Currently the image is set to Flexible and is connected / connect at power on.

The VM is using "VMWare Accelerated AMD PCNet Adapter"

I do not see an option to change from one adapter to another.. We are using ESX 3.5 Update 4.

Thanks

[TomHowarth]

Just a thought, have you verified that there are no shadows NICs by checking for hidden devices in Device Manager? if there are remove them

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts

[drose0]

I had this same problem last night and eventually found the fix with some random googling. Look at this fix on Microsoft, it worked for me but your scenario could be different.

http://support.microsoft.com/kb/270588