No Remote Desktop After SP2 Install

  • Thread starter Thread starter Nick Goodall
  • Start date Start date
In this case, file a support incident. SP2 specific problems are
generally free:
http://support.microsoft.com/default.aspx?scid=fh;en-us;Prodoffer80

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
From my experiences here I can add the following:

My laptop has an Intel CPU and a Nvidia graphice card. Since the install of
SP2 I can connect to any of our servers running Intel CPUs, all of which have
ATI graphics, however the one server we have with an AMD CPU and Nvidia card
I can no longer connect to. This may just be a coincidence but this has only
been the case since the SP2 install and if I remove SP2 I can connect to the
AMD server again.

As I can connect to the other servers it would appear that the mstsc
connection is being allowed through the XP firewall but I cannot see why the
server hardware should be relevant.
 
Interesting. This shouldn't happen for most folks. I've installed SP2 on a
number of machines--a dozen or so, via Remote Desktop and haven't seen this
issue. These machines in the main had the SP1 firewall in place with RD
opened.
 
I just wanted to let you know that I had the same problem. All the othe
XP boxes that had XP2 installed were fine except mine. The Admins box
how nice. During my searches on the web I could not find any fix fo
this. I did find someone talking about Concurrent users not in th
final build. But he saved some dll files from an older build tha
allowed for this option. So I went ahead and downloaded the zip fil
and followed the directions. My was not working so why not try it. Onc
I finished installing the new Termserv files I rebooted and tried it.
was able to connect on the first try. I am posting this here to allo
others to try to see if this fixes your problem. Here is the link fo
the files (You will have to register in order to get them).

http://forum.osnn.net/showthread.php?t=39878

Happy Computing and good luck.

Nick said:
*I was just using the default port of 3389, and it was
definatly allowed in the firewall.

I have also now tried changing it all to port 3390 and
that mode no difference. I can connect to the server from
my brothers pc (XP with RTM SP2) using port 3390 (and
default if set) but not from my system which had just the
same version of windows and same SP installed.

Nick
-----Original Message-----
You using a difrent port other than the 3389? If so you need to allow that
through firewall. That one of the first things I had to fix after
installing SP2.


news:[email protected]...
Click to expand...
connect.[vbcol=seagreen]
and[vbcol=seagreen]
Sliptreamed[vbcol=seagreen]
remote[vbcol=seagreen]


.
Click to expand...
Click to expand...


-
parrz
 
One thing that I noted - if you enable Remote Desktop via the Group
Policy method, it will not automatically enable the port in the ICF...
Weird bug...

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
The port isn't opened automagically, even if you've enabled the feature "by
hand."

My thinking about the reasoning behind this is that the ICF was designed to
be used as an Internet facing firewall, originally, and it is very
reasonable to think that folks might want RD enabled within a LAN, but not
accessable from the Internet--so opening it in the ICF remained a manual
step.
 
Thanks- very nice link!

Jeffrey Randow (MVP) said:
Actually, file a support incident. SP2 specific problems are
generally free:
http://support.microsoft.com/default.aspx?scid=fh;en-us;Prodoffer80

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
Click to expand...
 
Yep.. I asked for clarification as there are many new SP2-specific
issues.

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
That link impresses me more than their providing free CD's--there's a lot
more cost involved in providing that support than pressing and mailing a few
(10's of thousands?) CD's
 
Same here, works on my AMD/Nvidia laptop but not on my Intel/Nvidia
desktop. Just connects for a split second and disconnects, no error
messages nothing.
 
Success. I called MS service yesterday - they had me use the "msconfig"
application (start menu - run - msconfig) to disable nonessential
services and tray items, then (reboot and) install SP2. While there are
a couple of other strange things happening, this advice fixed the
problem with the remote desktop (server) and I will keep SP2 installed
this time.

Good luck all
 
Jeffrey said:
*I'll send this to the TS team at MS to see if they are seeing tech
support incidents on this, but I haven't been able to reproduce this
on ten machines I have tried...

Getting this solved will involve someone who has this issue to ope
up
a support incident with either MS or your OEM. However, this ma
cost
$$$...
*
Click to expand...

Just for the record, I'm having problems logging into an XP lapto
since installing SP2. When I contacted the company my company buy
computers from, they said they have seen this problem a lot, the onl
workaround is uninstalling SP2, and they are recommending that no on
installs SP2. This is very frustrating. Oh well, good-bye SP2


-
bjudso
 
Terrific--glad they were able to help, and glad you called.

Now it'd even be nicer to know through triage which service was really
causing the conflict, of course!
 
Thanks Bill,

The exact problem we were having, was that one of our XP Pro users couldn't
RDP to a particular customer's Windows 2000 SP3 Server running Terminal
Services in 'Application' mode, after installing SP2. Other users (1 with
Windows 2000 Pro SP4 and another with XP Pro SP1 didn't have any problem
connecting.

Jerry
 
I think that I've seen other messages tying this behavior into the SP2
installation, so you are probably correct in connecting it to SP2.

I need to remember to ask what the host is when these "can't connect after
SP2" messages come up--I tend to forget about TS licensing issues since I
mainly use TS in administrative mode, or work between XP machines.
 
I've been following this thread hoping to find an answer to this
problem.

The host is XP running XP-SP1.
MY home network consists of a Intel P4 1.7 running XP-SP1, which can
connect to the host no problems.
And a brand new Intel P4 3.2 running XP-SP2, which is connecting, then
disconnecting. One thing that I have not seen mentioned, is that I can
connect once (briefly) to a host. After that it never reconnects. The
other point is, that I can access both the host using
'\\ip-add\sharename' syntax with no problems.

I assume that everyone is using someform of VPN, could it be this
which is been affected when it used with remote desktop.

I'm hoping that someonme has the answer....

Regards

Mike
 
I've spoken to Microsoft support, and they sent me a hotfix to try.
'Q884020 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 '

This made no difference!

They have suggested that I uninstall SP2, until a fix is posted :(

Anyone got any suggestions, PLEASE?

Mike
 
Back
Top