MSTerminalServices.org Forums

Forums Home | FAQ | Search | Profile | Private Messages | Log in/Register/Password

Remote Session Cannot Now Connect.

Page 1 of 1
Next:  General Discussions: Terminal Services in Windows Server 2008 Default security  
Author Message
Mark Stoker

External


Since: Aug 17, 2007
Posts: 17



(Msg. 1) Posted: Wed Mar 26, 2008 5:24 am
Post subject: Remote Session Cannot Now Connect.
Archived from groups: microsoft>public>windows>terminal_services (more info?)

We have 2 Windows 2003 Servers that have stopped accepting RDP connections
from 2 XP remote clients that have until yesterday connected without any
problem. At one of the remote sites I have a new Windows 2003 Server - this
can connect okay ?

When the XP client fails it get the following message 'The remote session
was disconnected because there were network problems durning the licensing
protocol' I have checked the license server and there are plenty of licenses
free.
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 19, 2003
Posts: 1954



(Msg. 2) Posted: Wed Mar 26, 2008 6:21 am
Post subject: Re: Remote Session Cannot Now Connect. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Check if this helps:

921045 - Error message when you try to connect to a remote computer
by using Remote Desktop on a Windows XP Professional Edition-based
computer: "The remote computer disconnected the session"
http://support.microsoft.com/?kbid=921045

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?TWFyayBTdG9rZXI=?=
<MarkStoker.RemoveThis@discussions.microsoft.com> wrote on 26 mar 2008:

> We have 2 Windows 2003 Servers that have stopped accepting RDP
> connections from 2 XP remote clients that have until yesterday
> connected without any problem. At one of the remote sites I have
> a new Windows 2003 Server - this can connect okay ?
>
> When the XP client fails it get the following message 'The
> remote session was disconnected because there were network
> problems durning the licensing protocol' I have checked the
> license server and there are plenty of licenses free.
Back to top
Send e-mail Login to vote
Mark Stoker

External


Since: Aug 17, 2007
Posts: 17



(Msg. 3) Posted: Wed Mar 26, 2008 7:43 am
Post subject: Re: Remote Session Cannot Now Connect. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

This is a strange one !!

I followed the KB as suggested and this did not work. I then tried a couple
of different things. Firstly, instead of connecting via our secure VPN I
opened up RDP port 3380 on the firewall of the remote router and port
forwarded RDP connections to the local server. This worked fine. But the RDP
connection via the VPN tunnel failed.

I have just come back from lunch and tried the connection again and IT WORKS
????? and on both sites that were problamatic.

Could this be a VPN/network problem ?

Any way its all up and running as it should.

"Vera Noest [MVP]" wrote:

> Check if this helps:
>
> 921045 - Error message when you try to connect to a remote computer
> by using Remote Desktop on a Windows XP Professional Edition-based
> computer: "The remote computer disconnected the session"
> http://support.microsoft.com/?kbid=921045
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?TWFyayBTdG9rZXI=?=
> <MarkStoker.RemoveThis@discussions.microsoft.com> wrote on 26 mar 2008:
>
> > We have 2 Windows 2003 Servers that have stopped accepting RDP
> > connections from 2 XP remote clients that have until yesterday
> > connected without any problem. At one of the remote sites I have
> > a new Windows 2003 Server - this can connect okay ?
> >
> > When the XP client fails it get the following message 'The
> > remote session was disconnected because there were network
> > problems durning the licensing protocol' I have checked the
> > license server and there are plenty of licenses free.
>
Back to top
Send e-mail Login to vote
Vera Noest [MVP]

External


Since: Sep 07, 2003
Posts: 9440



(Msg. 4) Posted: Wed Mar 26, 2008 12:22 pm
Post subject: Re: Remote Session Cannot Now Connect. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Just a guess, but it could be a problem with the MTU size.
There might be a black hole router between your client and the TS,
which blocks packets above a certain size. This prevents the
transfer of the permanent TS CAL to the client. Once you connected
succesfully and received the TS CAL, subsequent connections
wouldn't have the problem anymore (until it expires again).
Check in the TS Licensing Manager if the client has received a new
license. And also if it gives more info when the connection failed,
you should see an Event with a description of "cannot issue
license" if the above is the problem.

If this is the problem, you have to change the MTU size. Documented
here:

A licensing error occurred while the client was attempting to
connect.
http://technet2.microsoft.com/windowsserver/en/library/08e8da91-
c7b6-416d-a0a5-ff0fd760a7a51033.mspx
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFyayBTdG9rZXI=?=
<MarkStoker.RemoveThis@discussions.microsoft.com> wrote on 26 mar 2008 in
microsoft.public.windows.terminal_services:

> This is a strange one !!
>
> I followed the KB as suggested and this did not work. I then
> tried a couple of different things. Firstly, instead of
> connecting via our secure VPN I opened up RDP port 3380 on the
> firewall of the remote router and port forwarded RDP connections
> to the local server. This worked fine. But the RDP connection
> via the VPN tunnel failed.
>
> I have just come back from lunch and tried the connection again
> and IT WORKS ????? and on both sites that were problamatic.
>
> Could this be a VPN/network problem ?
>
> Any way its all up and running as it should.
>
> "Vera Noest [MVP]" wrote:
>
>> Check if this helps:
>>
>> 921045 - Error message when you try to connect to a remote
>> computer by using Remote Desktop on a Windows XP Professional
>> Edition-based computer: "The remote computer disconnected the
>> session" http://support.microsoft.com/?kbid=921045
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?TWFyayBTdG9rZXI=?=
>> <MarkStoker.RemoveThis@discussions.microsoft.com> wrote on 26 mar 2008:
>>
>> > We have 2 Windows 2003 Servers that have stopped accepting
>> > RDP connections from 2 XP remote clients that have until
>> > yesterday connected without any problem. At one of the remote
>> > sites I have a new Windows 2003 Server - this can connect
>> > okay ?
>> >
>> > When the XP client fails it get the following message 'The
>> > remote session was disconnected because there were network
>> > problems durning the licensing protocol' I have checked the
>> > license server and there are plenty of licenses free.
Back to top
Send e-mail Login to vote
Display posts from previous:   
    All times are: Eastern Time (US & Canada) (change) Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Looking for more Terminal Services info?

Sign up to the MSTerminalServices.org Monthly Newsletter, written by Terminal Server MVP & Citrix CTP Stefan Vermeulen, containing news, tips, interviews, links of the month and much more. Subscribe today and don't miss a thing!

Become an MSTerminalServices.org member!

Discuss your Terminal Services & Citrix issues with thousands of other SBC experts. Click here to join!

Community Area

Log in | Register