2003 Remote Desktop Connection failing

[gswitz]

I'm so bummed. My server's across town, and I'm not longer able to use remote
desktop connection to connect to it. When I initially set up the server, I
configured it to use Terminal Server (as was required in W2000 Server for
remote control). Then, I learned about not having to do this if I used remote
desktop connection. I have been working happily along for a good while now (9
months or more). Recently I started seeing warnings but I foolishly ignored
them and now I'm out in the snow. I'm not really a server guy. Can anyone
give me easish instructions on how to get remote desktop connection running
again? I can still create a VPN to the server, but that's all. Also, my home
computer is not part of the domain for the server.

Thanks,

Geoff

[gswitz]

It looks like the problem is related to the fact that I disconnect from the
PC, rather than logging off. I'm currently getting errors saying that I
cannot login because I already have a session on the PC. Interestingly, this
message comes when I try to login using the PPP IP address (which I never
use). I've been using the internal IP address for the server, after
establishing the VPN. I never knew that it was an option to use the PPP
address. So, I'll go ahead and wait for a power failure to cause the PC to
reboot and then try to connect. I can still FTP and the server seems to be
working normally (otherwise).

Thanks,

Geoff

Post by gswitz
I'm so bummed. My server's across town, and I'm not longer able to use remote
desktop connection to connect to it. When I initially set up the server, I
configured it to use Terminal Server (as was required in W2000 Server for
remote control). Then, I learned about not having to do this if I used remote
desktop connection. I have been working happily along for a good while now (9
months or more). Recently I started seeing warnings but I foolishly ignored
them and now I'm out in the snow. I'm not really a server guy. Can anyone
give me easish instructions on how to get remote desktop connection running
again? I can still create a VPN to the server, but that's all. Also, my home
computer is not part of the domain for the server.
Thanks,
Geoff

[gswitz]

The whole problem is now resolved.

I changed Terminal Server Licensing to per user rather than per client.

I suppose when I rebuilt my home pc last time and gave it a new name the
server considered it a new client.

Thanks,

G

Post by gswitz
It looks like the problem is related to the fact that I disconnect from the
PC, rather than logging off. I'm currently getting errors saying that I
cannot login because I already have a session on the PC. Interestingly, this
message comes when I try to login using the PPP IP address (which I never
use). I've been using the internal IP address for the server, after
establishing the VPN. I never knew that it was an option to use the PPP
address. So, I'll go ahead and wait for a power failure to cause the PC to
reboot and then try to connect. I can still FTP and the server seems to be
working normally (otherwise).
Thanks,
Geoff

Post by gswitz
I'm so bummed. My server's across town, and I'm not longer able to use remote
desktop connection to connect to it. When I initially set up the server, I
configured it to use Terminal Server (as was required in W2000 Server for
remote control). Then, I learned about not having to do this if I used remote
desktop connection. I have been working happily along for a good while now (9
months or more). Recently I started seeing warnings but I foolishly ignored
them and now I'm out in the snow. I'm not really a server guy. Can anyone
give me easish instructions on how to get remote desktop connection running
again? I can still create a VPN to the server, but that's all. Also, my home
computer is not part of the domain for the server.
Thanks,
Geoff