Re: Terminal Service Manager not connecting -- Renewed Issue
Ok, finally got a solution for an Upgraded 2000 to 2003 Server. In addition
to having the HKLM\System\CurrentControlSet\Control\Terminal
Server\TSAdvertise DWORD set to 1,
You also want to have the
HKLM\System\CurrentControlSet\Control\SecurePipeServer\Winreg read permission
for the local service.
Thanks guys, and Viera as well! This is the answer for the 2000 to 2003
upgraded server TSM connection issue.
"Soo Kuan Teo [MSFT]" wrote:
> Please try TP suggestions.
> One quick check is, disable the firewall and see if the issue still repro.
> If it doesn't repro, then it implies that firewall is preventing you from
> connecting.
> Thanks
> Soo Kuan
>
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "TP" <tperson.knowspamn@mailandnews.com> wrote in message
> news:umNNUlHFIHA.1164@TK2MSFTNGP02.phx.gbl...
> > Hi David,
> >
> > You most likely have already done this, but have you made sure that
> > windows firewall is either disabled or that you are permitting the
> > necessary ports? Also check that Group Policy is not set to disable
> > "Allow remote administration exception".
> >
> > Besides the above you could do a detailed comparision of all the registry
> > settings between a working and non-working server. Keep in mind that
> > TS-related registry settings are many and scattered and you may not know
> > where many of them are located. Check tsoc.inf file for some help finding
> > areas you may not be aware of (not all are there but many). Also don't
> > forget related services and their entries (for example, Remote registry).
> >
> > If this is a serious issue then it may make sense to contact Microsoft PSS
> > for help. If the problem turns out to be a bug in windows you will not be
> > charged.
> >
> > -TP
> >
> > davidtheweb wrote:
> >> In a question on 6 Oct 07, I posted this question, about a 2003 Server
> >> refusing connection from my Terminal Service Manager. Viera solved
> >> part of the problem, isolating it as an issue with 2000 upgrading to
> >> 2003, and also found a way to allow XP SP2 machines to be connected
> >> to a TSM session, but never did resolve getting the 2003 machine
> >> (upgraded from 2000) to respond to TSM requests. I feel that
> >> resolving this issue would be a coup and a great help to many admins.
> >>
> >> So I renew this question...
> >>
> >> Thanks
>
>
