RE: RWW not working on some client desktops

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello Gordon,

Merry Christmas and Happy New Years!

Thank you for posting back and keeping us updated!

>From your reply, I understand that all domain clients cannot RWW -> RDP to
specific domain workstations. If I have misunderstood your issue, please
let me know.

I have performed a lot of research on your issue, please see my
suggestions:

1. On the problematic client workstation, go to Control Panel ->
Administrative Tools -> Local Security Policy.

2. Then under Local Policies go to User Rights Management. In User Rights
Management look for "Allow logon through terminal services", double click
and make sure to add the appropriate groups (which are granted Remote
Desktop Users and Administrators by default.). Also make sure that in "Deny
logon through terminal services" that the same groups are not listed.

3. Make sure that the user account which is used to connect to the client
computer is in the Remote Desktop Users group.

For more information, please see following KB articles:

886620 "The local policy does not permit you to logon interactively" error
http://support.microsoft.com/?id=886620

289289 Remote desktop connection "The local policy of this system does not
http://support.microsoft.com/?id=289289

Please take your time to perform the steps. If you have any updates, please
feel free to let me know. I am looking forward to hearing from you!

Best regards,

Brandy Nee

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
>Thread-Topic: RWW not working on some client desktops
>thread-index: AcYG29H5OowGlq/oQ7aqRsI3M22Xdw==
>X-WBNR-Posting-Host: 202.156.6.36
>From: "=?Utf-8?B?R29yZG9uIExhbWI=?=" <GordonLamb@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <907BEB78-A217-44A3-BB04-669E48A666B7@xxxxxxxxxxxxx>
<Ysnh$lG$FHA.3764@xxxxxxxxxxxxxxxxxxxxx>
<FB74917D-72EA-4948-95EC-26C3462E9F3E@xxxxxxxxxxxxx>
<dhQzMKL$FHA.832@xxxxxxxxxxxxxxxxxxxxx>
<50FE402C-B2D4-42DF-A3C6-C4C5A096F727@xxxxxxxxxxxxx>
<GNUbrV7$FHA.1236@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: RWW not working on some client desktops
>Date: Thu, 22 Dec 2005 01:41:02 -0800
>Lines: 456
>Message-ID: <9F94F855-326A-4F71-BF67-A69499B25813@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:231934
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi Brandy,
>
>sorry for the delay, been playing with sick exchange servers.....
>
>Replies in line
>
>""Brandy Nee [MSFT]"" wrote:
>
>> 1. This issue may occur if a process that is running on the SBS-based
>> computer is listening on TCP port 4125. On a SBS-based computer, the
Remote
>> Web Workplace uses TCP port 4125 for its remote desktop feature.
Sometimes,
>> another process may use TCP port 4125 before RWW can claim port 4125. If
>> another process is listening on this port, SBS Server cannot respond to
the
>> remote computer's connection request.
>>
>> For more detail information and how to troubleshoot the issue, please
see:
>>
>> 886209 Users cannot connect to remote desktops by using the Windows Small
>> http://support.microsoft.com/?id=886209
>
>I ran the netstat and nothing appears to be listening on 4125.
>
>The following is the output from the netstat command.
>
>Active Connections
>
> Proto Local Address Foreign Address State PID
> TCP 0.0.0.0:25 0.0.0.0:0 LISTENING 1308
> TCP 0.0.0.0:42 0.0.0.0:0 LISTENING 2820
> TCP 0.0.0.0:53 0.0.0.0:0 LISTENING 1140
> TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 3672
> TCP 0.0.0.0:88 0.0.0.0:0 LISTENING 496
> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 844
> TCP 0.0.0.0:389 0.0.0.0:0 LISTENING 496
> TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 3672
> TCP 0.0.0.0:444 0.0.0.0:0 LISTENING 3672
> TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
> TCP 0.0.0.0:464 0.0.0.0:0 LISTENING 496
> TCP 0.0.0.0:593 0.0.0.0:0 LISTENING 844
> TCP 0.0.0.0:636 0.0.0.0:0 LISTENING 496
> TCP 0.0.0.0:691 0.0.0.0:0 LISTENING 1308
> TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING 496
> TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING 496
> TCP 0.0.0.0:1028 0.0.0.0:0 LISTENING 1140
> TCP 0.0.0.0:1031 0.0.0.0:0 LISTENING 1308
> TCP 0.0.0.0:1032 0.0.0.0:0 LISTENING 1308
> TCP 0.0.0.0:1033 0.0.0.0:0 LISTENING 1308
> TCP 0.0.0.0:1034 0.0.0.0:0 LISTENING 1308
> TCP 0.0.0.0:1035 0.0.0.0:0 LISTENING 1308
> TCP 0.0.0.0:1037 0.0.0.0:0 LISTENING 2088
> TCP 0.0.0.0:1038 0.0.0.0:0 LISTENING 2820
> TCP 0.0.0.0:1039 0.0.0.0:0 LISTENING 3028
> TCP 0.0.0.0:1041 0.0.0.0:0 LISTENING 4056
> TCP 0.0.0.0:1723 0.0.0.0:0 LISTENING 4
> TCP 0.0.0.0:3268 0.0.0.0:0 LISTENING 496
> TCP 0.0.0.0:3269 0.0.0.0:0 LISTENING 496
> TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 956
> TCP 0.0.0.0:5225 0.0.0.0:0 LISTENING 4572
> TCP 0.0.0.0:5226 0.0.0.0:0 LISTENING 4572
> TCP 0.0.0.0:5900 0.0.0.0:0 LISTENING 2900
> TCP 0.0.0.0:6001 0.0.0.0:0 LISTENING 4056
> TCP 0.0.0.0:6002 0.0.0.0:0 LISTENING 3028
> TCP 0.0.0.0:6004 0.0.0.0:0 LISTENING 496
> TCP 0.0.0.0:7375 0.0.0.0:0 LISTENING 3672
> TCP 0.0.0.0:7402 0.0.0.0:0 LISTENING 1376
> TCP 0.0.0.0:7403 0.0.0.0:0 LISTENING 1376
> TCP 0.0.0.0:8008 0.0.0.0:0 LISTENING 4572
> TCP 0.0.0.0:8081 0.0.0.0:0 LISTENING 3672
> TCP 0.0.0.0:8530 0.0.0.0:0 LISTENING 3672
> TCP 0.0.0.0:8531 0.0.0.0:0 LISTENING 3672
> TCP 10.1.0.10:135 10.1.0.10:2839 ESTABLISHED 844
> TCP 10.1.0.10:139 0.0.0.0:0 LISTENING 4
> TCP 10.1.0.10:139 10.1.0.63:1083 ESTABLISHED 4
> TCP 10.1.0.10:389 10.1.0.10:1125 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1136 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1137 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1138 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1140 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1143 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1144 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1145 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1146 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1147 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1148 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1149 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1166 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1167 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1170 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1174 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1176 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1178 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1179 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:1182 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:2050 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:2306 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:2368 ESTABLISHED 496
> TCP 10.1.0.10:389 10.1.0.10:2844 TIME_WAIT 0
> TCP 10.1.0.10:389 10.1.0.10:2845 TIME_WAIT 0
> TCP 10.1.0.10:445 10.1.0.54:1086 ESTABLISHED 4
> TCP 10.1.0.10:691 10.1.0.10:1168 ESTABLISHED 1308
> TCP 10.1.0.10:691 10.1.0.10:1169 ESTABLISHED 1308
> TCP 10.1.0.10:691 10.1.0.10:1175 ESTABLISHED 1308
> TCP 10.1.0.10:1025 10.1.0.10:1127 ESTABLISHED 496
> TCP 10.1.0.10:1025 10.1.0.10:1142 ESTABLISHED 496
> TCP 10.1.0.10:1025 10.1.0.10:1209 ESTABLISHED 496
> TCP 10.1.0.10:1025 10.1.0.10:1400 ESTABLISHED 496
> TCP 10.1.0.10:1090 10.1.0.10:3268 ESTABLISHED 1308
> TCP 10.1.0.10:1125 10.1.0.10:389 ESTABLISHED 2088
> TCP 10.1.0.10:1127 10.1.0.10:1025 ESTABLISHED 2088
> TCP 10.1.0.10:1133 10.1.0.10:389 CLOSE_WAIT 3028
> TCP 10.1.0.10:1136 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1137 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1138 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1140 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1142 10.1.0.10:1025 ESTABLISHED 3028
> TCP 10.1.0.10:1143 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1144 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1145 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1146 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1147 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1148 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1149 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:1150 10.1.0.10:389 CLOSE_WAIT 3028
> TCP 10.1.0.10:1151 10.1.0.10:389 CLOSE_WAIT 3028
> TCP 10.1.0.10:1152 10.1.0.10:389 CLOSE_WAIT 3028
> TCP 10.1.0.10:1153 10.1.0.10:389 CLOSE_WAIT 3028
> TCP 10.1.0.10:1154 10.1.0.10:3268 CLOSE_WAIT 3028
> TCP 10.1.0.10:1155 10.1.0.10:389 CLOSE_WAIT 3028
> TCP 10.1.0.10:1156 10.1.0.10:3268 CLOSE_WAIT 3028
> TCP 10.1.0.10:1163 10.1.0.10:3268 ESTABLISHED 4056
> TCP 10.1.0.10:1165 10.1.0.10:389 CLOSE_WAIT 4056
> TCP 10.1.0.10:1166 10.1.0.10:389 ESTABLISHED 4056
> TCP 10.1.0.10:1167 10.1.0.10:389 ESTABLISHED 4056
> TCP 10.1.0.10:1168 10.1.0.10:691 ESTABLISHED 4056
> TCP 10.1.0.10:1169 10.1.0.10:691 ESTABLISHED 1308
> TCP 10.1.0.10:1170 10.1.0.10:389 ESTABLISHED 1308
> TCP 10.1.0.10:1173 10.1.0.10:3268 ESTABLISHED 2524
> TCP 10.1.0.10:1174 10.1.0.10:389 ESTABLISHED 2524
> TCP 10.1.0.10:1175 10.1.0.10:691 ESTABLISHED 2524
> TCP 10.1.0.10:1176 10.1.0.10:389 ESTABLISHED 4056
> TCP 10.1.0.10:1178 10.1.0.10:389 ESTABLISHED 1308
> TCP 10.1.0.10:1179 10.1.0.10:389 ESTABLISHED 1308
> TCP 10.1.0.10:1182 10.1.0.10:389 ESTABLISHED 1308
> TCP 10.1.0.10:1206 10.1.0.10:3268 ESTABLISHED 3028
> TCP 10.1.0.10:1209 10.1.0.10:1025 ESTABLISHED 3028
> TCP 10.1.0.10:1310 10.1.0.10:389 CLOSE_WAIT 988
> TCP 10.1.0.10:1400 10.1.0.10:1025 ESTABLISHED 496
> TCP 10.1.0.10:1512 10.1.0.10:389 CLOSE_WAIT 4872
> TCP 10.1.0.10:1647 10.1.0.10:389 CLOSE_WAIT 4872
> TCP 10.1.0.10:1718 10.1.0.10:3268 ESTABLISHED 4548
> TCP 10.1.0.10:1722 10.1.0.10:389 CLOSE_WAIT 4548
> TCP 10.1.0.10:1730 10.1.0.10:3268 CLOSE_WAIT 1308
> TCP 10.1.0.10:2050 10.1.0.10:389 ESTABLISHED 4548
> TCP 10.1.0.10:2306 10.1.0.10:389 ESTABLISHED 1308
> TCP 10.1.0.10:2368 10.1.0.10:389 ESTABLISHED 3028
> TCP 10.1.0.10:2839 10.1.0.10:135 ESTABLISHED 3028
> TCP 10.1.0.10:3268 10.1.0.10:1090 ESTABLISHED 496
> TCP 10.1.0.10:3268 10.1.0.10:1163 ESTABLISHED 496
> TCP 10.1.0.10:3268 10.1.0.10:1173 ESTABLISHED 496
> TCP 10.1.0.10:3268 10.1.0.10:1206 ESTABLISHED 496
> TCP 10.1.0.10:3268 10.1.0.10:1718 ESTABLISHED 496
> TCP 10.1.0.10:5900 10.1.0.54:1193 ESTABLISHED 2900
> TCP 127.0.0.1:389 127.0.0.1:1065 ESTABLISHED 496
> TCP 127.0.0.1:389 127.0.0.1:1083 ESTABLISHED 496
> TCP 127.0.0.1:389 127.0.0.1:1131 ESTABLISHED 496
> TCP 127.0.0.1:389 127.0.0.1:1164 ESTABLISHED 496
> TCP 127.0.0.1:389 127.0.0.1:1172 ESTABLISHED 496
> TCP 127.0.0.1:389 127.0.0.1:1717 ESTABLISHED 496
> TCP 127.0.0.1:445 127.0.0.1:2832 ESTABLISHED 4
> TCP 127.0.0.1:1043 0.0.0.0:0 LISTENING 212
> TCP 127.0.0.1:1043 127.0.0.1:1579 ESTABLISHED 212
> TCP 127.0.0.1:1065 127.0.0.1:389 ESTABLISHED 1140
> TCP 127.0.0.1:1083 127.0.0.1:389 ESTABLISHED 1308
> TCP 127.0.0.1:1131 127.0.0.1:389 ESTABLISHED 3028
> TCP 127.0.0.1:1164 127.0.0.1:389 ESTABLISHED 4056
> TCP 127.0.0.1:1172 127.0.0.1:389 ESTABLISHED 2524
> TCP 127.0.0.1:1579 127.0.0.1:1043 ESTABLISHED 3416
> TCP 127.0.0.1:1640 127.0.0.1:5225 CLOSE_WAIT 4572
> TCP 127.0.0.1:1641 127.0.0.1:5225 CLOSE_WAIT 4572
> TCP 127.0.0.1:1643 127.0.0.1:5225 CLOSE_WAIT 4572
> TCP 127.0.0.1:1644 127.0.0.1:5225 CLOSE_WAIT 4572
> TCP 127.0.0.1:1649 127.0.0.1:5226 ESTABLISHED 1484
> TCP 127.0.0.1:1650 127.0.0.1:5225 CLOSE_WAIT 4572
> TCP 127.0.0.1:1651 127.0.0.1:5225 CLOSE_WAIT 4572
> TCP 127.0.0.1:1652 127.0.0.1:5225 CLOSE_WAIT 4572
> TCP 127.0.0.1:1653 127.0.0.1:5225 CLOSE_WAIT 4572
> TCP 127.0.0.1:1717 127.0.0.1:389 ESTABLISHED 4548
> TCP 127.0.0.1:2832 127.0.0.1:445 ESTABLISHED 4
> TCP 127.0.0.1:5226 127.0.0.1:1649 ESTABLISHED 4572
> TCP 127.0.0.1:8005 0.0.0.0:0 LISTENING 4572
> UDP 0.0.0.0:42 *:* 2820
> UDP 0.0.0.0:135 *:* 844
> UDP 0.0.0.0:445 *:* 4
> UDP 0.0.0.0:500 *:* 496
> UDP 0.0.0.0:1036 *:* 1308
> UDP 0.0.0.0:1040 *:* 3028
> UDP 0.0.0.0:1042 *:* 4056
> UDP 0.0.0.0:1058 *:* 892
> UDP 0.0.0.0:1063 *:* 1140
> UDP 0.0.0.0:1113 *:* 892
> UDP 0.0.0.0:1210 *:* 3028
> UDP 0.0.0.0:3456 *:* 1308
> UDP 0.0.0.0:3457 *:* 1308
> UDP 0.0.0.0:4500 *:* 496
> UDP 10.1.0.10:53 *:* 1140
> UDP 10.1.0.10:88 *:* 496
> UDP 10.1.0.10:123 *:* 944
> UDP 10.1.0.10:137 *:* 4
> UDP 10.1.0.10:138 *:* 4
> UDP 10.1.0.10:389 *:* 496
> UDP 10.1.0.10:464 *:* 496
> UDP 127.0.0.1:53 *:* 1140
> UDP 127.0.0.1:123 *:* 944
> UDP 127.0.0.1:1062 *:* 1140
> UDP 127.0.0.1:1064 *:* 1140
> UDP 127.0.0.1:1066 *:* 1524
> UDP 127.0.0.1:1076 *:* 1308
> UDP 127.0.0.1:1112 *:* 1912
> UDP 127.0.0.1:1121 *:* 2820
> UDP 127.0.0.1:1124 *:* 2088
> UDP 127.0.0.1:1128 *:* 3028
> UDP 127.0.0.1:1162 *:* 4056
> UDP 127.0.0.1:1171 *:* 2524
> UDP 127.0.0.1:1183 *:* 440
> UDP 127.0.0.1:1190 *:* 2656
> UDP 127.0.0.1:1200 *:* 988
> UDP 127.0.0.1:1201 *:* 988
> UDP 127.0.0.1:1309 *:* 988
> UDP 127.0.0.1:1322 *:* 1116
> UDP 127.0.0.1:1404 *:* 1084
> UDP 127.0.0.1:1510 *:* 4872
> UDP 127.0.0.1:1575 *:* 5556
> UDP 127.0.0.1:1716 *:* 4548
> UDP 127.0.0.1:1720 *:* 4548
> UDP 127.0.0.1:3456 *:* 1308
> UDP 127.0.0.1:3457 *:* 1308
>
>
>:3389 is Pid 956 which is svchost.exe
>
>
>>
>> 2. On the problematic client workstations, right click My Computers, go
to
>> Remote tab. Make sure that you have checked the boxes "Remote
Assistance"
>> and "Remote Desktop".
>
>Yes to both
>
>> 3. Start one problematic client workstation in Safe mode, can you
reproduce
>> the issue?
>>
>> =============
>>
>> If the issue persists, please help to gather following information for
>> further research:
>>
>> a. On a good client workstation, can you directly RDP (mstsc) to the
>> problematic client workstations?
>
>No I can not connect, not even from the sbs server. The machines are all
on
>the same lan (all on my desk on the same switch....)
>
>> b. When did the issue occur? Could you RWW -> RDP to these problematic
>> client workstations before?
>>
>I have never been able to.
>
>> c. On a good client workstation, open a command window, type following
>> command:
>>
>
>
>> telnet <ip address of the problematic client workstation> 3389
>>
>> What is the result?
>
>Black screen
>
>i press enter and the dos prompt comes back.
>
>>
>> d. In your original post, you mentioned "sometimes I remove them from
the
>> domain and then re add them (via the wizzard) and they then work". I
need
>> to know:
>>
>> i. After rejoin problematic clients' workstations into domain, did you
make
>> any configuration on the Server or the problematic client workstations
so
>> the issue occurs again?
>
>no none that I can think of. It does not always work.
>>
>> ii. Can you reproduce the issue?
>>
>Yes
>
>> Please take your time to perform the steps above and collect the
>> information for us to troubleshoot your issue. I am looking forward to
>> hearing from you!
>>
>> Best regards,
>>
>> Brandy Nee
>>
>> Microsoft CSS Online Newsgroup Support
>>
>> Get Secure! - www.microsoft.com/security
>> ======================================================
>> This newsgroup only focuses on SBS technical issues. If you have issues
>> regarding other Microsoft products, you'd better post in the
corresponding
>> newsgroups so that they can be resolved in an efficient and timely
manner.
>> You can locate the newsgroup here:
>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>
>> When opening a new thread via the web interface, we recommend you check
the
>> "Notify me of replies" box to receive e-mail notifications when there
are
>> any updates in your thread. When responding to posts via your
newsreader,
>> please "Reply to Group" so that others may learn and benefit from your
>> issue.
>>
>> Microsoft engineers can only focus on one issue per thread. Although we
>> provide other information for your reference, we recommend you post
>> different incidents in different threads to keep the thread clean. In
doing
>> so, it will ensure your issues are resolved in a timely manner.
>>
>> For urgent issues, you may want to contact Microsoft CSS directly.
Please
>> check http://support.microsoft.com for regional support phone numbers.
>>
>> Any input or comments in this thread are highly appreciated.
>> ======================================================
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>>
>>
>> --------------------
>> >Thread-Topic: RWW not working on some client desktops
>> >thread-index: AcX+xTXu29kFiOlaRT2GfW6/jb3r6w==
>> >X-WBNR-Posting-Host: 202.156.6.36
>> >From: "=?Utf-8?B?R29yZG9uIExhbWI=?="
<GordonLamb@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >References: <907BEB78-A217-44A3-BB04-669E48A666B7@xxxxxxxxxxxxx>
>> <Ysnh$lG$FHA.3764@xxxxxxxxxxxxxxxxxxxxx>
>> <FB74917D-72EA-4948-95EC-26C3462E9F3E@xxxxxxxxxxxxx>
>> <dhQzMKL$FHA.832@xxxxxxxxxxxxxxxxxxxxx>
>> >Subject: RE: RWW not working on some client desktops
>> >Date: Sun, 11 Dec 2005 18:39:01 -0800
>> >Lines: 83
>> >Message-ID: <50FE402C-B2D4-42DF-A3C6-C4C5A096F727@xxxxxxxxxxxxx>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.windows.server.sbs
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:229407
>> >X-Tomcat-NG: microsoft.public.windows.server.sbs
>> >
>> >Hi Brandy,
>> >
>> >Thanks for your help.
>> >
>> >Reply inline
>> >
>> >Regards
>> >
>> >Gordon
>> >
>> >
>> >>
>> >> 1. Do you mean that the workstations have Murphy's law installed have
>> the
>> >> RWW access issue?
>> >
>> >Murphy's law - also known as Sod's law - What can go wrong will go
wrong
>> at
>> >the most inconvenient time or place - IE only the Important machines
have
>> the
>> >problem.....
>> >
>> >> 2. Please explain in detail "Can not control the PC by RWW as any
user".
>> >>
>> >
>> >In the RWW website I click on connect to client desktops
>> >I then select the compiuter I want to use and click connect
>> >I get the following message
>> >
>> >Connectivity to remote computer could not be established. Ensure that
the
>> >remote computer is on and connected to the Windows small business
server
>> >network.
>> >
>> >The machine is on and working, I can ping it and the user can log on to
it
>> >from the keyboard.
>> >
>> >> 3. As I mentioned in my last reply, you mentioned "RWW not working",
I
>> need
>> >> to know:
>> >
>> >It is the connect to client computer section that does not work for
some
>> >pc's. the rest is fine. It is the workstations that have the problem
not
>> the
>> >users.
>> >
>> >Users are administrators of the local machine and also the
Administrator
>> >user can not connect. Both Administrator and user can connect to other
>> >machines no the network via the nect to client computer section.
>> >
>> >I can manage the PC from the Server managment application when I log on
to
>> >the server
>> >
>> >in the PC's event log is the following
>> >
>> >Event Type: Warning
>> >Event Source: LSASRV
>> >Event Category: SPNEGO (Negotiator)
>> >Event ID: 40961
>> >Date: 12/12/2005
>> >Time: 01:37:20
>> >User: N/A
>> >Computer: GLPCW02
>> >Description:
>> >The Security System could not establish a secured connection with the
>> server
>> >ldap/glserver01.<server>.local/<server>.local@<server>.local. No
>> >authentication protocol was available.
>> >
>> >For more information, see Help and Support Center at
>> >http://go.microsoft.com/fwlink/events.asp.
>> >
>> >If I try to use the connect to computer via terminal services option on
>> the
>> >manage client computer page of the server managment tool I get the
>> following
>> >
>> >The client could not connect to the remote computer
>> >
>> >Remote connections might not be enables on the computer might be too
busy
>> to
>> >accept new connections. it is also possible that network problems are
>> >preventing your connection.
>> >
>> >Please try connecting again later. If the problem continues to occur,
>> >contact your administrator
>> >
>> >
>> >I hope the above clarifies the problem a little.
>> >
>> >Regards
>> >
>> >Gordon
>> >
>>
>>
>

.

Relevant Pages

  • Re: Redirect problems to remote client
    ... sent you a copy of the results file from the client. ... > remote client and redirecting the My Documents folder. ... > - Internet Explorer Maitenance policy processing ... Microsoft is providing this information as a convenience to you. ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW - One client unable to connect to his computer
    ... Drop down the security level for the trusted sites of this client: ... click to check the "Hide All Microsoft Services" ... The RWW remote desktop connection need to access SBS TCP 4125 port. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN fail to connect
    ... How do you configure the VPN connection? ... Please logon to an internal client computer, ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote Web Workplace Connect to client computer error
    ... going to attempt to download a Microsoft Remote Desktop ActiveX control ... That's going to be if the client does not ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN timeouts
    ... You remote clients VPN connection will timeout while trying to connect SBS ... We recommend that client to access VPN server by SBS connection manager. ... and then right click 'Microsoft Firewall' to ...
    (microsoft.public.windows.server.sbs)