"Error VBScript Remote Desktop Disconnected
The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might 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 can't connect to any computer on the network thru RWW. If I terminal
services into the server I can then terminal over to the desk top but not
thru RWW. I definetly can't give users access to the server that way.
1. I applied SBS 2003 SP1 and installed isa 2004 as a part of that upgrade.
2. There is no router or firewall in front of the server, only ISA 2004
3. I have run the ceicw after the isa 2004 install.
4. I have turned off the windows firewall thru group policy. The ISA
firewall client has been upgraded to 2004 and is running on the client
computers.
5. Rww is working, Owa is working both thru rww and straight from the web,
outlook rpc is working, sharepoint web site is working thru rww, VPN is
working, Terminal services to the Server desktop is working. The only thing
I can't do is Remote desktop thru RWW.
Need help please. Remote desktop has been down for 6 days. I’m about ready
to uninstall ISA 2004 and reinstall ISA 2000. I know it is something in ISA
because I installed SP1 and then waited a week to install ISA 2004.
Everything was working until ISA 2004 (I installed the ISA version that came
with the SBS 2003 SP1 CD's).
Thanks
Thanks for posting here!
For your description, I understand that you can access the RWW site, but
cannot connect to the remote desktop sessions through the site. If I am off
base, please don't hesitate to let me know.
The problem is probably caused by the 4125 port traffic. For the remote
desktop connection in RWW site, the TCP port 4125 is required. When we
connect to the clients'' desktop through RWW, the SBS server works as a RDP
proxy and use the 4125 port to communicate with the remote clients.
By default, if the ISA 2004 version which has installed in the server box
is an integration version with SBS 2003 SP1, running CEICW can
automatically create a rule to publish the TCP 4125 port through the ISA
2004 server. Please double check you have rerun CEICW and open the TCP 4125
port.
You can refer to the following KB article to configure network connection:
825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763
867483 How to configure networks in ISA Server 2004
http://support.microsoft.com/?id=867483
Try to test, can the question be resolved? When you run CEICW, do you get
any error? If so, please give me a screen shot of the error message.
If the issue persists, please kindly do some test to isolate the issue?
I. On the SBS server, if you connect to the RWW via http://localhost/remote
and logon as a regular user, are you able to connect to the XP workstation
using "Connect to my computer at work"?
II. From the remote location, if you connect to RWW via https://FQDN/remote
and logon as the administrator, are you able to connect to the server using
"Connect to Server Desktops"?
III. Does the issue occur to all Internet clients? Are all of the
workstations at the same location?
- Try connecting from a client at a different remote location, does the
issue occur?
- If the remote client from which you are connecting is running Windows XP
SP2, open Internet Explorer, go to Tools, Internet Options, then click on
the Privacy tab, remove the check for Block pop-ups. Close, re-open IE and
see if the issue persists.
- If you have third party pop-up stopper software installed, please also
disable it.
Try to test, does the issue occur?
IV�® If the problem still persists, please help to gather the following
information:
1. The accurate error info. You may also capture the screen-shoot of the
error page and send the picture to me at v-ya...@microsoft.com
2. Use the ISAinfo utility to collect the ISA configuration information:
a. Download the file from the following URL:
http://www.isatools.org/isainfo/ISAInfo.zip
b. Extract all files to a folder on ISA server
c. Double click Isainfo.js. This will generate 2 files
ISAInfo2004-<computer-name>.log and ISAInfo2004-<computer-name>.xml in the
current folder.
d. Please send these files to me at v-ya...@microsoft.com
3. Gather the ISA Web Proxy and Firewall service logs when reproducing the
problem:
Enable the full Web Proxy/firewall logging option:
a. Open ISA 2004 management console.
b. Expand the server node and highlight ''Monitoring''.
c. In the right pane, switch to the ''Logging'' tab, make sure the ''Task
Pane'' is showed there.
d. In the ''Task Pane'', click ''Configure Web Proxy Logging'' under
''Logging Tasks'', and then switch the ''log storage format'' from ''MSDE
database'' (default) to ''File''.
e. Switch to the ''Fields'' tab, and then click ''Select All''.
f. Click OK, and then click ''Apply'' to save changes and update the
configuration.
g. Click ''Configure Firewall Logging''. Do step d~f to enable the full
logging options for firewall logging.
Prepare to take the trace:
a. Temporarily stop the Firewall service to clear the current existing W3C
logs: Monitoring->Services tab, and then right click ''Microsoft Firewall''
to choose ''Stop''.
b. Go to the log saving directory and clean any existing .W3C logs. By
default, the logs will be saved to ''C:\Program Files\Microsoft ISA
Server\ISALogs''. (Some MDF may not be able to deleted, that''s normal.)
c. Go back to the ISA 2004 management console, and then Start the stopped
''Microsoft Firewall'' service.
Reproduce the problem:
a. Go to the external client computer. Try to access the RWW web site.
b. Go back to the ISA server. Stop the ''Microsoft Firewall'' service. Open
Windows Explorer, navigate to the ISA log file folder. Collect the recent
w3c files. Save them to a zip package as ''isalogs.zip''. Start the
''Microsoft Firewall'' Service.
c. Send the zip packages to me at v-ya...@microsoft.com
I appreciate you time and efforts to perform test. I am currently standing
by for you test result. I am always happy to be of further assistance.
Have a nice day!
Best Regards,
Jenny Wu
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 and Remote Desktop
>thread-index: AcWterNl7poVX4n1QlWS85SmT8aeSQ==
>X-WBNR-Posting-Host: 69.215.57.17
>From: "=?Utf-8?B?S2VpdGggU2NobWVpY2hlbA==?="
<KeithSc...@discussions.microsoft.com>
>Subject: RWW and Remote Desktop
>Date: Tue, 30 Aug 2005 08:51:35 -0700
>Lines: 33
>Message-ID: <6398863F-43BA-4DE5...@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:149171
>X-Tomcat-NG: microsoft.public.windows.server.sbs
I get no errors during CEICW.
ISA has created a SBS RWW Inbound Access Rule. That is for port 4125.
When I try to connect internally to Http://localhost/remote, RWW does not
work. If I substitute my server namer for localhost, RWW works and I can
connect to remote desktops. Could this be an issue? I have not knowingly
changed this.
If I log into RWW externally as Administrator I still get the same error
message as before.
This does happen for every client, and all computers are in the same
location. I have tried to remote in from multiple locations.
The only error message I'm getting is the one I posted in my main message.
I get it after you select a computer to connect to and try to connect.
I've downloaded ISAInfo.zip and will send you the extra information later.
Keith
""Jenny wu [MSFT]"" wrote:
> >Need help please. Remote desktop has been down for 6 days. I’m about
For the localhost issue, please add your FQDN and the IP address to HOSTS
file (C:\Windows\System32\Drivers\ETC\HOSTS), such as:
127.0.0.1 localhost
XX.XX.XX.XX(IP address) servername
XX.XX.XX.XX(IP address) FQDN
For your now scenario, I think the cause may be network configuration, let
us perform further test to isolate the issue:
1. Please try to access RWW sites using http://IP(public IP
address)/remote, how about the result?
2. Please try to run command "telnet IP:4125" (no quota marks) in command
prompt and paste the result in the newsgroup.
3. Have you installed router outside of the SBS LAN? Did you open 4125 port
in the router?
4. Please kindly help me collect these information and ISAinfo. And send to
v-ya...@microsoft.com
Have a nice day!
Best Regards,
>thread-index: AcWuQfsRvY5CejsMSzqbXTrroM2npw==
>X-WBNR-Posting-Host: 69.215.57.17
>From: "=?Utf-8?B?S2VpdGggU2NobWVpY2hlbA==?="
<KeithSc...@discussions.microsoft.com>
>References: <6398863F-43BA-4DE5...@microsoft.com>
<Siliwffr...@TK2MSFTNGXA01.phx.gbl>
>Subject: RE: RWW and Remote Desktop
>Date: Wed, 31 Aug 2005 08:38:05 -0700
>Lines: 236
>Message-ID: <C304F865-90A0-43C9...@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:149578
>X-Tomcat-NG: microsoft.public.windows.server.sbs
Adding my servers internal ip address and server name to the hosts file has
fixed the problem. All users can connect to thier desktops. I know this is
what fixed it because I made this change only and everything worked
immediatly.
Thank-you very much for your help with this issue.
Keith
""Jenny wu [MSFT]"" wrote:
> >> IV£® If the problem still persists, please help to gather the
Thanks for your update. I am glad to know that things are getting fine now.
I appreciate your time and effort to try my suggestions and get this
resolved.
Please feel free to post back when you need further assistance on this
issue and I am always happy to be assistance of you!
Have a nice day!
Best Regards,
>thread-index: AcWvIvNcZS25QAOyQ1Cki4XnbB6IiA==
>X-WBNR-Posting-Host: 24.11.231.117
>From: "=?Utf-8?B?S2VpdGggU2NobWVpY2hlbA==?="
<KeithSc...@discussions.microsoft.com>
>References: <6398863F-43BA-4DE5...@microsoft.com>
<Siliwffr...@TK2MSFTNGXA01.phx.gbl>
<C304F865-90A0-43C9...@microsoft.com>
<qR1F3#urFHA...@TK2MSFTNGXA01.phx.gbl>
>Subject: RE: RWW and Remote Desktop
>Date: Thu, 1 Sep 2005 11:28:29 -0700
>Lines: 313
>Message-ID: <1D46C817-10D0-47E8...@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:149986
>X-Tomcat-NG: microsoft.public.windows.server.sbs