Remote Desktop Stop Working After W2k3 SP2

[josemlos@gmail.com]

Can anyone help me.
After installation of SP2 for Windows Server 2003, Remote Desktop on
that server stop working.

I had restart several times.
I even had instal update (Remote Desktop Connection (Terminal Services
Client 6.0) for Windows Server 2003 (KB925876)).
But always without sucess.

Can anyone help?


Thanks,

Miguel Silva

 

[Vera Noest [MVP]]

Is the Terminal Server service running?
Is the server listening on port 3389? Check from the console, by
typing "netstat -an" (without the quotes) in a command window.
Are there any errors or warnings in the EventLog on the server?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

josemlos@gmail.com wrote on 18 jul 2007 in
microsoft.public.windows.terminal_services:

> Can anyone help me.
> After installation of SP2 for Windows Server 2003, Remote
> Desktop on that server stop working.
>
> I had restart several times.
> I even had instal update (Remote Desktop Connection (Terminal
> Services Client 6.0) for Windows Server 2003 (KB925876)).
> But always without sucess.
>
> Can anyone help?
>
>
> Thanks,
>
> Miguel Silva

 

[islandguy]

I have the same problem after installing SP2. I verified the server is
listening on 3389 and TS is running. The only errors I'm getting in event
log are ID32 and ID59, both with source: SideBySide, and both referring to
"Dependent Assembly Microsoft.VC80.MFCLOC" stating "The referenced assembly
is not installed on your system."

I installed the fix for this error as discovered on the MSDN site:
http://www.microsoft.com/downloads/...EE-A3F9-4C13-9C99-220B62A191EE&displaylang=en
and, this didn't fix _this_ problem. I'm going to uninstall SP2 and see
what happens.

> Is the server listening on port 3389? Check from the console, by
> typing "netstat -an" (without the quotes) in a command window.
> Are there any errors or warnings in the EventLog on the server?
>
>
>> Can anyone help me.
>> After installation of SP2 for Windows Server 2003, Remote
>> Desktop on that server stop working.
>>
>> I had restart several times.
>> I even had instal update (Remote Desktop Connection (Terminal
>> Services Client 6.0) for Windows Server 2003 (KB925876)).
>> But always without sucess.
>>
>> Can anyone help?
>>
>>
>> Thanks,
>>
>> Miguel Silva

 

[Vera Noest [MVP]]

I don't think that the missing C++ libraries have anything to do
with the connection problem.
And most other posters who reported problems after SP2 or later
Windows Updates seems to have a server which is *not* listening on
port 3389, although the TS service is running.

Which error message do you get when you try to connect?
Can you connect to the server in other ways (ping, telnet to port
3389, connect to a shared folder)?
Can you rdp to localhost from the physical console of the server?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"islandguy" <islandguy@newsgroup.nospam> wrote on 23 jul 2007 in
microsoft.public.windows.terminal_services:

> I have the same problem after installing SP2. I verified the
> server is listening on 3389 and TS is running. The only errors
> I'm getting in event log are ID32 and ID59, both with source:
> SideBySide, and both referring to "Dependent Assembly
> Microsoft.VC80.MFCLOC" stating "The referenced assembly is not
> installed on your system."
>
> I installed the fix for this error as discovered on the MSDN
> site:
> http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE
> -A3F9-4C13-9C99-220B62A191EE&displaylang=en and, this didn't fix
> _this_ problem. I'm going to uninstall SP2 and see what
> happens.
>
>> Is the server listening on port 3389? Check from the console,
>> by typing "netstat -an" (without the quotes) in a command
>> window. Are there any errors or warnings in the EventLog on the
>> server?
>>
>>
>>> Can anyone help me.
>>> After installation of SP2 for Windows Server 2003, Remote
>>> Desktop on that server stop working.
>>>
>>> I had restart several times.
>>> I even had instal update (Remote Desktop Connection (Terminal
>>> Services Client 6.0) for Windows Server 2003 (KB925876)).
>>> But always without sucess.
>>>
>>> Can anyone help?
>>>
>>>
>>> Thanks,
>>>
>>> Miguel Silva

 

[islandguy]

I didn't think the C++ thing had anything to do with the remote access
problem but anyway, that error went away.

OK, I can actually RDP to (the LAN adapter on) the server from any
workstation on the local network. Thus, terminal services is working fine.
I just can't RDP in from a remote network.

The server has RRAS configured for both routing and remote access and and is
properly routing all outgoing traffic. The firewall is port forwarding
inbound port 3389 (and 1723) to the WAN adapter on the server. I cannot
telnet to the server (from the WAN side) on 3389 or 1723. I have replaced
the firewall with one bench tested and confirmed to be forwarding these
ports properly. Also, I have several other clients setup identically and
working fine, but they are all still at SP1 on W2K3.

I checked the RDP properties in Terminal Services Configuration and both
adapters are configured.

What else is there to check?


"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9976E1A345A48veranoesthemutforsse@207.46.248.16...
>I don't think that the missing C++ libraries have anything to do
> with the connection problem.
> And most other posters who reported problems after SP2 or later
> Windows Updates seems to have a server which is *not* listening on
> port 3389, although the TS service is running.
>
> Which error message do you get when you try to connect?
> Can you connect to the server in other ways (ping, telnet to port
> 3389, connect to a shared folder)?
> Can you rdp to localhost from the physical console of the server?
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "islandguy" <islandguy@newsgroup.nospam> wrote on 23 jul 2007 in
> microsoft.public.windows.terminal_services:
>
>> I have the same problem after installing SP2. I verified the
>> server is listening on 3389 and TS is running. The only errors
>> I'm getting in event log are ID32 and ID59, both with source:
>> SideBySide, and both referring to "Dependent Assembly
>> Microsoft.VC80.MFCLOC" stating "The referenced assembly is not
>> installed on your system."
>>
>> I installed the fix for this error as discovered on the MSDN
>> site:
>> http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE
>> -A3F9-4C13-9C99-220B62A191EE&displaylang=en and, this didn't fix
>> _this_ problem. I'm going to uninstall SP2 and see what
>> happens.
>>
>>> Is the server listening on port 3389? Check from the console,
>>> by typing "netstat -an" (without the quotes) in a command
>>> window. Are there any errors or warnings in the EventLog on the
>>> server?
>>>
>>>
>>>> Can anyone help me.
>>>> After installation of SP2 for Windows Server 2003, Remote
>>>> Desktop on that server stop working.
>>>>
>>>> I had restart several times.
>>>> I even had instal update (Remote Desktop Connection (Terminal
>>>> Services Client 6.0) for Windows Server 2003 (KB925876)).
>>>> But always without sucess.
>>>>
>>>> Can anyone help?
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Miguel Silva

 

[Vera Noest [MVP]]

OK, this seems to be more a networking issue than a TS issue. You
might get better help in a networking newsgroup.

That said, the only relevant change in SP2 that I know of is this:

925280 - Changes in PMTU black hole router detection in Windows
Server 2003 and in Windows Vista
http://support.microsoft.com/?kbid=925280

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"islandguy" <islandguy@newsgroup.nospam> wrote on 24 jul 2007 in
microsoft.public.windows.terminal_services:

> I didn't think the C++ thing had anything to do with the remote
> access problem but anyway, that error went away.
>
> OK, I can actually RDP to (the LAN adapter on) the server from
> any workstation on the local network. Thus, terminal services
> is working fine. I just can't RDP in from a remote network.
>
> The server has RRAS configured for both routing and remote
> access and and is properly routing all outgoing traffic. The
> firewall is port forwarding inbound port 3389 (and 1723) to the
> WAN adapter on the server. I cannot telnet to the server (from
> the WAN side) on 3389 or 1723. I have replaced the firewall
> with one bench tested and confirmed to be forwarding these ports
> properly. Also, I have several other clients setup identically
> and working fine, but they are all still at SP1 on W2K3.
>
> I checked the RDP properties in Terminal Services Configuration
> and both adapters are configured.
>
> What else is there to check?
>
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns9976E1A345A48veranoesthemutforsse@207.46.248.16...
>>I don't think that the missing C++ libraries have anything to do
>> with the connection problem.
>> And most other posters who reported problems after SP2 or later
>> Windows Updates seems to have a server which is *not* listening
>> on port 3389, although the TS service is running.
>>
>> Which error message do you get when you try to connect?
>> Can you connect to the server in other ways (ping, telnet to
>> port 3389, connect to a shared folder)?
>> Can you rdp to localhost from the physical console of the
>> server?
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "islandguy" <islandguy@newsgroup.nospam> wrote on 23 jul 2007
>> in microsoft.public.windows.terminal_services:
>>
>>> I have the same problem after installing SP2. I verified the
>>> server is listening on 3389 and TS is running. The only
>>> errors I'm getting in event log are ID32 and ID59, both with
>>> source: SideBySide, and both referring to "Dependent Assembly
>>> Microsoft.VC80.MFCLOC" stating "The referenced assembly is not
>>> installed on your system."
>>>
>>> I installed the fix for this error as discovered on the MSDN
>>> site:
>>> http://www.microsoft.com/downloads/details.aspx?familyid=32BC1B
>>> EE -A3F9-4C13-9C99-220B62A191EE&displaylang=en and, this
>>> didn't fix _this_ problem. I'm going to uninstall SP2 and
>>> see what happens.
>>>
>>>> Is the server listening on port 3389? Check from the console,
>>>> by typing "netstat -an" (without the quotes) in a command
>>>> window. Are there any errors or warnings in the EventLog on
>>>> the server?
>>>>
>>>>
>>>>> Can anyone help me.
>>>>> After installation of SP2 for Windows Server 2003, Remote
>>>>> Desktop on that server stop working.
>>>>>
>>>>> I had restart several times.
>>>>> I even had instal update (Remote Desktop Connection
>>>>> (Terminal Services Client 6.0) for Windows Server 2003
>>>>> (KB925876)). But always without sucess.
>>>>>
>>>>> Can anyone help?
>>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Miguel Silva