Jump to content

1st login always fails, 2nd always ok


Recommended Posts

Guest James S Clark
Posted

I have a recently installed W2K3 SP2 Terminal Server that always rejects the

1st attempt at a remote login but subsequent attempts work fine.

 

Upon 1st login the server leaves an "Idle" session hanging for a minute or

two without ever displaying the actual windows login dialog to the client.

Whilst this is happening the remote client sees the TS connection window

border but never gets a chance to enter log-in credentials. After a anything

from 20 seconds to 5 minutes the server resets the session connection attempt

and the connection window drops, displaying the error message "The remote

connection was ended because of a network error. Please try connecting to

the remote computer again.".

 

If a 2nd attempt is made at connecting from the same remote machine whilst

the first session is hanging the login always succeeds.

 

This anomaly occurs even after a restart of all equipment.

 

Has anyone seen this type of behaviour before?

 

--

Regards,

 

James S Clark

Software Developer & Technician

The Coleman Group (UK)

  • Replies 3
  • Created
  • Last Reply

Popular Days

Guest Vera Noest [MVP]
Posted

Re: 1st login always fails, 2nd always ok

 

Any warnings or errors in the EventLog on the server?

Is a logon at the physical console of the server normal, i.e. no

delay between hitting Ctrl-Alt-Del and the login window appearing?

_________________________________________________________

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?SmFtZXMgUyBDbGFyaw==?=

<JamesSClark@discussions.microsoft.com> wrote on 04 jan 2008 in

microsoft.public.windows.terminal_services:

> I have a recently installed W2K3 SP2 Terminal Server that always

> rejects the 1st attempt at a remote login but subsequent

> attempts work fine.

>

> Upon 1st login the server leaves an "Idle" session hanging for a

> minute or two without ever displaying the actual windows login

> dialog to the client. Whilst this is happening the remote

> client sees the TS connection window border but never gets a

> chance to enter log-in credentials. After a anything from 20

> seconds to 5 minutes the server resets the session connection

> attempt and the connection window drops, displaying the error

> message "The remote connection was ended because of a network

> error. Please try connecting to the remote computer again.".

>

> If a 2nd attempt is made at connecting from the same remote

> machine whilst the first session is hanging the login always

> succeeds.

>

> This anomaly occurs even after a restart of all equipment.

>

> Has anyone seen this type of behaviour before?

Guest James S Clark
Posted

Re: 1st login always fails, 2nd always ok

 

No, no errors in any event logs for either the server or the PCs trying to

connect.

 

Last time I was on site the console log-in was fine but I may have to book

another site visit to check this again.

 

To my dismay I have noticed that there are now more problems. IE7 won't

browse webapges but all pings to URLs and IPs work fine. Also, the TS drive

connectivity no longer works properly - it breaks the RDP connection

momentarily when I try to copy files between local & remote drives. Still no

eveidence of these problems in the event logs either.

 

Maybe I have OS corruption which is surprising since the machine has only

been installed for a few weeks :( Obviously I'm loath to re-install the OS

because it's disruptive and entails a lot of re-configuration. Any idea's?

Is it worth continuing to troubleshoot?

 

--

Regards,

 

James S Clark

Software Developer & Technician

The Coleman Group (UK)

 

 

"Vera Noest [MVP]" wrote:

> Any warnings or errors in the EventLog on the server?

> Is a logon at the physical console of the server normal, i.e. no

> delay between hitting Ctrl-Alt-Del and the login window appearing?

> _________________________________________________________

> 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?SmFtZXMgUyBDbGFyaw==?=

> <JamesSClark@discussions.microsoft.com> wrote on 04 jan 2008 in

> microsoft.public.windows.terminal_services:

>

> > I have a recently installed W2K3 SP2 Terminal Server that always

> > rejects the 1st attempt at a remote login but subsequent

> > attempts work fine.

> >

> > Upon 1st login the server leaves an "Idle" session hanging for a

> > minute or two without ever displaying the actual windows login

> > dialog to the client. Whilst this is happening the remote

> > client sees the TS connection window border but never gets a

> > chance to enter log-in credentials. After a anything from 20

> > seconds to 5 minutes the server resets the session connection

> > attempt and the connection window drops, displaying the error

> > message "The remote connection was ended because of a network

> > error. Please try connecting to the remote computer again.".

> >

> > If a 2nd attempt is made at connecting from the same remote

> > machine whilst the first session is hanging the login always

> > succeeds.

> >

> > This anomaly occurs even after a restart of all equipment.

> >

> > Has anyone seen this type of behaviour before?

>

Guest Vera Noest [MVP]
Posted

Re: 1st login always fails, 2nd always ok

 

I would certainly not rule out hardware problems (with the NIC, or

maybe the switch), especially when the equipment is brandnew.

 

Also check out the latest updates, I have seen reports about the

december IE7 security update causing problems with IE7 not being

able to display websites, but I'm not sure if that only applied to

XP or also to 2003, and if it also caused other network problems.

 

_________________________________________________________

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?SmFtZXMgUyBDbGFyaw==?=

<JamesSClark@discussions.microsoft.com> wrote on 08 jan 2008 in

microsoft.public.windows.terminal_services:

> No, no errors in any event logs for either the server or the PCs

> trying to connect.

>

> Last time I was on site the console log-in was fine but I may

> have to book another site visit to check this again.

>

> To my dismay I have noticed that there are now more problems.

> IE7 won't browse webapges but all pings to URLs and IPs work

> fine. Also, the TS drive connectivity no longer works properly

> - it breaks the RDP connection momentarily when I try to copy

> files between local & remote drives. Still no eveidence of

> these problems in the event logs either.

>

> Maybe I have OS corruption which is surprising since the machine

> has only been installed for a few weeks :( Obviously I'm loath

> to re-install the OS because it's disruptive and entails a lot

> of re-configuration. Any idea's? Is it worth continuing to

> troubleshoot?


×
×
  • Create New...