Windows Xp Rdp

admin



  1. Using Remote Desktop With Windows XP Professional
  2. Windows Xp Rdp To Windows 10
  3. Windows Xp Rdp Not Working
  4. Windows Xp Rdp Exploit
  5. See More Results

Sep 26, 2006 Non-Windows XP systems can also access Windows systems running Windows Remote Desktop. The local system used to access the remote computer must have the remote connectivity client software installed. Non-Windows XP systems can also access Windows systems running Windows Remote Desktop. The local system used to access the remote computer must have the remote connectivity client software installed. Many XP users have been blaming Service Pack 3 for breaking remote desktop connections to their machines. I, for one, have been unable to RDC into my Windows XP machine since the upgrade to Service Pack 3 as well. However, the issue isn’t with Service Pack 3 at all! Nvidia is at fault!

There are multiple methods of connecting to a virtual machine in VMware. You could do it manually, through the VMware Workstation program, or install TeamViewer, LogMeIn, or any other remote access software. If you just need access within a local network, and you don’t want to access the host machine every time, it’s really easy to enable standard remote desktop connections.

Enabling remote desktop connections in VMware is done both regularly, through the operating system, and within the VMware network settings. We must set up port forwarding in VMware so the program knows what to do when we request access via remote desktop.

Configure VMware for RDP (Remote Desktop) Connections

VMware first needs to be configured to forward RDP requests to the IP address the virtual machine is using.

Step 1: Launch the menu item VM > Settings.

From the Hardware tab, select Network Adapter and choose NAT as the connection type.

Step 2: Search the start menu for command prompt from within the virtual machine. Enter ipconfig in the prompt and search for a value following the IPv4 Address. Record this address for later use. Ours is 192.168.163.133.

Step 3: Now select the menu item Edit > Virtual Network Editor.

Select the NAT network type and then choose NAT Settings.

Step 4: From this new prompt, click Add to include a new port forwarder.

Enter the following information:

Host Port:9997

The Host Port number is simply an open port number. If you’re unsure what number to use, select the one we have here.

Type: TCP

Windows Xp Rdp

Using Remote Desktop With Windows XP Professional

Virtual machine IP address:Enter the IP you recorded in Step 2.

Virtual machine port:3389

This port number is 3389 by default, but can be changed via a registry edit. If you’re unaware of any changes, select the one we have here.

Save any open prompts so the configuration changes can take place.

Step 5: The final step is to enable RDP connections from within the operating system itself.

Windows Xp Rdp To Windows 10

In Windows 8.1, search for Who can use remote from the start menu to narrow down the results.

For Windows 7, search for Remote Desktop from the start menu and choose Select users who can use remote desktop.

For Windows XP, right-click My Computer from the start menu and navigate to the Remote settings.

Choose to Allow remote connections to this computer for any of these operating systems.

Connect To the Virtual Machine With RDP

Connecting to the VM is the same as with any other computer. Open Mstsc from the start menu and type the IP address or computer name and press Connect.

Enter the regular login details to connect, like so:

Conclusion

Windows Xp Rdp Not Working

It’s much easier to connect to a computer of any kind, be in virtual or not, using Windows Remote Desktop. The screen isn’t bogged down by extra menu settings and you can maximize the window and use the machine as if it’s literally in front of you.


The above article may contain affiliate links which help support Guiding Tech. However, it does not affect our editorial integrity. The content remains unbiased and authentic.

Read Next

7 Best Ways to Fix Kindle for PC Desktop App Won't Open on Windows

Can't open the Amazon

With the advent of Windows Vista, Windows 7, and Windows 2008, the Microsoft RDP client was updated to support NLA, or Network Level Authentication. Seen below, the selected option allows for the most secure RDP experience.
The downside of this is that if you run older clients, specifically, Windows XP - the newest RDP client doesn't support NLA, so you receive this error when attempting to connect.
The common workaround for this is to choose the less secure option of allowing connections from computers running any version of Remote Desktop. While this may be fine for some organizations, it might not be as well. I wanted a better work around since it would mean I needed to ask a customer to change this setting. I searched and found this AWESOME workaround here.


On the Windows XP workstation you use to RDP into the server/workstation:

  1. Click Start, click Run, type regedit, and then press ENTER.
  2. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa
  3. In the details pane, right-click Security Packages, and then click Modify.
  4. In the Value data box, add tspkg on a new line. Leave any existing data that is specific to other SSPs, and then click OK.
  5. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProviders
  6. In the details pane, right-click SecurityProviders, and then click Modify.
  7. In the Value data box, add an additional comma, a space, and then credssp.dll - leave any data that is specific to other SSPs, and then click OK.
  8. Exit Registry Editor.
  9. Restart the computer

After rebooting, you will be able to RDP to newer OS's with the more secure NLA SSP.

Windows Xp Rdp Exploit


From Simon G - here is a VBS script to do this in case you need to do it en masse.

See More Results


const HKEY_LOCAL_MACHINE = &H80000002
lsaKey = 'SYSTEMCurrentControlSetControlLsa'
lsaValue = 'Security Packages'
hostname = '.'
Set regObj = GetObject( 'winmgmts:{impersonationLevel=impersonate}!' & hostname & 'rootdefault:StdRegProv' )
regObj.GetMultiStringValue HKEY_LOCAL_MACHINE, lsaKey, lsaValue, stringValues
size = Ubound( stringValues ) + 1
ReDim Preserve stringValues( size )
stringValues( size ) = 'tspkg'
regObj.SetMultiStringValue HKEY_LOCAL_MACHINE, lsaKey, lsaValue, stringValues
secProvKey = 'SYSTEMCurrentControlSetControlSecurityProviders'
secProvValue = 'SecurityProviders'
regObj.GetStringValue HKEY_LOCAL_MACHINE, secProvKey, secProvValue, theValue
theValue = theValue & ', credssp.dll'
regObj.SetStringValue HKEY_LOCAL_MACHINE, secProvKey, secProvValue, theValue