Cannot connect nor maintain session 0

[Guest Markus]

I go to start->run and then enter the string:

mstsc /v:<servername> /console /f

It will connect me to the server, but if someone is already logged on using

session 0 (console session) I get an ID+1 session assigned to me as opposed

to me bumping that person off and getting assigned ID 0.

 

I have even created multiple connections to the same <servername> using the

above command and param's ( I also connected to a <severname2> machine from

my machine and attempted to get a console session started from it to

<severname> to no avail).

 

I am using Vista Enterprise on my email machine attempting to connect to

win2k3 servers.

 

Any suggestions?

 

Thanks,

Markus

[Guest Priya Raghavan [MSFT]]

Re: Cannot connect nor maintain session 0

 

Are you using the same user name as the one use in session 0?

 

Does the server have this setting enabled in tscc.msc?:

"Restrict each user to a single session"

 

--

Thanks,

Priya.

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"Markus" <Markus@discussions.microsoft.com> wrote in message

news:F3335C73-77A8-4645-8C62-9A5AD5C536D8@microsoft.com...

>I go to start->run and then enter the string:

> mstsc /v:<servername> /console /f

> It will connect me to the server, but if someone is already logged on

> using

> session 0 (console session) I get an ID+1 session assigned to me as

> opposed

> to me bumping that person off and getting assigned ID 0.

>

> I have even created multiple connections to the same <servername> using

> the

> above command and param's ( I also connected to a <severname2> machine

> from

> my machine and attempted to get a console session started from it to

> <severname> to no avail).

>

> I am using Vista Enterprise on my email machine attempting to connect to

> win2k3 servers.

>

> Any suggestions?

>

> Thanks,

> Markus

>

[Guest Markus]

Re: Cannot connect nor maintain session 0

 

Here is the thread:

> Are you using the same user name as the one use in session 0?

 

Yes.

> Does the server have this setting enabled in tscc.msc?:

> "Restrict each user to a single session"

 

I set Restrict each user ... = yes. But I think that only keeps ME from

multiple log ins.

 

What happens is this:

 

I log in using /console, and in task manager under the USER tab I can see

another user logged on (who also used /console to log in, I am not 'given'

his session like I should be, and instead get a non-console session).

 

Anyway, I right click on his logon info and select connect. This will give

me console session and 'bump' that user off. However, if that user logs on

again, using /console, they successfully log on, and I get moved to a non

console session and DO NOT get bumped off.

 

Please help. I am thinking I am going to have to flatten my machine. But I

would rather find out what happened to avoid it in the future.

 

Markus

 

 

"Priya Raghavan [MSFT]" wrote:

> Are you using the same user name as the one use in session 0?

>

> Does the server have this setting enabled in tscc.msc?:

> "Restrict each user to a single session"

>

> --

> Thanks,

> Priya.

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

>

> "Markus" <Markus@discussions.microsoft.com> wrote in message

> news:F3335C73-77A8-4645-8C62-9A5AD5C536D8@microsoft.com...

> >I go to start->run and then enter the string:

> > mstsc /v:<servername> /console /f

> > It will connect me to the server, but if someone is already logged on

> > using

> > session 0 (console session) I get an ID+1 session assigned to me as

> > opposed

> > to me bumping that person off and getting assigned ID 0.

> >

> > I have even created multiple connections to the same <servername> using

> > the

> > above command and param's ( I also connected to a <severname2> machine

> > from

> > my machine and attempted to get a console session started from it to

> > <severname> to no avail).

> >

> > I am using Vista Enterprise on my email machine attempting to connect to

> > win2k3 servers.

> >

> > Any suggestions?

> >

> > Thanks,

> > Markus

> >

>

>

[Guest Markus]

Re: Cannot connect nor maintain session 0

 

> > Are you using the same user name as the one use in session 0?

 

Actually, the above should be Yes and No :)

 

Yes up until I restricted each user to one login. However, this isn't a

concern at all.

 

The concern is what I describe below regarding console sessions. Further

testing shows that only I, using my user name and Remote log in from my

station, am experiencing this problem. Meaning two other co-workers who

remotely log in to the same sever using /console get the console session of

the other. When I log in, I get just a non-console session. All three of us

are running Vista connecting to a server running 2k3.

 

FWIW: Another co-worker has experienced this problem when RAS'ed in, but for

now that is the only time he has experienced it.

 

"Markus" wrote:

> Here is the thread:

>

> > Are you using the same user name as the one use in session 0?

>

> Yes.

>

> > Does the server have this setting enabled in tscc.msc?:

> > "Restrict each user to a single session"

>

> I set Restrict each user ... = yes. But I think that only keeps ME from

> multiple log ins.

>

> What happens is this:

>

> I log in using /console, and in task manager under the USER tab I can see

> another user logged on (who also used /console to log in, I am not 'given'

> his session like I should be, and instead get a non-console session).

>

> Anyway, I right click on his logon info and select connect. This will give

> me console session and 'bump' that user off. However, if that user logs on

> again, using /console, they successfully log on, and I get moved to a non

> console session and DO NOT get bumped off.

>

> Please help. I am thinking I am going to have to flatten my machine. But I

> would rather find out what happened to avoid it in the future.

>

> Markus

>

>

> "Priya Raghavan [MSFT]" wrote:

>

> > Are you using the same user name as the one use in session 0?

> >

> > Does the server have this setting enabled in tscc.msc?:

> > "Restrict each user to a single session"

> >

> > --

> > Thanks,

> > Priya.

> >

> > --

> > This posting is provided "AS IS" with no warranties, and confers no rights.

> >

> > "Markus" <Markus@discussions.microsoft.com> wrote in message

> > news:F3335C73-77A8-4645-8C62-9A5AD5C536D8@microsoft.com...

> > >I go to start->run and then enter the string:

> > > mstsc /v:<servername> /console /f

> > > It will connect me to the server, but if someone is already logged on

> > > using

> > > session 0 (console session) I get an ID+1 session assigned to me as

> > > opposed

> > > to me bumping that person off and getting assigned ID 0.

> > >

> > > I have even created multiple connections to the same <servername> using

> > > the

> > > above command and param's ( I also connected to a <severname2> machine

> > > from

> > > my machine and attempted to get a console session started from it to

> > > <severname> to no avail).

> > >

> > > I am using Vista Enterprise on my email machine attempting to connect to

> > > win2k3 servers.

> > >

> > > Any suggestions?

> > >

> > > Thanks,

> > > Markus

> > >

> >

> >

[Guest Vera Noest [MVP]]

Re: Cannot connect nor maintain session 0

 

=?Utf-8?B?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote on

14 jan 2008 in microsoft.public.windows.terminal_services:

>> > Are you using the same user name as the one use in session 0?

>

> Actually, the above should be Yes and No :)

>

> Yes up until I restricted each user to one login. However, this

> isn't a concern at all.

>

> The concern is what I describe below regarding console sessions.

> Further testing shows that only I, using my user name and

> Remote log in from my station, am experiencing this problem.

> Meaning two other co-workers who remotely log in to the same

> sever using /console get the console session of the other. When

> I log in, I get just a non-console session. All three of us are

> running Vista connecting to a server running 2k3.

>

> FWIW: Another co-worker has experienced this problem when RAS'ed

> in, but for now that is the only time he has experienced it.

>

> "Markus" wrote:

>

>> Here is the thread:

>>

>> > Are you using the same user name as the one use in session 0?

>>

>> Yes.

>>

>> > Does the server have this setting enabled in tscc.msc?:

>> > "Restrict each user to a single session"

>>

>> I set Restrict each user ... = yes. But I think that only

>> keeps ME from multiple log ins.

>>

>> What happens is this:

>>

>> I log in using /console, and in task manager under the USER tab

>> I can see another user logged on (who also used /console to log

>> in, I am not 'given' his session like I should be, and instead

>> get a non-console session).

>>

>> Anyway, I right click on his logon info and select connect.

>> This will give me console session and 'bump' that user off.

>> However, if that user logs on again, using /console, they

>> successfully log on, and I get moved to a non console session

>> and DO NOT get bumped off.

>>

>> Please help. I am thinking I am going to have to flatten my

>> machine. But I would rather find out what happened to avoid it

>> in the future.

>>

>> Markus

>>

>>

>> "Priya Raghavan [MSFT]" wrote:

>>

>> > Are you using the same user name as the one use in session 0?

>> >

>> > Does the server have this setting enabled in tscc.msc?:

>> > "Restrict each user to a single session"

>> >

>> > --

>> > Thanks,

>> > Priya.

>> >

>> > --

>> > This posting is provided "AS IS" with no warranties, and

>> > confers no rights.

>> >

>> > "Markus" <Markus@discussions.microsoft.com> wrote in message

>> > news:F3335C73-77A8-4645-8C62-9A5AD5C536D8@microsoft.com...

>> > >I go to start->run and then enter the string:

>> > > mstsc /v:<servername> /console /f

>> > > It will connect me to the server, but if someone is already

>> > > logged on using

>> > > session 0 (console session) I get an ID+1 session assigned

>> > > to me as opposed

>> > > to me bumping that person off and getting assigned ID 0.

>> > >

>> > > I have even created multiple connections to the same

>> > > <servername> using the

>> > > above command and param's ( I also connected to a

>> > > <severname2> machine from

>> > > my machine and attempted to get a console session started

>> > > from it to <severname> to no avail).

>> > >

>> > > I am using Vista Enterprise on my email machine attempting

>> > > to connect to win2k3 servers.

>> > >

>> > > Any suggestions?

>> > >

>> > > Thanks,

>> > > Markus

 

This is a wild guess, but are you maybe running (beta) SP1 for

Vista, or RDC 6.1?

With RDC 6.1, the /console switch is not supported anymore and

silently ignored, since there is no console session anymore on

Windows Server 2008.

To connect to a console session on a Windows 2003 server from an

RDC 6.1 client, use the new /admin switch in stead of /console.

 

Details here:

 

Changes to Remote Administration in Windows Server 2008

http://blogs.msdn.com/ts/archive/2007/12/17/changes-to-remote-

administration-in-windows-server-2008.aspx

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

[Guest Markus]

Re: Cannot connect nor maintain session 0

 

 

 

"Vera Noest [MVP]" wrote:

> This is a wild guess, but are you maybe running (beta) SP1 for

> Vista, or RDC 6.1?

> With RDC 6.1, the /console switch is not supported anymore and

> silently ignored, since there is no console session anymore on

> Windows Server 2008.

> To connect to a console session on a Windows 2003 server from an

> RDC 6.1 client, use the new /admin switch in stead of /console.

>

> Details here:

>

> Changes to Remote Administration in Windows Server 2008

> http://blogs.msdn.com/ts/archive/2007/12/17/changes-to-remote-

> administration-in-windows-server-2008.aspx

 

Not a wild guess at all, in fact it turns out to be spot on and exactly the

problem. Wow.

 

Thanks,

Markus

[Guest Vera Noest [MVP]]

Re: Cannot connect nor maintain session 0

 

=?Utf-8?B?TWFya3Vz?= <Markus@discussions.microsoft.com> wrote on

14 jan 2008 in microsoft.public.windows.terminal_services:

> "Vera Noest [MVP]" wrote:

>> This is a wild guess, but are you maybe running (beta) SP1 for

>> Vista, or RDC 6.1?

>> With RDC 6.1, the /console switch is not supported anymore and

>> silently ignored, since there is no console session anymore on

>> Windows Server 2008.

>> To connect to a console session on a Windows 2003 server from

>> an RDC 6.1 client, use the new /admin switch in stead of

>> /console.

>>

>> Details here:

>>

>> Changes to Remote Administration in Windows Server 2008

>> http://blogs.msdn.com/ts/archive/2007/12/17/changes-to-remote-

>> administration-in-windows-server-2008.aspx

>

> Not a wild guess at all, in fact it turns out to be spot on and

> exactly the problem. Wow.

>

> Thanks,

> Markus

 

Great! I'm glad that the problem is solved, and thanks for the

feedback, Markus!

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___