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@xxxxxxxxxxxxxxxxxxxxxxxxx> 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?

.

Relevant Pages

  • Re: Connecting a remote workstation to a domain
    ... If you have more than a couple of remote workstations connecting to the SBS ... server via VPN, you really need to consider a Terminal Server in the main ... "Log in using a dial up connection" checkbox, ... roaming profile then synchronizes with the server over the VPN); ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with Web based client
    ... Seems like you are having problems accessing the web server on the PC you ... > My remote desktop connection works fine when I connect with a Remote ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote Access and ISA Server in SBS 2003?
    ... I am glad to hear the Remote Access Wizard is working fine now. ... there is no difference in VPN between SBS 4.5 and SBS ... Error Message: VPN Connection Error 800: Unable to Establish Connection ... the external NIC of the SBS Server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Office Configuration Suggestions?
    ... Welcome to SBS newsgroup. ... I understand that you want to keep the remote office continue working even ... after the main internet connection on the main office is not available. ... If you want to join the remote server to a SBS domain and become a member ...
    (microsoft.public.windows.server.sbs)
  • RE: Another Remote Connection Manager Problem
    ... > internal and 192.168.1.3 for the internet connection. ... > via the SBS server to all clients. ... > With this configuration OWA and Remote Workplace are operational. ... > Connection Manager to connect to the VPN server and gain access to a shared ...
    (microsoft.public.windows.server.sbs)