Terminal Services cannot connect

[jmhcs]

I am working with a small network that uses Terminal services. Been running well for aboput 6 months. This morning start getting the message "The client cannot connect to the Terminal Server, the server may be too busy. Try later" . There is lilltle running on the server.

I have trie3d the Microsoft knowledge base but to no avail. Please help if you can.

[BipolarBill]

http://support.microsoft.com/?kbid=258021

[jmhcs]

Went there, checked everything and it looks good. Did noy get into licensing as this was O.K. before. Can this be corrupted??
Obviously could have missed something.

All network connections are good. Can ping varios computers on the network.

[r8500]

Is this a local server?
can you ping the server?
have you tried rebooting the server?
is terminal services running on the server, or is the service maybe not starting correctly

[jmhcs]

It is a local server and I can ping it from a client. I have rebooted the server many times and Terminal Services seems to be starting, albiet there may be errors, maninly a W32Time error.

[r8500]

w32 time is not a related error.

What other errors are showing up in the event viewer.

[r8500]

What happens if you try to establish a terminal sessions, from the server. Go to the server, and try to terminal to itself, and see what it does.

Also, are you entering the server name in the terminal services connection app., or its IP address?

[omendata]

Have you rebooted the server - there may be too many dead connections?

Have you applied the rpc patch for msblaster - it has already caused me problems with Exchange5.5 intersite f$%£ replication - bloody microsoft.

[jmhcs]

Just got back on task. Been in the hospital and could only work so long. If I take the Internet out of the picture, Terminal Services works well. When I introduce the Internet, the Internet works but not Terminal Services. MsBlast fix has been applied. Are there other worms that could cause this.

[r8500]

has something changed in your firewall or proxy settings, that caused the terminal services port to close?

[jmhcs]

Let is said again I am not a network expert and that is part of the problem. I have disabled DHCP, made a new connection at the client computer using client manager and referencing the IP address of the server and that worked. It worked for all computers so for now I am up and running.

I do not know what caused the problem but obviously, my lack of networking knowledge is the limiting factor here. Do you know of an understandable manual the explains networking in an understandable fashion??? I could go to school but I do little networking and it is a use it or lose it skill.

[BipolarBill]

Networking doesn't come in bite-sized pieces, unfortunately. Either you know most of it or you know none of it - especially when Windows networking is involved.

The only course worth taking is a full MS course.

[omendata]

Yep unfortunately thats true.
Each little piece of networking knowledge always seems to depend on having another piece of knowledge about another bit.

Sort of like knowing IP without knowing TCP.
TCP and IP go together like peaches and cream!!!

Get to know your OSI model and what each level does - its essential to get the basics done first.

[jmhcs]

The network previously mentioned is now working better than ever. Unfortunately, I will continue to struggle with networking, not that I would not put out the $ for a full course but rather that after learning, I will not use it often enough and will lose it. I don't have enough $ to waste because of forgetfulness. Notes only go so far. Sort of a gray (white) hair syndrom.

Thanks for your advice.