XP Pro Client won't accept incoming RDP Connection

Posted the following in our local NG yesterday - despite helpful advice, we
have not yet been able to resolve the issue!

Money-conscious SB Client buys 2 XP Pro clones from local PC shop, XP Pro
SP2 pre-installed with CoA on box. Client then has cheek (didn't accept our
name-brand quote) to ring us for advice on how to join these PCs to their
SBS 2003 network . With some reserve, we tell them about the
'connectcomputer" wizard. Next day another call - why can't we connect to
these boxes via RDP? We waste some time with them to confiirm that all the
basics are in place, and we promise to investigate next time they make a
service call requiring us to be onsite. Which was today.
We checked that the Remote Access box was ticked. We checked that the users
were in the right security groups. We checked their IP configs. We ran
netstat and confirmed that port 3389 was listening. We temporarily disabled
their Windows Firewall through the services snap-in. We ran PortqryUI. We
reset the TCP stack. We reset the local security settings. All came up OK.
Outbound RDP is fine...

Checked Event Logs - nothing of note but then we don't know what we should
be looking for so it's possible we might have missed some SCM message. When
trying to connect from the SBS 2003 server, we do get the message from IE -
"connectivity to the remote computer could not be established..." (Very
helpful.)

Suggestions from local NG members - :

The users have local admin status and there are no obvious errors except
that which I posted from IE, Both boxes are running SP2 - did try SP3 in
the vain hope it might "fix" the problem but it didn't, so it was
uninstalled...

I did try to Telnet to port 3389 from another known-good XP SP2 PC, and
received a window with a flashing white cursor
on a black background - I think this confirms 3389 is listening and open?

These boxes do run Autocad with a fancy graphics card feeding 28" LCD
monitors. Might be worth trying a lower res here?

Another suggestion was to remove them from the domain and then rerun the
ConnectComputer wizard - don't really want to remove the boxes from the
domain as this will require us to setup a "local" user to save the domain
users' existing domain profiles to, and they're huge... But if needs to be
done...

Any further suggestions out there?

Regards
Norm Hughes

I think your last option is the best place to start...you can always blow
away the local user profile after reconnected to the domain. There is no
guarantee that they joined them with connectcomputer, even after you told
them

I also agree about the video resolution.

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-...7269967&sr=8-1

------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"Ex-Engineer" <ex-engineerNOSPAM@hotmail.com> wrote in message
news:u8xPi2DGJHA.6052@TK2MSFTNGP04.phx.gbl...
> Posted the following in our local NG yesterday - despite helpful advice,
> we have not yet been able to resolve the issue!
>
> Money-conscious SB Client buys 2 XP Pro clones from local PC shop, XP Pro
> SP2 pre-installed with CoA on box. Client then has cheek (didn't accept
> our name-brand quote) to ring us for advice on how to join these PCs to
> their SBS 2003 network . With some reserve, we tell them about the
> 'connectcomputer" wizard. Next day another call - why can't we connect to
> these boxes via RDP? We waste some time with them to confiirm that all
> the basics are in place, and we promise to investigate next time they make
> a service call requiring us to be onsite. Which was today.
> We checked that the Remote Access box was ticked. We checked that the
> users were in the right security groups. We checked their IP configs. We
> ran netstat and confirmed that port 3389 was listening. We temporarily
> disabled their Windows Firewall through the services snap-in. We ran
> PortqryUI. We reset the TCP stack. We reset the local security settings.
> All came up OK. Outbound RDP is fine...
>
> Checked Event Logs - nothing of note but then we don't know what we should
> be looking for so it's possible we might have missed some SCM message.
> When trying to connect from the SBS 2003 server, we do get the message
> from IE - "connectivity to the remote computer could not be
> established..." (Very helpful.)
>
> Suggestions from local NG members - :
>
> The users have local admin status and there are no obvious errors except
> that which I posted from IE, Both boxes are running SP2 - did try SP3 in
> the vain hope it might "fix" the problem but it didn't, so it was
> uninstalled...
>
> I did try to Telnet to port 3389 from another known-good XP SP2 PC, and
> received a window with a flashing white cursor
> on a black background - I think this confirms 3389 is listening and open?
>
> These boxes do run Autocad with a fancy graphics card feeding 28" LCD
> monitors. Might be worth trying a lower res here?
>
> Another suggestion was to remove them from the domain and then rerun the
> ConnectComputer wizard - don't really want to remove the boxes from the
> domain as this will require us to setup a "local" user to save the domain
> users' existing domain profiles to, and they're huge... But if needs to be
> done...
>
> Any further suggestions out there?
>
> Regards
> Norm Hughes
>
>
>

A couple of things:

1) Are you sure these are XP Pro machines? XP Home allows remote
ASSISTANCE, but not remote DESKTOP. Very different usage, and would explain
the listening port.

2) You say you made sure the "remote access" checkbox is ticked. But on an
XP pro box, there are two remote checkboxes. right-click
computer->properties->remote tab
On that tab exists TWO checkboxes. One for remote assistance, the other for
remote desktop. NEITHER is labeled "remote access" so your post was,
unfortunately, not clear in this regard...so just wanted to clarify.

Also, just a few other comments in general:

1) You can safely remove the computer from the domain. The user's profiles
will remain on the machine until manually deleted. I shuffle computers on
and off domains all the time as part of my test lab, so trust me, it works.

2) I doubt removing and rejoining the computer on the domain will fix the
problem. Although it is possible that there is a group policy that is
misconfiguring your firewall, if you were able to DISABLE the firewall then
this GP would never come into play. And, yes, there is also a GP setting to
disallow disabling of the firewall, but that is clearly evident on the
firewall configuration screen...it TELLS you it cannot be disabled. So
you'd know if that was an issue.

3) I'd do ALL testing with the client firewall disabled until you get it to
work. Then you can start looking for firewall rules and exceptions. Are
you sure no third-party firewalls are installed?

-Cliff


"Ex-Engineer" <ex-engineerNOSPAM@hotmail.com> wrote in message
news:u8xPi2DGJHA.6052@TK2MSFTNGP04.phx.gbl...
> Posted the following in our local NG yesterday - despite helpful advice,
> we have not yet been able to resolve the issue!
>
> Money-conscious SB Client buys 2 XP Pro clones from local PC shop, XP Pro
> SP2 pre-installed with CoA on box. Client then has cheek (didn't accept
> our name-brand quote) to ring us for advice on how to join these PCs to
> their SBS 2003 network . With some reserve, we tell them about the
> 'connectcomputer" wizard. Next day another call - why can't we connect to
> these boxes via RDP? We waste some time with them to confiirm that all
> the basics are in place, and we promise to investigate next time they make
> a service call requiring us to be onsite. Which was today.
> We checked that the Remote Access box was ticked. We checked that the
> users were in the right security groups. We checked their IP configs. We
> ran netstat and confirmed that port 3389 was listening. We temporarily
> disabled their Windows Firewall through the services snap-in. We ran
> PortqryUI. We reset the TCP stack. We reset the local security settings.
> All came up OK. Outbound RDP is fine...
>
> Checked Event Logs - nothing of note but then we don't know what we should
> be looking for so it's possible we might have missed some SCM message.
> When trying to connect from the SBS 2003 server, we do get the message
> from IE - "connectivity to the remote computer could not be
> established..." (Very helpful.)
>
> Suggestions from local NG members - :
>
> The users have local admin status and there are no obvious errors except
> that which I posted from IE, Both boxes are running SP2 - did try SP3 in
> the vain hope it might "fix" the problem but it didn't, so it was
> uninstalled...
>
> I did try to Telnet to port 3389 from another known-good XP SP2 PC, and
> received a window with a flashing white cursor
> on a black background - I think this confirms 3389 is listening and open?
>
> These boxes do run Autocad with a fancy graphics card feeding 28" LCD
> monitors. Might be worth trying a lower res here?
>
> Another suggestion was to remove them from the domain and then rerun the
> ConnectComputer wizard - don't really want to remove the boxes from the
> domain as this will require us to setup a "local" user to save the domain
> users' existing domain profiles to, and they're huge... But if needs to be
> done...
>
> Any further suggestions out there?
>
> Regards
> Norm Hughes
>
>
>

Oops! I guess my advice conflicts with Chris's advice. But as my other
post indicated, removing the computer from the domain won't kill domain
profiles, so it should be a non-issue. Certainly won't *hurt* to go through
the process. :)

-Cliff


"Cris Hanna [SBS - MVP]" <crisnospamhanna@cpunospamservices.net> wrote in
message news:Oz#8T7DGJHA.5572@TK2MSFTNGP03.phx.gbl...
> I think your last option is the best place to start...you can always blow
> away the local user profile after reconnected to the domain. There is no
> guarantee that they joined them with connectcomputer, even after you told
> them
>
> I also agree about the video resolution.
>
> --
> Cris Hanna [SBS - MVP]
> Co-Author, Windows Small Business Server 2008 Unleashed
> http://www.amazon.com/Windows-Small-...7269967&sr=8-1
>
> ------------------------------------
> MVPs do not work for Microsoft
> Please do not submit questions directly to me.
>
> "Ex-Engineer" <ex-engineerNOSPAM@hotmail.com> wrote in message
> news:u8xPi2DGJHA.6052@TK2MSFTNGP04.phx.gbl...
>> Posted the following in our local NG yesterday - despite helpful advice,
>> we have not yet been able to resolve the issue!
>>
>> Money-conscious SB Client buys 2 XP Pro clones from local PC shop, XP Pro
>> SP2 pre-installed with CoA on box. Client then has cheek (didn't accept
>> our name-brand quote) to ring us for advice on how to join these PCs to
>> their SBS 2003 network . With some reserve, we tell them about the
>> 'connectcomputer" wizard. Next day another call - why can't we connect to
>> these boxes via RDP? We waste some time with them to confiirm that all
>> the basics are in place, and we promise to investigate next time they
>> make a service call requiring us to be onsite. Which was today.
>> We checked that the Remote Access box was ticked. We checked that the
>> users were in the right security groups. We checked their IP configs. We
>> ran netstat and confirmed that port 3389 was listening. We temporarily
>> disabled their Windows Firewall through the services snap-in. We ran
>> PortqryUI. We reset the TCP stack. We reset the local security settings.
>> All came up OK. Outbound RDP is fine...
>>
>> Checked Event Logs - nothing of note but then we don't know what we
>> should be looking for so it's possible we might have missed some SCM
>> message. When trying to connect from the SBS 2003 server, we do get the
>> message from IE - "connectivity to the remote computer could not be
>> established..." (Very helpful.)
>>
>> Suggestions from local NG members - :
>>
>> The users have local admin status and there are no obvious errors except
>> that which I posted from IE, Both boxes are running SP2 - did try SP3 in
>> the vain hope it might "fix" the problem but it didn't, so it was
>> uninstalled...
>>
>> I did try to Telnet to port 3389 from another known-good XP SP2 PC, and
>> received a window with a flashing white cursor
>> on a black background - I think this confirms 3389 is listening and open?
>>
>> These boxes do run Autocad with a fancy graphics card feeding 28" LCD
>> monitors. Might be worth trying a lower res here?
>>
>> Another suggestion was to remove them from the domain and then rerun the
>> ConnectComputer wizard - don't really want to remove the boxes from the
>> domain as this will require us to setup a "local" user to save the domain
>> users' existing domain profiles to, and they're huge... But if needs to
>> be done...
>>
>> Any further suggestions out there?
>>
>> Regards
>> Norm Hughes
>>
>>
>>
>

Winver from a command prompt.

Start run mstsc and then connect from the SBS to the workstation.
Eliminate any RWW web page fun.

What workstation antivirus?

What resolution are you trying to connect to the desktop with? At
least you have that option when you use mstsc/rdp.

On Tue, 16 Sep 2008 15:03:15 -0600, "Cliff Galiher"
<cgaliher@gmail.com> wrote:

>A couple of things:
>
>1) Are you sure these are XP Pro machines? XP Home allows remote
>ASSISTANCE, but not remote DESKTOP. Very different usage, and would explain
>the listening port.
>
>2) You say you made sure the "remote access" checkbox is ticked. But on an
>XP pro box, there are two remote checkboxes. right-click
>computer->properties->remote tab
>On that tab exists TWO checkboxes. One for remote assistance, the other for
>remote desktop. NEITHER is labeled "remote access" so your post was,
>unfortunately, not clear in this regard...so just wanted to clarify.
>
>Also, just a few other comments in general:
>
>1) You can safely remove the computer from the domain. The user's profiles
>will remain on the machine until manually deleted. I shuffle computers on
>and off domains all the time as part of my test lab, so trust me, it works.
>
>2) I doubt removing and rejoining the computer on the domain will fix the
>problem. Although it is possible that there is a group policy that is
>misconfiguring your firewall, if you were able to DISABLE the firewall then
>this GP would never come into play. And, yes, there is also a GP setting to
>disallow disabling of the firewall, but that is clearly evident on the
>firewall configuration screen...it TELLS you it cannot be disabled. So
>you'd know if that was an issue.
>
>3) I'd do ALL testing with the client firewall disabled until you get it to
>work. Then you can start looking for firewall rules and exceptions. Are
>you sure no third-party firewalls are installed?
>
>-Cliff
>
>
>"Ex-Engineer" <ex-engineerNOSPAM@hotmail.com> wrote in message
>news:u8xPi2DGJHA.6052@TK2MSFTNGP04.phx.gbl...
>> Posted the following in our local NG yesterday - despite helpful advice,
>> we have not yet been able to resolve the issue!
>>
>> Money-conscious SB Client buys 2 XP Pro clones from local PC shop, XP Pro
>> SP2 pre-installed with CoA on box. Client then has cheek (didn't accept
>> our name-brand quote) to ring us for advice on how to join these PCs to
>> their SBS 2003 network . With some reserve, we tell them about the
>> 'connectcomputer" wizard. Next day another call - why can't we connect to
>> these boxes via RDP? We waste some time with them to confiirm that all
>> the basics are in place, and we promise to investigate next time they make
>> a service call requiring us to be onsite. Which was today.
>> We checked that the Remote Access box was ticked. We checked that the
>> users were in the right security groups. We checked their IP configs. We
>> ran netstat and confirmed that port 3389 was listening. We temporarily
>> disabled their Windows Firewall through the services snap-in. We ran
>> PortqryUI. We reset the TCP stack. We reset the local security settings.
>> All came up OK. Outbound RDP is fine...
>>
>> Checked Event Logs - nothing of note but then we don't know what we should
>> be looking for so it's possible we might have missed some SCM message.
>> When trying to connect from the SBS 2003 server, we do get the message
>> from IE - "connectivity to the remote computer could not be
>> established..." (Very helpful.)
>>
>> Suggestions from local NG members - :
>>
>> The users have local admin status and there are no obvious errors except
>> that which I posted from IE, Both boxes are running SP2 - did try SP3 in
>> the vain hope it might "fix" the problem but it didn't, so it was
>> uninstalled...
>>
>> I did try to Telnet to port 3389 from another known-good XP SP2 PC, and
>> received a window with a flashing white cursor
>> on a black background - I think this confirms 3389 is listening and open?
>>
>> These boxes do run Autocad with a fancy graphics card feeding 28" LCD
>> monitors. Might be worth trying a lower res here?
>>
>> Another suggestion was to remove them from the domain and then rerun the
>> ConnectComputer wizard - don't really want to remove the boxes from the
>> domain as this will require us to setup a "local" user to save the domain
>> users' existing domain profiles to, and they're huge... But if needs to be
>> done...
>>
>> Any further suggestions out there?
>>
>> Regards
>> Norm Hughes
>>
>>
>>
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive...A/default.aspx

Hello Norm,

Thank you for posting here.

According to your description, I understand that:

The inbound RDP connection fails on the new Windows XP client computer.

If I have misunderstood the problem, please don't hesitate to let me know.

Suggestions:
===============
First of all, I'd like to know whether the issue happens on both Windows XP
SP2 new computer. If yes, you can narrow down the issue to those two
computer specific. You mentioned that these XP Pro SP2 are pre-installed
with CoA on box and there should be some 3-party software (firewall?)
installed . To verify that, you may check how it works with clean boot. To
do that:

1) Run MSCONFIG.EXE. (MSCONFIG is a built-in tool for Windows XP\2003
systems.)

2) In the Services tab, click "Hide All Microsoft Services" and click
"Disable All". Please note that the Exchange services could be marked as
non-Microsoft. Please do not disable those services.

3) In the Startup tab, click "Disable All". Click OK. (This will
temporarily prevent third-party programs from running automatically during
start-up.)

4) Restart the computer. Does the problem still persist?

If the problem does not occur, it indicates that the problem is related to
one application or service we have disabled. You can use the MSCONFIG tool
again to re-enable the disabled item one by one to find out the culprit.

If the issue persists, please try to capture the network trace on the
problematic Windows XP client to indentify whether the remote desktop
package is blocked by the network device. You can get the network monitor
from the following link and install it on the SBS server.

Download the NetMon3.1 from the following link:
http://www.microsoft.com/downloads/d...59d-f4d8-4213-
8d17-2f6dde7d7aac&DisplayLang=en

1) Install the network monitor on the problematic Windows XP client and a
test source computer.

2) Start the capture and try RDP to the problematic computer.

2) Once the error is prompted, stop the captures and save the network trace
files to verify whether the client receives the RDP request package.

More information please refer to:

886209 Users cannot connect to remote desktops by using the Windows Small
Business Server 2003 Remote Web Workplace
http://support.microsoft.com/default...b;EN-US;886209


For the further investigation, please answer the following questions:
===============
1. How it works if you try to connect a problematic computer with RDP
client (mstsc)? What is the exact error message if connecting fails?

Hope it helps. If you have any questions or concerns, please do not
hesitate to let me know.


Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Norm,
You mentioned fancy graphic card. Are the systems using an Nvidia graphic
chipset and is the driver very recent? Had the same issue which was resolved
by going back to version forceware 162.18. None of the later drivers (all
WHQL certified ???) worked. Look for RDP.dll failed load in event logs.

Cheers,
ColinJ

"Ex-Engineer" wrote:

> Posted the following in our local NG yesterday - despite helpful advice, we
> have not yet been able to resolve the issue!
>
> Money-conscious SB Client buys 2 XP Pro clones from local PC shop, XP Pro
> SP2 pre-installed with CoA on box. Client then has cheek (didn't accept our
> name-brand quote) to ring us for advice on how to join these PCs to their
> SBS 2003 network . With some reserve, we tell them about the
> 'connectcomputer" wizard. Next day another call - why can't we connect to
> these boxes via RDP? We waste some time with them to confiirm that all the
> basics are in place, and we promise to investigate next time they make a
> service call requiring us to be onsite. Which was today.
> We checked that the Remote Access box was ticked. We checked that the users
> were in the right security groups. We checked their IP configs. We ran
> netstat and confirmed that port 3389 was listening. We temporarily disabled
> their Windows Firewall through the services snap-in. We ran PortqryUI. We
> reset the TCP stack. We reset the local security settings. All came up OK.
> Outbound RDP is fine...
>
> Checked Event Logs - nothing of note but then we don't know what we should
> be looking for so it's possible we might have missed some SCM message. When
> trying to connect from the SBS 2003 server, we do get the message from IE -
> "connectivity to the remote computer could not be established..." (Very
> helpful.)
>
> Suggestions from local NG members - :
>
> The users have local admin status and there are no obvious errors except
> that which I posted from IE, Both boxes are running SP2 - did try SP3 in
> the vain hope it might "fix" the problem but it didn't, so it was
> uninstalled...
>
> I did try to Telnet to port 3389 from another known-good XP SP2 PC, and
> received a window with a flashing white cursor
> on a black background - I think this confirms 3389 is listening and open?
>
> These boxes do run Autocad with a fancy graphics card feeding 28" LCD
> monitors. Might be worth trying a lower res here?
>
> Another suggestion was to remove them from the domain and then rerun the
> ConnectComputer wizard - don't really want to remove the boxes from the
> domain as this will require us to setup a "local" user to save the domain
> users' existing domain profiles to, and they're huge... But if needs to be
> done...
>
> Any further suggestions out there?
>
> Regards
> Norm Hughes
>
>
>
>

To all who have offered suggestions, apologies for my tardy reply - getting
to the site poses some travel and time restraints.
Now we have tried everything suggested with the exception of the Netmon
trace (suggested by Miles) and substitutng a different graphics card
(suggested by ColinJ.au) - both I hope to do this week.
I will post back regardless of outcome - and thanks again for all Ideas!

Cheers
Norm Hughes


"ColinJ.au" <ColinJau@discussions.microsoft.com> wrote in message
news:8AB43CBC-3675-4BC1-B9BD-401DF451CC8C@microsoft.com...
> Hi Norm,
> You mentioned fancy graphic card. Are the systems using an Nvidia graphic
> chipset and is the driver very recent? Had the same issue which was
> resolved
> by going back to version forceware 162.18. None of the later drivers (all
> WHQL certified ???) worked. Look for RDP.dll failed load in event logs.
>
> Cheers,
> ColinJ
>
> "Ex-Engineer" wrote:
>
>> Posted the following in our local NG yesterday - despite helpful advice,
>> we
>> have not yet been able to resolve the issue!
>>
>> Money-conscious SB Client buys 2 XP Pro clones from local PC shop, XP Pro
>> SP2 pre-installed with CoA on box. Client then has cheek (didn't accept
>> our
>> name-brand quote) to ring us for advice on how to join these PCs to their
>> SBS 2003 network . With some reserve, we tell them about the
>> 'connectcomputer" wizard. Next day another call - why can't we connect to
>> these boxes via RDP? We waste some time with them to confiirm that all
>> the
>> basics are in place, and we promise to investigate next time they make a
>> service call requiring us to be onsite. Which was today.
>> We checked that the Remote Access box was ticked. We checked that the
>> users
>> were in the right security groups. We checked their IP configs. We ran
>> netstat and confirmed that port 3389 was listening. We temporarily
>> disabled
>> their Windows Firewall through the services snap-in. We ran PortqryUI. We
>> reset the TCP stack. We reset the local security settings. All came up
>> OK.
>> Outbound RDP is fine...
>>
>> Checked Event Logs - nothing of note but then we don't know what we
>> should
>> be looking for so it's possible we might have missed some SCM message.
>> When
>> trying to connect from the SBS 2003 server, we do get the message from
>> IE -
>> "connectivity to the remote computer could not be established..." (Very
>> helpful.)
>>
>> Suggestions from local NG members - :
>>
>> The users have local admin status and there are no obvious errors except
>> that which I posted from IE, Both boxes are running SP2 - did try SP3 in
>> the vain hope it might "fix" the problem but it didn't, so it was
>> uninstalled...
>>
>> I did try to Telnet to port 3389 from another known-good XP SP2 PC, and
>> received a window with a flashing white cursor
>> on a black background - I think this confirms 3389 is listening and open?
>>
>> These boxes do run Autocad with a fancy graphics card feeding 28" LCD
>> monitors. Might be worth trying a lower res here?
>>
>> Another suggestion was to remove them from the domain and then rerun the
>> ConnectComputer wizard - don't really want to remove the boxes from the
>> domain as this will require us to setup a "local" user to save the domain
>> users' existing domain profiles to, and they're huge... But if needs to
>> be
>> done...
>>
>> Any further suggestions out there?
>>
>> Regards
>> Norm Hughes
>>
>>
>>
>>

Hello Norm,

Please take your time to have the test. If there is any update on the
issue, please please do not hesitate to let us know.


Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.