Unable to reconnect to 2003 TS session

[David J]

I'd be extremely grateful if anyone could offer me some
advice on the following problem:
I'm running TS in application mode on a single 2003
server. Everything appears to function correctly until a
client loses its connection and the session moves to a
disconnected state. If the user attempts to reconnect,
they get the following error after logging on 'The
connection was ended because of a network error. Please
try connecting to the remote computer again'. All
attempts to reconnect are unsuccessful until the session
is either manually reset, or the time limit for the
session disconnect is reached. Any unsaved work is lost
during the reset. The problem also occurs with auto-
reconnect enabled and for all classes of user. To
minimise the chance of network issues, I've
(unsuccessfully) tried a workstation on the same switch as
the server. Workstations run 2000/XP with the latest TS
Client. No messages are generated in the event logs
(workstation / server / license server) and group policy
settings appear to be correct.
Any pointers would be very much appreciated. Thanks in
advance. David J.

 

[Matthew Harris [MVP]]

Once the user is disconnected, can another user connect
from the same computer, using a different logon account?

-M

 

[David J]

Matthew / Cherry,

Thanks for the replies.

If another user connects from a recently disconnected
computer, they get straight on to the TS. If the user who
disconnected tries on the same or a different computer,
they still don't get access (user issue?). Changing
RestrictAnonymous makes no difference. I've also had no
success removing all group policy settings from the
clients and server.

I'd already tried troubleshooting with TSAC.
Unfortunately, the TSAC pack referenced in the article no
longer exists. You can still download Tswebsetup.exe, but
it's a newer version - after installing, I can find no
trace of Connect.asp, or of the code mentioned in the
article. Then again, I might be looking in the wrong
place.

I monitored the security event logs and found that
attempts to re-logon are successful to the point at which
special privileges are assigned. 'Success' audits then
indicate that winlogon and crss have excited and the whole
process ends.

To make sure the issue isn't caused by a hardware fault or
mistake on my part, I've started a step-by-step rebuild on
a different box. Though I've not got very far, things are
currently working as they should. If it does turn out
that the issue relates to a change I make, then I'll add a
post with the information.

Thanks again for the advice - it was much appreciated.
David J.

 

[Cherry Qian]

Hi David,

Thank you for the posting again. I am glad to hear things are currently
working as they should.

Please keep me updated obout any progress on this issue. If anything is
unclear or if there is anything further we can help you with from our side,
please let me know and we will try our best to assist you.

It was my pleasure working with you on this issue. Thank you for your
understanding and cooperation.

Sincerely,

Cherry Qian
MCSE2000, MCSA2000, MCDBA2000
Microsoft Partner Online Support


Get Secure! - www.microsoft.com/security

====================================================
When responding to posts, please Reply to Group via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided AS IS with no warranties, and confers no rights.