Re: Immediate Logoff

From: JD (ntborg_at_yahoo.com)
Date: 04/21/04 

Date: Tue, 20 Apr 2004 21:56:09 -0500

Thank you Patrick. I will try that in the morning. I will let you know my
results. 

-- 
Thanks
"Patrick Rouse [MVP]" <anonymous@discussions.microsoft.com> wrote in message
news:C751062E-CAF7-4289-B00D-3592144C1FE0@microsoft.com...
> What I am saying is that there is no magic button that MSFT can push to
fix the problem unless you can give them some information, i.e. I applied
hotfix X and product Y stopped working.
>
> What I would do is restore from backup and spend time recreating the
situation on a non-production workstation-class machine.
>
> If you call Microsoft PSS with a problem and it is fixed by them creating
a new hotfix then you will NOT be charged.  To save some time zip off your
event logs (system & application) and the system information files
(msinfo32.exe) that they will request.
>
> It's also worth trying a generic video driver knowing that there have been
problems with NVidia.  It's possible that there are problems with other
display drivers that people haven't reported yet.
>
> Patrick Rouse
> Microsoft MVP - Terminal Server
> http://www.workthin.com
>
>      ----- JD wrote: -----
>
>      Patrick,
>
>                    I have no evidence yet that Microsoft patches caused
this. I
>      however think it is ironic how it happened from a patch. We are just
looking
>      for a fix. Do you know where I can report this to Microsoft for free?
I
>      called Microsoft and they said that I have to find the hot fix #
before they
>      will send it to me lol. Others have said that Nividia drivers can
cause
>      this. I have an ATI.
>
>      Any Idea's
>
>
>      -- 
>      Thanks
>
>      The Borg
>
>      CSR
>      Payroll Services Corporation
>      "Patrick Rouse [MVP]" <anonymous@discussions.microsoft.com> wrote in
message
>      news:B8933C6F-3128-4A15-9F8F-30F2E8A017E6@microsoft.com...
>      > "To me it seems Microsoft locked it down with there patch".
>      >> What patch did you apply that you believe caused the problem?
>      > What need do you have for a fancy video driver on the server?
>      >> "I was lucky to that I was able to get it working by adding the
group to
>      the local admin group on the server."
>      > Be prepared for users to destroy your server's configuration if you
make
>      them all admins.
>      >> If you think a certain patch/hotfix/SP causes a specific problem,
please
>      post that information so it can be properly addressed.  Thanks.
>      >> P.S.  Always have a reliable backup you can restore from if you
install
>      something that causes unexpected results.
>      >> Patrick Rouse
>      > Microsoft MVP - Terminal Server
>      > http://www.workthin.com
>      >>      ----- NTborg wrote: -----
>      >>      I am having the same issue but not on a DC. Did you recently
patch
>      your
>      >      server with the new patches? I am thinking Microsoft broke my
>      terminal
>      >      server with there patches. I just hope they get it fixed. I
was lucky
>      to
>      >      that I was able to get it working by adding the group to the
local
>      admin
>      >      group on the server. To me it seems Microsoft locked it down
with
>      there
>      >      patch. I have not been able to confirm this.
>      >>      NTborg
>      >>>      "Matt Cole" <mcole@sigpc.com> wrote in message
>      >      news:193801c426e2$601d8bf0$a501280a@phx.gbl...
>      >> I have had terminal services installed on a DC for
>      >> several months without an issue. Lately when I attempt to
>      >> connect, I get the login box, but as soon as I login the
>      >> session goes immediately to logging off and the session
>      >> drops.
>      >>> This happens to all users. The users I am testing with
>      >> are domain admins so it is not a permissions issue. I
>      >> have checked the UDP properties of the connection and
>      >> there are no logon scripts running. I have been able to
>      >> work around this issue temporarily by using the /console
>      >> switch, that seems to work. It is only when I attempt to
>      >> login to a non-console session it has the problem.
>      >>> I have also tried the connection from 10-12 machines so
>      >> it is not an issue with the client. The same stations can
>      >> log onto other DC's with the same usernames so it is
>      >> something with particular DC.
>      >>> This same server is a terminal server license server, has
>      >> been activated and has 5 client licenses installed (non-
>      >> trial).  I have even attempted to uninstall terminal
>      >> services to see if I could connect using the remote
>      >> desktop connection (yes it is enabled). The status has
>      >> not changed.
>      >>> This has been very frustrating. Can anyone think of
>      >> anything I missed? I am a total loss of where to go next
>      >> without a total reinstall of the OS.
>      >>> R. Matthew Cole
>      >> MCSE 2k3, 2000, NT4
>      >> MCSA, NT-CIP, CCNA, MCP+I
>      >>>
Quantcast