Archived from groups: microsoft.public.windows.terminal_services,microsoft.public.windowsnt.terminalserver.connectivity,microsoft.public.windowsnt.terminalserver.setup (
More info?)
my experiences, there are some good changes of recovering a termianl server
with the following steps:
-remove the terminal service
- remove iis from the server
-reinstall iis server
-reinstall terminal server service
sometimes this helps.
cheers.
"Scott" <foo> wrote in message news:ehTLA0kbEHA.1548@TK2MSFTNGP12.phx.gbl...
> My judgement about MS and Terminal Services are:
>
> * MS burying the TS into the OS so deep that the only way to reinstall
this
> component is to reinstall the OS. If this were Unix, this functionality
> wouldn't be buried in the OS. I could just reinstall the application.
>
> * No way to bounce the TS service.
>
> * No debugging clues in the event log.
>
> * No real help in the KB. When I searched on the error dialog text, there
> weren't any useful hits.
>
> Who knows, perhaps the security update broke the functionality? FWIW I
work
> in IT, and have a little knowledge about networking, although of course
> there is so much I don't know. I doubt it was me who messed up, although
> perhaps there is some conflict with either s/w or security updates that
were
> installed.
>
> Actually, you did have a great suggestion tho - I hadn't thought to look
at
> the restore points. I've never actually had need to use them before. I
see
> that on 14Jul, a number of KB's were installed. I'll back them out and
see
> what happens.
>
> "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote in message
> news:Xns952C7933C5FF5veranoesthemutforsse@207.46.248.16...
> > Scott, as far as I know, you can't re-install Remote Desktop only
> > without re-installing the whole OS. And with this kind of
> > problems, that's the only sensible thing to do. You never know
> > what else has been corrupted.
> >
> > You could go back to the latest restore point, though, and undo
> > the software installation.
> >
> > I must also say that your judgement about Microsofts Remote
> > Desktop sounds a bit unjustified. After all, it's probably you who
> > messed up, not Microsoft, isn't it?
> >
> > --
> > Vera Noest
> > MCSE,CCEA, Microsoft MVP - Terminal Server
> >
http://hem.fyristorg.com/vera/IT
> > *----------- Please reply in newsgroup -------------*
> >
> > "Scott" <foo> wrote in news:O7H7p3jbEHA.2908@TK2MSFTNGP10.phx.gbl:
> >
> > > Yeah, plus I had this running about a week ago. It stopped
> > > working when I rebooted my home WXP machine. To be honest I
> > > can't remember why I rebooted; it may have been a security
> > > update requirement, or I may have installed some s/w. But
> > > regardless, I don't know what changed. One thing that didn't
> > > change is the firewall setup. And I've tried both the W2K
> > > ("old") client and WXP ("new") client on my office W2K Pro
> > > machine.
> > >
> > > At this point I'm stumped. If there is a way to reinstall
> > > Terminal Services/Remote Desktop Connection without reinstalling
> > > all of WXP, please let me know.
> > >
> > > In the meantime, I'm trying TightVNC now. It would really be a
> > > shame if open source TightVNC works better than multi-billion
> > > $$$ MS Terminal Services.
> > >
> > > "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se> wrote
> > > in message
> > > news:Xns952BA9D3CE9F3veranoesthemutforsse@207.46.248.16...
> > >> Strange. Service is running, you can telnet to 3389, but not
> > >> connect with an rdp client, and nothing in the eventlog?
> > >>
> > >> I have no idea what else you could try.
> > >>
> > >> --
> > >> Vera Noest
> > >> MCSE,CCEA, Microsoft MVP - Terminal Server
> > >>
http://hem.fyristorg.com/vera/IT
> > >> *----------- Please reply in newsgroup -------------*
> > >>
> > >> "Scott" <foo> wrote in
> > >> news:u8XX5YZbEHA.3664@TK2MSFTNGP12.phx.gbl:
> > >>
> > >> > "The remote connection has timed out. Please try connecting
> > >> > to the remote computer again."
> > >> >
> > >> > No messages in the event log.
> > >> >
> > >> > "Vera Noest [MVP]" <Vera.Noest@remove-this.hem.utfors.se>
> > >> > wrote in message
> > >> > news:Xns952B907083F9Fveranoesthemutforsse@207.46.248.16...
> > >> >> Yes, it's normal that you cannot stop or start the TS
> > >> >> service, only modify the startup parameters.
> > >> >>
> > >> >> 278657 - Terminal Services Cannot Be Manipulated
> > >> >>
http://support.microsoft.com/?kbid=278657
> > >> >>
> > >> >> What error message do you get when you try to connect?
> > >> >>
> > >> >> --
> > >> >> Vera Noest
> > >> >> MCSE,CCEA, Microsoft MVP - Terminal Server
> > >> >>
http://hem.fyristorg.com/vera/IT
> > >> >> *----------- Please reply in newsgroup -------------*
> > >> >>
> > >> >> "Scott" <foo> wrote in
> > >> >> news:#DkFbLNbEHA.2544@TK2MSFTNGP10.phx.gbl:
> > >> >>
> > >> >> > Win XP Pro
> > >> >> >
> > >> >> > I cannot connect to my Win XP Pro machine via terminal
> > >> >> > services/remote desktop connection. I can telnet to the
> > >> >> > machine on 3389. Here is a snippet from my firewall log:
> > >> >> >
> > >> >> > Mon, 2004-07-19 00:48:10 - TCP packet -
> > >> >> > Source:XXX.XXX.XXX.XXX,2297 ,WAN -
> > >> >> > Destination:XXX.XXX.XXX.XXX,3389 ,LAN [Forward] - [Inbound
> > >> >> > Rule(5) match]
> > >> >> >
> > >> >> > (Inbound Rule (5) is port 3389)
> > >> >> >
> > >> >> > I also hooked up my laptop to my internal network, and
> > >> >> > tried to connect directly via the internal IP. This would
> > >> >> > bypass the firewall and connect directly to the machine.
> > >> >> > Again no joy.
> > >> >> >
> > >> >> > No entries in the event log.
> > >> >> >
> > >> >> > I think terminal services is stuffed. Is it possible to
> > >> >> > reinstall it without reinstalling all of WXP?
> > >> >> >
> > >> >> > Is it normal that the terminal services service is
> > >> >> > started, but unable to be bounced (all options are grayed
> > >> >> > out)?
> > >> >> >
> > >> >> > Thanks...
> >
>
>
Facebook
Twitter
Instagram