G
Guest
Guest
Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)
Hi,
I have locked myself out of a co-located machine (win2000) which I normally
use terminal services to access. The two sessions have become disconected
(but still active), and I recieve a liscensing error if I now try to
connect.
I have tried to drop the sessions by using qwinsta and rwinsta from our
development server (win2000) but recieve the following error:
Error opening Terminal server xxx.xxx.xxx.xxx
Error [1722]:The RPC server is unavailable.
Now the co-located machine is behind a firewall, but has port 3389 opened up
for terminal services access from our IP. Does qwinsta use any other ports?
One thing I do not understand about these two tools is authentication.
There is no optoin to enter a username password to get the query
information - does this mean that it will only work in a trust relationship
(the two machine are on unrelated domains) or qwinsta normally just offer
this information to anyone who asks?
Thanks for any info
Hi,
I have locked myself out of a co-located machine (win2000) which I normally
use terminal services to access. The two sessions have become disconected
(but still active), and I recieve a liscensing error if I now try to
connect.
I have tried to drop the sessions by using qwinsta and rwinsta from our
development server (win2000) but recieve the following error:
Error opening Terminal server xxx.xxx.xxx.xxx
Error [1722]:The RPC server is unavailable.
Now the co-located machine is behind a firewall, but has port 3389 opened up
for terminal services access from our IP. Does qwinsta use any other ports?
One thing I do not understand about these two tools is authentication.
There is no optoin to enter a username password to get the query
information - does this mean that it will only work in a trust relationship
(the two machine are on unrelated domains) or qwinsta normally just offer
this information to anyone who asks?
Thanks for any info