Re: Connecting from TSM to client

• Previous message: Henrik Johansen: "Session hangs when the 3. new user logson"
• In reply to: Vera Noest [MVP]: "Re: Connecting from TSM to client"
• Messages sorted by: [ date ] [ thread ]

Date: Tue, 7 Dec 2004 00:04:10 -0800

Hello Vera et al,

I have now DLL'd and tried that -- no change.

Thanks again,
_Scott

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns95B6E178730BAveranoesthemutforsse@207.46.248.16...
> Have you tried the update for XP SP2?
> 884020 - Programs that connect to IP addresses that are in the
> loopback address range may not work as you expect in Windows XP
> Service Pack 2
> http://support.microsoft.com/?kbid=884020
>
> --
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> --- please respond in newsgroup, NOT by private email ---
>
> "_Scott" <sfbing@hotmail.com> wrote on 05 dec 2004 in
> microsoft.public.windows.terminal_services:
>
> > Hello Vera,
> >
> > Thanks, but I do not think that this is it. I had been through
> > this, and went through it again.
> >
> > Since the WinXP system is a member of the domain, it gets its
> > firewall settings from the Win 2003 Server DC, via Windows
> > Firewall Group Policy, as described at the end of your article.
> > I have created Domain-Profile and Standard-Profile firewall
> > settings for the domain, with a different firewall log file for
> > each, and I can see that the WinXP system sees these profiles
> > because it creates entries in the two log files, depending upon
> > whether the DC is available.
> >
> > However, the TSadmin connection fails even when the firewall is
> > disabled, in the profile. Further, while the firewall is
> > enabled, I can see no dropped packets in the log files as a
> > result of an attempted TSadmin connection. (But I do see entries
> > for attempted HTTP connections, so I know that the log file is
> > working.)
> >
> > In no case can I make connections into the client via TSadmin,
> > and I am still looking for a solution.
> >
> > Thanks again,
> > _Scott
> >
> > "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> > in message
> > news:Xns95B1E9DD738B8veranoesthemutforsse@207.46.248.16...
> >> This should help:
> >>
> >> Troubleshooting Windows Firewall settings in Windows XP Service
> >> Pack 2
> >> http://support.microsoft.com/?kbid=875357
> >>
> >> --
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> http://hem.fyristorg.com/vera/IT
> >> --- please respond in newsgroup, NOT by private email ---
> >>
> >> "_Scott" <sfbing@hotmail.com> wrote on 30 nov 2004 in
> >> microsoft.public.windows.terminal_services:
> >>
> >> > Hello all,
> >> >
> >> > I have come into this forum looking for the answer to this
> >> > same problem.
> >> >
> >> > My Server is Win 2k3 with AD and DC. My client is Win XP
> >> > Pro. Since the day that I updated the XP client from SP1 to
> >> > SP2, I have been unable to use TSadmin to connect to the
> >> > client, to see who is logged in, send a message, or force a
> >> > logout. The message from TSadmin upon attempted right-click
> >> > of the client is "You could not be authenticated on this
> >> > server." I am a domain admin, and this domain admin account
> >> > is a member of the local Administrators group on the client.
> >> >
> >> > I can still login via RDP. I can do all sorts of things that
> >> > require admin-level access, such as access event viewer
> >> > remotely from the DC. There are no events, success or fail,
> >> > being generated during the TSadmin connection attempt.
> >> >
> >> > The SP2 update closes off lots of things, but I have been
> >> > unable to find anything that addresses this scenario, and had
> >> > almost written it off as coincidence until I saw the entry
> >> > below.
> >> >
> >> > Thanks,
> >> > _Scott Bingham
> >> >
> >> > "Eric" <Eric@discussions.microsoft.com> wrote in message
> >> > news:312EF306-2A2A-4D15-ACA9-BDF741D9BFD6@microsoft.com...
> >> >> I am running Win 2k3 with AD and DC. I am trying to
> >> >> accomplish this: From the Domain server, start TSM. Right
> >> >> click on the Domain root and
> >> > select
> >> >> "Connect to Computer". Type in the computer name or IP
> >> >> address and press
> >> > ok.
> >> >> The outcome should be that the computer is located and all
> >> >> processes
> >> > running
> >> >> on that machine can be displayed, also messages can be sent
> >> >> to the client
> >> > or
> >> >> the client can be forced to log off.
> >> >> After upgrading the client from XP Pro Sp1 to Sp2 I can no
> >> >> longer locate
> >> > any
> >> >> client logged into the domain with TSM. I get the error
> >> >> message from TSM saying that I could not be authenticated on
> >> >> this server. ( I can ping both client IP address and name
> >> >> from the server ) Any ideas?
>

• Previous message: Henrik Johansen: "Session hangs when the 3. new user logson"
• In reply to: Vera Noest [MVP]: "Re: Connecting from TSM to client"
• Messages sorted by: [ date ] [ thread ]