Unable to connect to clients via Remote Assistance or Remote Desktop

Unable to connect to clients via Remote Assistance or Remote Desktop

Post by Garbi » Fri, 22 Dec 2006 04:11:33


Here is an overview of our network:

Server 2003 SBS in our headquarters
- DNS and WINS all go through here

Cisco PIX 506E at headquarters, Cisco PIX 501 at remote office
(192.168.1.1 at hq, 192.168.0.1 at remote)
- VPN Tunnel

Sometimes before it was hit or miss if I could connect to the computers
at our remote location, but now it's completely stopped. Not only is
it our remote location, but I can't even connect to my test computer
here at the same location as the server.

Under the Remote Assitance Group Policy, I have Offer Remote Assitance
enabled, and I list Administrators as the group allowed to connect.
Under Windows Firewall group policy, I made the proper changes for
Defining Port Exemptions and Program Exemptions as stated by the Remote
Assistance explanation menu:

However, this isn't working. I did a gpupdate /force on the client,
and that didn't help either. When I try to connect for Remote
Assitance, it says "The remote server machine does not exist or is
unavailable". When I try to connect for Remote Desktop, it says "The
Client could not connect to the remote computer. Remote Connections may
not be enabled or the computer might be too busy to accept new
connections. It is also possible that network problems are preventing
your connection."

I'm all out of ideas. Any other things I should try? It would
obviously seem as if there is some configuration issue, but I don't
know what that would be.

Thanks....
 
 
 

Unable to connect to clients via Remote Assistance or Remote Desktop

Post by v-terli » Fri, 22 Dec 2006 16:36:44

ello Garbis,

Thank you for posting here.

According to your description, I understand that you can not connect
clients via Remote Assistance or Remote Desktop, even the client is in
local network. 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. Rerun CEICW

You have to make sure your SBS 2003 server have right network
configuration. Go through the follow KB and Rerun CEICW again carefully.

How to configure Internet access in Windows Small Business Server 2003
http://support.microsoft.com/kb/825763/en-us

2. Please disable the firewall on the problematic client, then test this
issue.

3. Please telnet 3389 port from SBS to problematic client. If it not works,
please check your VPN configuration. May be there are some firewalls block
the connection?

4. Remote Assistance will use multiple TCP port, please check your
configuration via the following KB:

Remote Assistance cannot connect to a Windows XP SP2 client computer in SMS
Administrator console in Systems Management Server 2003
http://support.microsoft.com/?id=886120

Additional, since your Site-to-Site VPN is setup by 3rd-party hardware, if
you have problem about connection via this VPN, you can connect your Cisco
vendor for further assistance.

If the issue persists, please kindly help me collect some information for
further investigation:

1. Do you install ISA on SBS server? What is the version of ISA?

2. Is this issue happens on all clients?

3. Try to access RDP from the client itself, is it fine?

4. Try to access the problematic client from other client machine, is it
fine?

5. How many NICs in your SBS server?

6. Gather netstat -ano command outcome on problematic client and let me
know the result.

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.

--------------------
| From: "Garbis" < XXXX@XXXXX.COM >
|
 
 
 

Unable to connect to clients via Remote Assistance or Remote Desktop

Post by Garbi » Sun, 24 Dec 2006 02:27:47

erence,

Thanks for the reply. I actually fixed this issue.

I deleted the windows firewall group permission, and then created a new
one.

I re-added all of the proper exceptions, and now I can do remote
desktop and remote assistance. I'm not sure why it stopped working,
but at least this fixed the problem.

Thanks...


Terence Liu [MSFT] wrote:

 
 
 

Unable to connect to clients via Remote Assistance or Remote Desktop

Post by v-terli » Tue, 26 Dec 2006 18:20:23

ello Phil,

I'm glad to hear that things are working correctly for you now. Thank you
very much for sharing out your resolution. Please do not hesitate to post
in this great newsgroup if you need any assistance in the future. I look
forward to working with you again.

Thanks and Merry Christmas!

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.

--------------------
| From: "Garbis" < XXXX@XXXXX.COM >
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: Re: Unable to connect to clients via Remote Assistance or Remote
Desktop
| Date: 22 Dec 2006 09:27:47 -0800
| Organization: http://groups.google.com
| Lines: 176
| Message-ID: < XXXX@XXXXX.COM >
| References: < XXXX@XXXXX.COM >
| < XXXX@XXXXX.COM >
| NNTP-Posting-Host: 206.239.170.180
| Mime-Version: 1.0
| Content-Type: text/plain; charset="us-ascii"
| X-Trace: posting.google.com 1166808472 13971 127.0.0.1 (22 Dec 2006
17:27:52 GMT)
| X-Complaints-To: XXXX@XXXXX.COM
| NNTP-Posting-Date: Fri, 22 Dec 2006 17:27:52 +0000 (UTC)
| In-Reply-To: < XXXX@XXXXX.COM >
| User-Agent: G2/1.0
| X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
SV1),gzip(gfe),gzip(gfe)
| Complaints-To: XXXX@XXXXX.COM
| Injection-Info: h40g2000cwb.googlegroups.com;
posting-host=206.239.170.180;
| posting-account=LPTghw0AAACd6dIrwn_wzxAGfInXi_uR
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!newsfeed0
0.sul.t-online.de!t-online.de!198.186.194.250.MISMATCH!transit3.readnews.com
!news-out.readnews.com!news-out.readnews.com!news-xxxfer.readnews.com!postne
ws.google.com!h40g2000cwb.googlegroups.com!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:6160
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Terence,
|
| Thanks for the reply. I actually fixed this issue.
|
| I deleted the windows firewall group permission, and then created a new
| one.
|
| I re-added all of the proper exceptions, and now I can do remote
| desktop and remote assistance. I