Tom's Hardware: Topic Using qwinsta to drop terminal services sessions
Ad
Related Topics
- Terminal Services Login Problem
- Access to applications in Terminal Services
- Can not connect using RDC
- are files accessible to server provider when using \tsclie..
- Terminal Server connectivity problems after reboot
- Is it possible to map a drive over 3389 using 2003 TS + re..
- Terminal session to console of server
- Zone Alarm kills Terminal Services access
- Help with missing mapped drives using Cisco VPN w/ NT 4.0
Latest Reviews & Articles
Village Tronic ViBook: Multi-Monitor For Your Netbook
Once you've used a multi-monitor setup, it's almost impossible to go back to a single screen. Notebook users likely feel this pain most sharply. However, Village Tronic's ViBook proposes a USB-based solution for the folks looking for more display space. Read more
Setting Up Your First 64-Bit Digital Audio Workstation
You already know how to build a PC. But do you know how to take desktop hardware components and turn them into a digital audio workstation? John Brandon discusses how he pieced together his latest musical creation, along with the accompanying software. Read more
Windows 7 Versus XP: Which Belongs On Your Netbook?
Windows Vista was never really an option for netbook users, but the release candidate of Windows 7 piqued our interest. Can Microsoft finally retire Windows XP in the netbook space? Even now with RC1 available, the answer seems tied to driver development. Read more
A Lesson In Backup: Taking Care Of Your Data
If you aren't regularly backing up your data, now's a good time to start. In this piece we cover some of the basic backup strategies, a handful of available tools, and backup performance over USB 2.0 using Samsung's newest Story Station external drive. Read more
Tom's Hardware > Forum > Windows 2000/NT > Windows 2000/NT General Discussion > Using qwinsta to drop terminal services sessions
Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions.
Sign up now! Its free!
Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)
Sosh,
If the user acccount that runs qwinsta/rwinsta that is not known to the
remote machine, then you need to setup a 'trust' relationship. One way to to
it is run net use \\remoteMachine before running qwinsta/rwinsta
hope it helps
Thanks
Soo Kuan
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"sosh" <sosh@something.com> wrote in message
news
fHCIv4EFHA.3780@TK2MSFTNGP09.phx.gbl...
> 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
>
>
>
Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)
Thanks for the info Soo.
I've set up an exact copy of the production admin account on the dev server,
but still get the error. I used a packet sniffer, and it seems that qwinsta
is trying to communicate on port 445. I'll get that opened up for our IP
and cross my fingers.
"Soo Kuan Teo [MSFT]" <sookuant@online.microsoft.com> wrote in message
news:%23CGB%23u7EFHA.732@TK2MSFTNGP12.phx.gbl...
> Sosh,
> If the user acccount that runs qwinsta/rwinsta that is not known to the
> remote machine, then you need to setup a 'trust' relationship. One way to
to
> it is run net use \\remoteMachine before running qwinsta/rwinsta
> hope it helps
>
> Thanks
> Soo Kuan
>
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
>
> "sosh" <sosh@something.com> wrote in message
> newsfHCIv4EFHA.3780@TK2MSFTNGP09.phx.gbl...
> > 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
> >
> >
> >
>
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.
Add a reply
Cancel
Sponsored links