Terminal Server and RDP connection error

I can connect to my Terminal Server (Windows 2003 R2 SP2), licensed with 20 user CALs internally no problem with multiple user names.

I have a client that connects remotely with 3 Windows XP Pro computers using a Cisco VPN clinet connection.  The client connects no problem and can ping by name and IP address.

From 1 XP computer the RDP connection works and connects without a problem.
Log this session off and disconnect the VPN connection and move to the 2nd XP computer.
VPN client connects and can ping by name and IP address.  Try to connect to the terminal Server and the following error happens.

The client could not connect to the remote computer.

Remote connections might not be enabled or the computer might be too busy to accept new connections.  It is also possible that network problems are preventing your connection.

Any help possible is appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

So just to verify, from the computer getting the error can you ping the terminal server IP and host name?

Can you try connection to the terminal server by IP address?

Does nslookup on the problem computer resolve the terminal server hostname to the correct IP address?
agencycoopAuthor Commented:
Yes I can ping by IP and hostname.

I've tried RDP by IP and still get the same error.

I'll need to be at the clients to test the nslookup and will report back.

Also, make sure that your access list are not stopping the one machine.
Cláudio RodriguesFounder and CEOCommented:
Another thing to consider is tweaking the MTU size on the TS end. Very common tweak required when people are coming through VPN connections.
The thing is sometimes it is needed, sometimes you do not need to do anything. It is really a trial and error thing.
Look for MTU.

Claudio Rodrigues

Microsoft MVP
Windows Server - Terminal Services
agencycoopAuthor Commented:
Thanks to everyone but the problem was with the tunneling of the VPN client software.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.