Hi all -

A weird one...

While logged in to the server with the Terminal
Client, an instance of IE crashed and my attempts
to reboot the server resulted in the screen freezing.

Later attempts to login showed the same frozen
screen upon passing the login dialog.

I asked for a reboot (and the company apparantly
have done it) - but attempts to login in using the
Terminal Client gives the following msgs:

First: ---
"The terminal server has exceeded the maximum
number of allowed connections."

And Second --
"The System cannot log you on (1B8E). Please try
again or consult your system admin"

http://www.vietnamartgallery.com/files/errmsg.jpg

Other info - i'm running win2k server (no patches as yet), IIS5, and probably Code Red. :-\

Really need your help on this one.

Murray.

That is strange. I would get VNC installed and then take a look at Terminal Manager to see who is connected, how long and where they are from.

Also, when you get into Terminal Manager configure it so that all sessions timeout after 5 minutes of no activity. That way it will free up sessions if you get locked out.


Let us know what you find.

Hi Mike,

Thanks for your reply!

At this point in time, I have no way of accessing
remote admin on the server at all.... which means
i can't install any software on it.

What would you suggest i do from here?

Also - a question on your colo services... do you
charge to make DNS entries in your tables? i'd
be very tempted to change colo company if i feel
i could get more helpful support from another
organisation.

thanks for your help and best regards!

murray gray

Hello Murray,

At this point in time, I have no way of accessing
remote admin on the server at all.... which means
i can't install any software on it. That's the trouble with remote access software :(

Your colo provider should be able to hook up a monitor & keyboard and install it for you (even if you have to walk them through it).

Here is what I am thinking:

1) You are only given one TS session with W2K for remote administration. Sometimes you will loose your connection to the server and the server still thinks you are connected and will not let you back in. This is why you should always set the idle session time out to something like 5 minutes so when this happens, W2K will reset all sessions. Make sense?

2) A reboot should clear out that session that is stuck. I know this is a silly question, but are you sure your provider did a reboot? If they did an you still get that error there is something wrong with TS.

Try a another reboot and see if that helps. No, we do not charge to make DNS entries (with in reason :) ).

Sorry I cannot be of more help,