Chris Pohlad-Thomas
December 27th 03, 11:23 AM
I am trying to connect to a Windows 2000 server machine running Terminal
Services with Remote Desktop Connection. Everytime I try to connect I get
the message saying that it cannot connect to the remote computer for those 3
reasons. I checked to make sure we weren't maxed out on users getting in,
and that's fine. I could connect to the Terminal Server from another
machine in house running Terminal Services on Win2k. I can't connect to it
using Terminal Services on my machine either. A couple interesting things.
I set up a totally new Terminal Server just to make sure it wasn't the
server that we had already had setup and the first time I connected to it,
it connected just fine. Every subsequent time i received the error message
discussed above. Is there some kind of file that is dumped somewhere when
you are successful connecting to a server? The server is running
Application Server mode and I can connect to every other computer we have
running terminal services but they are running in Remote Admin mode.
Thanks in advance,
Chris
Services with Remote Desktop Connection. Everytime I try to connect I get
the message saying that it cannot connect to the remote computer for those 3
reasons. I checked to make sure we weren't maxed out on users getting in,
and that's fine. I could connect to the Terminal Server from another
machine in house running Terminal Services on Win2k. I can't connect to it
using Terminal Services on my machine either. A couple interesting things.
I set up a totally new Terminal Server just to make sure it wasn't the
server that we had already had setup and the first time I connected to it,
it connected just fine. Every subsequent time i received the error message
discussed above. Is there some kind of file that is dumped somewhere when
you are successful connecting to a server? The server is running
Application Server mode and I can connect to every other computer we have
running terminal services but they are running in Remote Admin mode.
Thanks in advance,
Chris