RDP Connection Failing

D

Dave Imig

After connecting to a win 2000 Term Svr to run a medical
app from a number of clinics via DSL 768/256 (Most of them
connect to various servers through a VPN Tunnel forwarded
to the appropriate server by a Linksys VPN Rtr. I could
also use a direct connection to my wan IP to access a
single TS server which was fine for those people who
needed the app on that server anyway. The problem is that
all of a sudden one day they couldn't connect. (Got the
message you get if you try to connect to a session that
doesn't exist. i.e. too busy, NW issues, etc. The
strange part is that I have 2 locations that access the
same Term Svr for the same purpose & they are still running
fine as always. All client machines are XP Home Edition.
From the bad site I can ping my wan IP, the vpn tunnel is
connected properly & I can ping the Term Server's IP.
Whay won't the RDP Client connect? I've tried 5.0, 5.2,
and the one that Term Svr Client Creator makes, but still
nothing.
The only thing that I can say I've done differently is
that because the site with the problem is closer, I've
been more dilligent about installing the critical
updates. Does anyone think that MS has created a security
patch that could be the cause of my issue?

Help!!!!!!
 
V

Vera Noest [MVP]

Is there anything in the EventLog on the TS when these clients are
rejected? Have you checked your TS licenses?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top