Terminal Services Client 6.0 Not Able to Connect

[rignes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry for the cross post but this may be relevant here too. I've posted this to
the Server 2003 group:

I've just done an update to the Terminal Services Client 6.0 via WSUS and RDP
has stopped working. The install ran fine aka w/o errors as far as I can tell.
However, when I try to connect to any machine using either its NetBIOS name,
FQDN, or IP Address I get the following error immediately after I click
connect:

"This computer can't connect to the remote computer. The problem might be due
to low virtual memory on your computer. Close your other programs, and then
try connecting again. If the problem continues, contact your network
administrator or technical support."

I have 1.5GB of RAM and only have about 650MB committed so it's not virtual
memory.

I'm glad I didn't deploy this company wide and instead chose to test it out
first.

Anyone else running into this and if so what have you found towards a solution?

Thanks,

Brian


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFeaWuohDvlOzv16wRAseAAJ9EamQh6yDXPauhf3RtUNG3aV40JACdGXci
zwvd0xhBOpvGpkkOTPRHW5A=
=dkjO
-----END PGP SIGNATURE-----

 

[KandLClark]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry for the cross post but this may be relevant here too. I've posted this to
the Server 2003 group:

I've just done an update to the Terminal Services Client 6.0 via WSUS and RDP
has stopped working. The install ran fine aka w/o errors as far as I can tell.
However, when I try to connect to any machine using either its NetBIOS name,
FQDN, or IP Address I get the following error immediately after I click
connect:

"This computer can't connect to the remote computer. The problem might be due
to low virtual memory on your computer. Close your other programs, and then
try connecting again. If the problem continues, contact your network
administrator or technical support."

I have 1.5GB of RAM and only have about 650MB committed so it's not virtual
memory.

I'm glad I didn't deploy this company wide and instead chose to test it out
first.

Anyone else running into this and if so what have you found towards a solution?

Thanks,

Brian


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFeaWuohDvlOzv16wRAseAAJ9EamQh6yDXPauhf3RtUNG3aV40JACdGXci
zwvd0xhBOpvGpkkOTPRHW5A=
=dkjO
-----END PGP SIGNATURE-----

We are having the same issue on several different machines. Have yet
to find a solution or anything that they may have in common. All are
XPSP2 Clients.

 

[APHicks]

We are having this exact issue as well on our XP-SP2 clients. Works
fine on some of our clients and doesn't work on others. We cannot find
anything different about the computers that it does and does not work
on. One thing I would like to add is that it doesn't matter if you
enter a valid computer name or not, you still get prompted for
credentials and still get the virtual memory error. If you go into the
C:\WINDOWS\$NtUninstallKB925876$ folder, the old mstsc.exe v5.1 is
still there and still works even though the mstsc.exe v6.0 does not.
Hope that helps someone out there. I will be interested in seeing what
is causing this issue.

 

[KandLClark]

We have discovered that deleting the NTUSER.dat file from the local
cached profile will stop this error and allow you to connect.

 

[APHicks]

How ironic, we discovered the same thing today. First we deleted their
cached profile, had them login and it worked. Then we went broke it
down to the ntuser.dat file, just deleting that and allow it to
re-create works. Still confusing how some of our admins never had any
issue and some did.