Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Cannot connect to server remotelyor locally

1 view
Skip to first unread message

Lanwench [MVP - Exchange]

unread,
Oct 14, 2005, 12:07:05 AM10/14/05
to

In news:F0522D39-FB3D-4AD8...@microsoft.com,
Marko <Ma...@discussions.microsoft.com> typed:
> Hi , need some help please with SBS 2003.
>
> I can access my local clients remotely and access my companyweb via
> RWW. But when I get to access server a blank page comes up with
> connecting..... in the middle of the page but that's all , and no
> error message.
>
> I have a single NIC, NO ISA server is the DHCP which connects to the
> internet via a DSL router.
>
> Have forwarded ports, 4127, 4125,444,443,3389, 8080, 80 and more to
> point to the SBS box.

Eeek!

No port 80. Nor 8080. Nor 4127 (?). Nor "more". The only one I'd add is TCP
25 for SMTP - presuming you host your own mail. Don't randomly open ports -

Can you connect to the server via the RD client on the LAN? Make sure that
works first.

>
> Any suggestions where to look
>
> Mark


Marko

unread,
Oct 14, 2005, 4:40:02 AM10/14/05
to
Thanks for your reply.

As you can see still a novice here, what is the RD client?

Have done as you said and not forwarded any ports, not using exchange yet as
no antivirus installed on server.

I still get CONNECTING in middle of the page! why is that?

Everything else connects fine.

Mark

Jenny wu [MSFT]

unread,
Oct 14, 2005, 4:57:49 AM10/14/05
to
Hi Mark,

Thanks for posting here! Also thanks for Lanwench's input.

For your description, I understand that you can not remotely access the SBS
server box in RWW site. If I am off base, please don't hesitate to let me
know.

Based on my experience, the problem should lies in the server box side. Let
us do some test to try to troubleshoot the issue:

I. Please try to rerun CEICW to make sure enable basic firewall and publish
RWW and OWA to internet. You can refer to the following steps:

1. Expand Standard Management | To Do List.
2. Click Connect to the Internet in the right pane.
3. Navigate the wizard to Firewall and then select Enable firewall. In the
next page, make sure the Terminal services item is checked in services
configuration page.
4. Click Next and then select Allow access to the following web site
services from the internet.
5. Make sure OWA, RWW be selected and click Next.
6. Click Create a new Web services certificate (input your FQDN as the web
server certificate) and then click Next.
7. Following the wizard to finish it.

More detail information:

825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763

II. And then try to RDP to the server box from the internal client computer
to test, how about the result?

If the issue persists, that indicates some hardware problem of the server
box. Please try to connect the server box to a different port of
router/switcher to see if the issue be fixed.

If the issue disappears locally, please try to access the server box using
appropriate user permissions (domain admin) remotely in RWW site, how about
the result?

Additionally, it is not recommended we open too many ports in the router
since it is very insecure to our network. Generally, we open the ports we
needed to allow some specific traffic. you can refer to the following list:

TCP port Definition
25 Email (SMTP)
80 required for HTTP
requests for your site
443 required for HTTPS
requests using SSL, which secures communications from your server and a Web
browser
444 Companyweb
4125 Remote Web Workplace
1723 (plus GRE Protocol 47) VPN
3389 Terminal Services
21 FTP

I am currently waiting for your test result and glad to be assistance of
you!

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.

--------------------
>From: "Lanwench [MVP - Exchange]"
<lanw...@heybuddy.donotsendme.unsolicitedmail.atyahoo.com>
>References: <F0522D39-FB3D-4AD8...@microsoft.com>
>Subject: Re: Cannot connect to server remotelyor locally
>Date: Fri, 14 Oct 2005 00:07:05 -0400
>Lines: 31
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
>X-RFC2646: Format=Flowed; Original
>Message-ID: <e#6EEUH0F...@TK2MSFTNGP14.phx.gbl>
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: cpe-24-193-74-240.nyc.res.rr.com 24.193.74.240
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:161263
>X-Tomcat-NG: microsoft.public.windows.server.sbs

Jenny wu [MSFT]

unread,
Oct 14, 2005, 5:13:50 AM10/14/05
to
The RDP client is Remote Desktop Connection software, with it you get full
access to your work computer remotely via an Internet or network
connection. This method use same terminal services as that you connect to
computer using RWW.

The Windows XP has pre-installed the application, you just need type
"mstsc" (no quotations marks) in command line (Start -> Run) to launch it.

If the client computer is not preinstall Remote Desktop Connection
software, you can download in the following link and install it:
http://www.microsoft.com/downloads/details.aspx?familyid=80111f21-d48d-426e-
96c2-08aa2bd23a49&displaylang=en

Have a nice day!

Best Regards,

Jenny Wu
Microsoft CSS Online Newsgroup Support

--------------------
>Newsgroups: microsoft.public.windows.server.sbs
>From: v-ya...@online.microsoft.com ("Jenny wu [MSFT]")
>Organization: Microsoft
>Date: Fri, 14 Oct 2005 08:57:49 GMT


>Subject: Re: Cannot connect to server remotelyor locally

>X-Tomcat-NG: microsoft.public.windows.server.sbs
>MIME-Version: 1.0
>Content-Type: text/plain
>Content-Transfer-Encoding: 7bit

Marko

unread,
Oct 14, 2005, 9:58:03 AM10/14/05
to
Hi Jenny, thanks for you input, tried what you said and got this message:

"The connection was ended because of a network error"
when I used RDP.

No port 47 open though , does that matter?

Mark

Jenny wu [MSFT]

unread,
Oct 17, 2005, 7:38:12 AM10/17/05
to
Hi Mark,

Thanks for your update! I appreciate your time and efforts to the issue.
Regarding to the error: "The connection was ended because of a network
error. Please try connecting to the remote computer again"

Based on research, I have the following suggestions for you to try.

1. Open Registry Editor (regedit.exe), locate the following registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters

2. Click Parameters, click File menu>Export, backup the Parameters key.

3. Delete the "Certificate" REG_BINARY value under the Parameters key.

4. Reboot, the value will be recreated again.

Try the remote desktop connection to see if it works.

If the error reoccurs, please run the tracert command to trace route.

On the remote client, run the following command:
Tracert <IP address>
Where <IP address> is the IP address of the host computer.

How to Use TRACERT to Troubleshoot TCP/IP Problems in Windows
http://support.microsoft.com/?id=314868

Please also check the event log to see if there are any envet ID regarding
RDP and let me know.

We need not open port 47 to allow RDP traffic.

I am happy to be assistance of you and look forward to your reply!

Have a nice day!

Best Regards,

--------------------
>Thread-Topic: Cannot connect to server remotelyor locally
>thread-index: AcXQx0uN+DbuTu/oSI2IUQCkwOvLlQ==
>X-WBNR-Posting-Host: 81.77.140.213
>From: "=?Utf-8?B?TWFya28=?=" <Ma...@discussions.microsoft.com>
>References: <F0522D39-FB3D-4AD8...@microsoft.com>
<e#6EEUH0F...@TK2MSFTNGP14.phx.gbl>
<X7EDe1J0...@TK2MSFTNGXA01.phx.gbl>


>Subject: Re: Cannot connect to server remotelyor locally

>Date: Fri, 14 Oct 2005 06:58:03 -0700
>Lines: 163
>Message-ID: <C1FA4BAB-B892-4B05...@microsoft.com>
>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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:161405
>X-Tomcat-NG: microsoft.public.windows.server.sbs

Marko

unread,
Oct 17, 2005, 5:41:04 PM10/17/05
to
Hi Jenny,

Great news! That worked. Deleted cerificate and rebooted and I can now
connect to the server. Well done you!

Why did this happen though, and should I do this again if it recurs?

Jenny wu [MSFT]

unread,
Oct 18, 2005, 9:09:06 AM10/18/05
to
Hi Mark,

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.

The issue caused by that a potential race condition between the Icaapi.dll
and Rdpwsx.dll dynamic-link libraries (DLLs) may cause the private
certificate key on the Terminal Services server not to be synchronized.

For details, please refer to the following MS KB article:

323497 "The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..."
http://support.microsoft.com/?id=323497

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-Topic: Cannot connect to server remotelyor locally

>thread-index: AcXTY3l2Vf8HYILATR2md6NAtIz8Yg==
>X-WBNR-Posting-Host: 81.79.114.172


>From: "=?Utf-8?B?TWFya28=?=" <Ma...@discussions.microsoft.com>
>References: <F0522D39-FB3D-4AD8...@microsoft.com>
<e#6EEUH0F...@TK2MSFTNGP14.phx.gbl>
<X7EDe1J0...@TK2MSFTNGXA01.phx.gbl>

<C1FA4BAB-B892-4B05...@microsoft.com>
<BVvJG9w0...@TK2MSFTNGXA01.phx.gbl>


>Subject: Re: Cannot connect to server remotelyor locally

>Date: Mon, 17 Oct 2005 14:41:04 -0700
>Lines: 294
>Message-ID: <F7B616B0-54C9-4A16...@microsoft.com>


>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: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:162144
>X-Tomcat-NG: microsoft.public.windows.server.sbs

0 new messages