Re: RWW client won't connect

That's a real bummer. I hope they didn't make you pay for the call. I would
never have gotten that one.

--
Claus
"Ken" <Ken@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:171A9980-9C40-4386-BEB6-C3CEACA25B58@xxxxxxxxxxxxxxxx
Thanks for all the input, especially Claus. Was under the gun to get this
working so I contacted MS and after 4 grueling hours it was determined
that
it was a registry error on every system. No reason why other than maybe
some
software interfered with nornal settings. Here is the registry fix that
worked:

HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\TERMINAL SERVER\WINSTATIONS\RDP-TCP

Changed PortNumber to decimal 3389.

For some reason it was set to 30089.

That did it.

Thanks again for the help.
Ken

"Terence Liu [MSFT]" wrote:

Hello Ken,

Thank you for posting here. Let's also thank Claus for the input.

According to your description, I understand that you unable connect some
client computers desktop thru RWW. If I have misunderstood the problem,
please don't hesitate to let me know.

Based on my research, I suggest we try the following steps to see if we
can
resolve this issue:

1. Check the remote desktop connection settings:

a. Right click My Computer on problematic client computer, select
Properties.

b. Click Remote tab, ensure tick "Allow users to connect remotely to this
computer" option.

c. Select Remote Users button, please ensure your user account which need
to RDP to it in the list.

d. Click OK twice to finish.

2. Check the windows firewall settings:

a. Open Control panel on problematic client computer

b. Double click Windows Firewall, select Exceptions tab

c. Ensure the Remote Desktop option is checked

d. Click OK.

3. Ensure the problematic client computers do not install any 3rd-party
firewall on it.

4. RWW desktop connection only support Windows XP client or later.
Confirm
the problematic client computer OS version.

If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:

1. Does this issue happen on all clients or only several clients?

2. Please try to logon RWW from SBS itself, and try to connect the
problematic client desktop. Do you get the same result?

3. Please run command "mstsc" to open RDC on SBS, then connect to the
problematic client desktop. Do you get the same result?

4. Run command "ipconfig /all > c:\ipconfig_sbs.txt" and "route print >
c:\route_sbs.txt" on SBS, send the files c:\ipconfig_sbs.txt and
c:\route_sbs.txt to me at v-terliu@xxxxxxxxxxxxx

5. Run command "ipconfig /all > c:\ipconfig_client.txt" and "route print
>
c:\route_client.txt" on problematic client, send the files
c:\ipconfig_client.txt and c:\route_client.txt to me at
v-terliu@xxxxxxxxxxxxx

6. What's edition of your SBS?

I hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

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 client won't connect
| thread-index: AcgTLWHG32V2nC1fQ7uCSKUqfdbo3A==
| X-WBNR-Posting-Host: 207.46.19.197
| From: =?Utf-8?B?S2Vu?= <Ken@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: RWW client won't connect
| Date: Sat, 20 Oct 2007 08:25:01 -0700
| Lines: 10
| Message-ID: <662DF2DD-927A-4DFF-A269-4BF64642DAC2@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.2929
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:70553
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| I can use RWW to attach to the server but I have several client systems
I
| can't attach to. It must be a local system problem but don't know
where
else
| to look. All users and client systems have the same administrative
rights
| and have Remote Access checked off under Remote control. On the client
| systems I can't attach to I get the dreaded "Remote system is in use or
not
| available" message.
|
| Any trouble shooting procedures would be appreciated.
|
| Thanks in advance.
|




.

Loading