Re: Remote Desktop connect then disconnects

OK, if you already did the rebuild from scratch, it's not much use
to do it again. I thought that maybe you had done a rebuild from
backup, which also could have contained corrupt files.

I'm really running out of ideas.
Basically, everything works fine, except rdp, isn't it? And rdp
does accept connections, but drops them immediately.

I assume that you have already updated the servers BIOS and all
drivers (especially the Broadcom drivers) to the latest version?

You could try to install VNC, I've no idea if that will work or
not. At best, it will provide a workaround, and if it doesn't work,
you know that the problem is not confined to rdp alone.

You could also try to use NetMon to see if that gives you a cause
for dropping the connection.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Bill Cart" <wcart@xxxxxxxxxxxxxxxxxxxxxxxx> wrote on 06 apr 2007
in microsoft.public.windows.terminal_services:

Thanks for the idea but deleting and restoring the connection
had no effect. I can connect to the other servers with this one
and they can see and connect to it but it then drops the
connection right away. All 6 of the servers have the same
motherboard and prior to the array failure and rebuild this one
was working OK. I can connect to it with the SQL enterprise
manager and it works OK with network neighborhood.

I did rebuild this server from scratch with a fresh windows 2003
install. This SQL computer has Great Planes, CBORD, Time Star
and Mysis on it. All of this software is very complicated and a
bit touchy. We spent all week on it and are still trying to get
all of the software put back as it was.

If I even suggest rebuilding it again I better start looking for
a new job as a truck driver. After this it might not be that bad
an idea.

The only good part of it is that we may finally be getting the
Acronis backup software and a tape drive with enough room to
hold images of all of the servers. I had a current backup of
this server but it was on the array that failed and I forgot to
copy it off to another location before the array failed. I had
an older ASR of the server but I could not find the matching
floppy for it.

I may just try putting the VNC software on it to see if I can
get that to work. The previous administrator had all the
computers set up with that. Do you think that might work?


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message
news:Xns9909905598878veranoesthemutforsse@xxxxxxxxxxxxxxxx
A Windows 2003 server uses rdp 5.2.
The fact that you installed rdp 6.0 *client* doesn't change
that. The first server to use the rdp 6.x protocol will be the
next server version, code named Longhorn.
When you recreated the rdp-tcp 5.2 connection, did that solve
the problem?
If it doesn't, I would seriously consider a fresh installation
of the whole server from scratch, because something isn't
right. How did you rebuild the server after the crash?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Bill Cart" <bcart@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 05
apr 2007 in microsoft.public.windows.terminal_services:

I have tried all sorts of stuff with no results. I installed
the Web Remote Desktop to see it that might help. I have been
through the registery and all of the setting there look good.
TSEnabled is 1 and fDenyTSConnections is 0. I updated the
network adapter drivers.

When I deleted the rdp-tpc connections I found that it will
only set itself to RDP 5.2. The server is at SP2 and has had
the RDP 6.0 client installed on it. I tried to intall it again
and it says the service pack of computer is later than the
update. But why would the connection be 5.2? I thought about
deleting and reinstalling the service pack but it say that a
lot of the software may stop working if I uninstall it.


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:Xns990790E6EC43Fveranoesthemutforsse@xxxxxxxxxxxxxxxx
Yes, both the full rdp client and the web client use the
rdp-tcp connection.
Just delete the connection in TS Configuration, and then
create a new one (right-click on Connections - Create new
connection)
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Bill Cart" <wcart@xxxxxxxxxxxxxxxxxxxxxxxx> wrote on 03 apr
2007 in microsoft.public.windows.terminal_services:

I can't find anything in the eventlog that seems to relate
to the problem. We are using the standard Windows Remote
desktop not the Remote Desktop Web Connection. Does that use
the rdp-tcp connection also? Should I just delete the
connection and then set up RRAS or can I recreate the
connection without doing that?

"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:Xns9906DFAFD1F11veranoesthemutforsse@xxxxxxxxxxxxxxxx
Anything in the EventLog?
I think that I would delete and then recreate the rdp-tcp
connection, in TS Configuration.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Bill Cart" <wcart@xxxxxxxxxxxxxxxxxxxxxxxx> wrote on 02
apr 2007 in microsoft.public.windows.terminal_services:

We had a server crash and I have just spent the weekend
rebuilding it. I have almost everything working but I
can't log into it from any other computer using remote
desktop. We have a TAS server on the network but this
computer does not have TS installed on it, only Remote
Desktop enabled.

The message is

Your Remote Desktop session has ended, possibly for one of
the following reasons:
The administrator has ended the session
An error has occurred while the connection was being
established A network problem occurred.

I can ping the computer and the file shares on it show up
in network neighborhood and the backup works.

I have been to windows update and it has everything it
will take including the new RDP client. I rebuilt the
computer with same name so I had to delete it from active
directory. It shows up in active directory now and it
shows up in NDS. Yesterday before I left I intalled SQL
server on it and connected to it with remote desktop but
when I got home and since then I could not connect to it.
I don't see anything in the logs. I might be a bit burnt
out so what am I missing?

The server is a CybertronPC with a SuperMicro motherboard
which has 2 built in Broadcom nics (one disabled).
.

Relevant Pages

  • RE: Windows Remote Desktop
    ... between the server and client in addition to RDP encryption. ... On the topic of securing RDP i was wondering if anyone can help.... ... connection is difficult. ... >We provide Ethical Hacking, Advanced Ethical Hacking, Intrusion ...
    (Security-Basics)
  • Re: MSKB 891957, VSS Update for Windows Server 2003
    ... I left the connection sit idle and checked back in an hour. ... server and browsed around for a few minutes. ... it would seem that there is still some issue with the V6 RDP ... I left the server with user Backup logged in when I left the ...
    (microsoft.public.windows.server.general)
  • Re: Storing Username/Password problem
    ... It's set on a per-server basis, so that any incoming RDP connection to that server is logged on with the credentials specified in Terminal Services Configuration. ...
    (microsoft.public.windows.terminal_services)
  • Re: MSKB 891957, VSS Update for Windows Server 2003
    ... Well, it turns out the RDP connection dropping issue won't go away, ... level to the server in the office may have an affect on the issue. ... I just remembered I also re-installed RDP Client V6 last night as ... I left the server with user Backup logged in when I left the ...
    (microsoft.public.windows.server.general)
  • Re: 2003 Server RDP errors
    ... help confirm its a remote connection fault rather thanthe RDP application. ... have you tried setting this server up as a Terminal Servicer via the ... Looked in the event viewer and after trying RDP using two different accounts, ... Terminal Services, allowing multiple users to use RDP simultaniously, called ...
    (microsoft.public.windows.server.general)