Remote Access

[steve]

We have a few admins here that remote into some of our servers. but when 1 of
us in remoted in, and another remotes in, we get kicked off. how can i
prevent this? is there a setting somewhere to increase the number of sessions?

Thx,
Steve

 

[Ehren]

With using "remote desktop for administration" as they call it you are only
allowed two remote sessions to a particular server. If someone uses it and
disconects (clicks the X in the RDP client instead of logging off) and you do
not have your TS configuration set you boot idle connections after a certain
time that connection will remain in use and use up 1 of your 2 slots. If 2
people do this then both will remain used and no one will be able to remote
in.

The only way to have more than two connections is to set up Terminal
Services and buy licenses for terminal services for however many connections
you want/need.

The built in remote desktop feature as I said only allows a max of 2
concurrent connections.

Hope that helps
/Ehren - MCSE2003

"steve" wrote:

> We have a few admins here that remote into some of our servers. but when 1 of
> us in remoted in, and another remotes in, we get kicked off. how can i
> prevent this? is there a setting somewhere to increase the number of sessions?
>
> Thx,
> Steve

 

[steve]

so i should set the ts config in the gp to 2?

Thx

"Ehren" wrote:

> With using "remote desktop for administration" as they call it you are only
> allowed two remote sessions to a particular server. If someone uses it and
> disconects (clicks the X in the RDP client instead of logging off) and you do
> not have your TS configuration set you boot idle connections after a certain
> time that connection will remain in use and use up 1 of your 2 slots. If 2
> people do this then both will remain used and no one will be able to remote
> in.
>
> The only way to have more than two connections is to set up Terminal
> Services and buy licenses for terminal services for however many connections
> you want/need.
>
> The built in remote desktop feature as I said only allows a max of 2
> concurrent connections.
>
> Hope that helps
> /Ehren - MCSE2003
>
> "steve" wrote:
>
> > We have a few admins here that remote into some of our servers. but when 1 of
> > us in remoted in, and another remotes in, we get kicked off. how can i
> > prevent this? is there a setting somewhere to increase the number of sessions?
> >
> > Thx,
> > Steve

 

[Ehren]

Another reason you could get kicked off like that is if you are both trying
to remote into the console session. There can only be one active console
session. If someone is using the computer locally and someone remotes into
the console session then the local terminal will become locked and if the
person at the local terminal logs back in it would kick out the remote user.
I bet that more accurately describes your issue.

Are you actually using the remote desktop client
(Start/Programs/Accessories) to connect?

"steve" wrote:

> so i should set the ts config in the gp to 2?
>
> Thx
>
> "Ehren" wrote:
>
> > With using "remote desktop for administration" as they call it you are only
> > allowed two remote sessions to a particular server. If someone uses it and
> > disconects (clicks the X in the RDP client instead of logging off) and you do
> > not have your TS configuration set you boot idle connections after a certain
> > time that connection will remain in use and use up 1 of your 2 slots. If 2
> > people do this then both will remain used and no one will be able to remote
> > in.
> >
> > The only way to have more than two connections is to set up Terminal
> > Services and buy licenses for terminal services for however many connections
> > you want/need.
> >
> > The built in remote desktop feature as I said only allows a max of 2
> > concurrent connections.
> >
> > Hope that helps
> > /Ehren - MCSE2003
> >
> > "steve" wrote:
> >
> > > We have a few admins here that remote into some of our servers. but when 1 of
> > > us in remoted in, and another remotes in, we get kicked off. how can i
> > > prevent this? is there a setting somewhere to increase the number of sessions?
> > >
> > > Thx,
> > > Steve

 

[steve]

yes, we use the remote desktop..

"Ehren" wrote:

> Another reason you could get kicked off like that is if you are both trying
> to remote into the console session. There can only be one active console
> session. If someone is using the computer locally and someone remotes into
> the console session then the local terminal will become locked and if the
> person at the local terminal logs back in it would kick out the remote user.
> I bet that more accurately describes your issue.
>
> Are you actually using the remote desktop client
> (Start/Programs/Accessories) to connect?
>
> "steve" wrote:
>
> > so i should set the ts config in the gp to 2?
> >
> > Thx
> >
> > "Ehren" wrote:
> >
> > > With using "remote desktop for administration" as they call it you are only
> > > allowed two remote sessions to a particular server. If someone uses it and
> > > disconects (clicks the X in the RDP client instead of logging off) and you do
> > > not have your TS configuration set you boot idle connections after a certain
> > > time that connection will remain in use and use up 1 of your 2 slots. If 2
> > > people do this then both will remain used and no one will be able to remote
> > > in.
> > >
> > > The only way to have more than two connections is to set up Terminal
> > > Services and buy licenses for terminal services for however many connections
> > > you want/need.
> > >
> > > The built in remote desktop feature as I said only allows a max of 2
> > > concurrent connections.
> > >
> > > Hope that helps
> > > /Ehren - MCSE2003
> > >
> > > "steve" wrote:
> > >
> > > > We have a few admins here that remote into some of our servers. but when 1 of
> > > > us in remoted in, and another remotes in, we get kicked off. how can i
> > > > prevent this? is there a setting somewhere to increase the number of sessions?
> > > >
> > > > Thx,
> > > > Steve