Spooling, RAS and Remote Desktop fails after August-Updates

Hi there,

have 10 servers running. All Windows2000 Advanced Servers.
Single Domain, very simple.
Did the August-Updates in all machines.
Unfortunatley on the Domaincontroller some problems occured:
1.The system is very slow.
2.The PrintSpooler won't work properly.
3. Remote Desktop won't work anymore.
4. RAS-Settings disappeard

1.All processes look normal, no 100%CPU-Usage etc. While updating, i had a
error with my VLAN-Configutration, but solveable.
2. Since the Update, we can't print anymore. When trying to send a
test-document, i get an error that the Spool-Server is full. The Status of
all printers are OK, i can get all device informations.
Had some Shockwave-Files in WINNT/system32/spool/printers....deleted them as
suggested in another post. no changes
3. Remote Desktop won't connect to this server anymore. "The connection was
ended because of a networkerror"
4. After the Update, all my Static Routes were deleted.

See this link for details on the spooler issue:
http://support.microsoft.com/?kbid=832219

thanks steve !
that fixed the spooler problem.

Anyone any Ideas about the Remote Desktop Issue? Remote works fine on
similar machines with same config and SP-Level

I've installed VNC to have access somehow.
I can see an Icon popping up for a millisecond in TerminalServer Monitor,
when i try connecting with my Client . But the Icon gets "kicked out" and the
Client tells me that there maybe a networkerror or maximum users exceeded.
Have already reinstalled Terminalservices. Can't see any Entries in the
Eventlog-
Is there a Logfile for RDP-Sessions? or Switch to turn on Eventlogs?

Thanks for Help

Hakan

"" wrote:

> See this link for details on the spooler issue:
> http://support.microsoft.com/?kbid=832219
>
>

short update:

telnet on port 3389 "works"
at least, it gives no error, but a blank screen.
don't know what to expect here; should there be a login-echo?

"" wrote:

> See this link for details on the spooler issue:
> http://support.microsoft.com/?kbid=832219
>
>

"Spool,RDP & RAS fails after 08-updates" < oft.com> wrote in message
news:9B7D3541-0F93-4473-A8C6-...
> short update:
>
> telnet on port 3389 "works"
> at least, it gives no error, but a blank screen.
> don't know what to expect here; should there be a login-echo?


Apparently not.

<title>KB187628 - Using Telnet to Test Port 3389 Functionality</title>

(MSKB Titles-only search for
3389
)


<quote>
If telnet is successful, you simply receive the telnet screen and a cursor.
On the Terminal Server, Terminal Server Administration will show a blue
computer icon with no other information. The Telnet connection will also
consume an idle session.
</quote>


---


>
> "" wrote:
>
>> See this link for details on the spooler issue:
>> http://support.microsoft.com/?kbid=832219
>>
>>

hi, thanks for input

thats what i get!
A blank screen and a blue Icon in the Terminal Server Administration.
I get the same Icon when using the Client, but it disapears instantly.


"Robert Aldwinckle" wrote:

> "Spool,RDP & RAS fails after 08-updates" < oft.com> wrote in message
> news:9B7D3541-0F93-4473-A8C6-...
> > short update:
> >
> > telnet on port 3389 "works"
> > at least, it gives no error, but a blank screen.
> > don't know what to expect here; should there be a login-echo?
>
>
> Apparently not.
>
> <title>KB187628 - Using Telnet to Test Port 3389 Functionality</title>
>
> (MSKB Titles-only search for
> 3389
> )
>
>
> <quote>
> If telnet is successful, you simply receive the telnet screen and a cursor.
> On the Terminal Server, Terminal Server Administration will show a blue
> computer icon with no other information. The Telnet connection will also
> consume an idle session.
> </quote>
>
>
> ---
>
>
> >
> > "" wrote:
> >
> >> See this link for details on the spooler issue:
> >> http://support.microsoft.com/?kbid=832219
> >>
> >>
>
>
>

hi,
found solution for my problem here:

http://support.microsoft.com/default...b;en-us;323497

>>Another frequent cause of these problems stems from issues with some registry values in the TermService\Parameters registry key. To this end, could you export the following key: HKLM\System\CurrentControlSet\Services\TermService s\Parameters

After doing this, delete the Certificate, X509 Certificate, and X509
Certificate ID values, and restart the Terminal Server. These values should
be regenerated on reboot (but keep the Exported values just in case). This is
documented in Q323497. The X509 Certificate and X509 Certificate ID values
have also been known to cause this problem, so delete them as well. Also see
Q329896. In 9 out of 10 cases this resolves the issue