RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2

Hello Bob,

Thank you for your update.

The SBS is running under SP2, the sp2 is windows server 2003 sp2, but not
SBS 2003 sp2. We only have SBS 2003 sp1 still now. Please ensure you had
applied 5 parts of SBS 2003 sp1 on your SBS. You can find the detail steps
in my previous reply.

I hope these steps will give you some help.

Thanks and have a nice weekend!

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: No Client or Server Desktop Access Through RWW SBS 2003 SP2
| thread-index: AcfrA3GdCxE1nGjES866pQgvmHXP+w==
| X-WBNR-Posting-Host: 207.46.19.197
| From: =?Utf-8?B?UkpT?= <RJS@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <50E99B7B-9A3E-4A7B-AAB1-7B0092BA79ED@xxxxxxxxxxxxx>
<Gn0qqbt6HHA.5204@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
| Date: Thu, 30 Aug 2007 05:44:02 -0700
| Lines: 303
| Message-ID: <39BB2A3D-97EC-436E-A964-68FB465055EC@xxxxxxxxxxxxx>
| 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.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:59726
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| A couple of clarifications:
|
| The SBS server is running SP2. All of the Windows XP Clients are running
| SP1 except 2, which are running SP2. I am using a XP client with SP2
| installed to access the RWW.
|
| The SBS has RD enabled. However I don't know if the client computers do.
I
| will have to check.
|
| To my knowledge the clientapps folder has not been moved but I will check.
|
| Thanks for the reply.
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Bob,
| >
| > Thank you for posting here.
| >
| > According to your description, I understand that you cannot connect SBS
and
| > internal client Remote Desktop via RWW. If I have misunderstood the
| > problem, please don't hesitate to let me know.
| >
| > From the error message, I think the RDP is not enable on the SBS and
| > internal client computers, I suggest we try the following steps to see
if
| > we can resolve this issue:
| >
| > Please perform the steps on the SBS and internal client computers:
| >
| > a. Right click My Computer, select Properties.
| >
| > b. Click Remote tab, tick Enable Remote Desktop on this computer
| >
| > c. Select Remote Users button, please add the 2 remote domain user
accounts
| > to the box.
| >
| > d. Click OK twice to finish.
| >
| > For your RRAS log error, based on my experience, this issue may occur
if:
| >
| > 1. The Clientapps directory is moved to other location.
| > 2. You applied Windows Server 2003 SP1 but not SBS SP1.
| >
| > I suggest we try the following steps to see if we can resolve this
issue:
| >
| > I. This issue will occur if the clientapps directory is pointing to an
| > invalid location. So, I would like to know if you have moved the
Clientapps
| > directory to other location.
| >
| > While we can move Clietnapps directory to other location, we need
change
| > the following key to set the new path:
| >
| > "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\clientsetup"
| >
| > By default, "ClientAppsRoot"="C:\ClientApps". If you moved the
Clientapps
| > to other folders or partition, please modify it and then reboot the
| > machine. Then please re-run CEICW wizard and Remote Access wizard to
see if
| > it works.
| >
| > For more information, you can review the following article:
| >
| > How to move the client programs folder to another location in Windows
Small
| > Business Server 2003
| > http://support.microsoft.com/?id=830254
| >
| > II. If it is not above situation, let us check if you have applied the
| > whole SBS 2003 sp1 to the server rather than Windows 2003 sp1. This
issue
| > will also occur if you applied Windows Server 2003 SP1 but not the SBS
SP1
| > or if the SBS SP1 did not finish the installation. If that is the case,
| > please make sure that you downloaded and installed the SBS SP1.
| >
| > And also you can check the registry key as follows:
| >
| > On the SBS server, click Start, click Run, type "regedit" (without the
| > quotation marks) and click OK. Navigate to
| > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer, and check
the
| > data of the registry value ServicePackNumber. Is it set to "1"? If not,
| > then this problem will occur because SBS 2003 SP1 has not been
completely
| > installed. To successfully install SBS 2003 SP1, we must install all
five
| > updates listed below. Additionally, the updates must be installed in
the
| > sequence listed.
| >
| > Downloading and Installing Windows Small Business Server 2003 Service
Pack 1
| >
http://download.microsoft.com/download/e/0/f/e0fee8ce-768d-41c0-8871-9bc48e0
| > b3fc3/ToDownLoadFilesandReadInstructions.htm
| >
| > Note: If one or more of the listed components is already installed, you
can
| > skip to the next step. Since you had installed Windows 2003 sp2, you
can
| > skip the step of Windows 2003 sp1 installation.
| >
| > A. Service Pack 1 for the Windows Server 2003 operating system
| > B. Windows SharePoint Services 2.0 Service Pack 1
| > C. Exchange Server 2003 Service Pack 1
| > E. Windows XP SP2 for Client Deployment
| > F. Windows Small Business Server 2003 Service Pack 1
| >
| > After you applied the whole SBS 2003 SP1, please run CEICW and then
re-run
| > remote access wizard to test the issue. What is the result?
| >
| > Go through the follow KB and Rerun CEICW carefully.
| >
| > How to configure Internet access in Windows Small Business Server 2003
| > http://support.microsoft.com/kb/825763/en-us
| >
| > If we cannot resolve the issue after we perform the above steps, please
| > help me collect some information for further investigation:
| >
| > 1. Can you connect SBS thru RDP from internal client computer?
| >
| > 2. Can you connect client computer thru RDP from SBS?
| >
| > 3. Please capture screenshots on the error messages you get when you
| > connect RDP and send the pictures to me at v-terliu@xxxxxxxxxxxxx
| >
| > 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: No Client or Server Desktop Access Through RWW SBS 2003
SP2
| > | thread-index: AcfqZ0J7aRkTXu0bS6y1ypdh8Eib2g==
| > | X-WBNR-Posting-Host: 207.46.193.207
| > | From: =?Utf-8?B?UkpT?= <RJS@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: No Client or Server Desktop Access Through RWW SBS 2003 SP2
| > | Date: Wed, 29 Aug 2007 11:06:02 -0700
| > | Lines: 113
| > | Message-ID: <50E99B7B-9A3E-4A7B-AAB1-7B0092BA79ED@xxxxxxxxxxxxx>
| > | 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.2826
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:59513
| > | NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | OS Windows SBS 2003 sp2
| > | SBS Hotfix KB872769 installed.
| > | McAffee Enterprise 2007 A/V and security installed
| > |
| > | HP Proliant Server Xenon 3Ghz CPU 1Gb RAM
| > |
| > | The person who set this server up has let customer twist in the wind.

| > The
| > | customer called me to assist in the operation of his POS system
(Windward
| > | System 5) and server administration.
| > |
| > | I am unable to access the system through the RWW. I can log on, view
| > logs
| > | but can�t log on to the server desktop or any of the client
desktops.
| > I have
| > | the proper administrator permissions. The url used to access the RWW
is
| > | https://mail.domain name.com. That gets me to the RWW page but when
I
| > try to
| > | access the client or server desktops, I get the following message:
| > |
| > | ââ?¬Å?The client could not connect to the remote computer. Remote
| > connections
| > | might 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. Please try connecting later. If the problem continues
to
| > occur,
| > | contact your administrator.�
| > |
| > | According to the client, this has been an issue since the system was
| > | installed over a year ago. They can check mail but that�s it.
The
| > original
| > | server failed and this is the system that was reinstalled. Since it
is a
| > | brand new box, I have to assume that the install was a clean install.
I
| > | don�t know how the system was set up however. I can only
assume that
| > | defaults were applied. There are two nic�s, on the server.
One is
| > disabled
| > | and not connected. There is an external router. The server is on a
| > Cisco
| > | switch. I checked the McAfee product and it is not blocking port
4125.
| > |
| > | Research on the Microsoft Website turned up the KB886209 article with
a
| > | possible fix for this problem. I ran the netstat command and nothing
was
| > | listening on port 4125.
| > |
| > | Additionally when I ran the RAS Wizard hoping to fix the problem, it
| > ââ?¬Å?blew
| > | up� and returned the messages in the following log of the
operation.
| > |
| > | 8/28/2007 6:39 PM
| > | C:\Program Files\Microsoft Windows Small Business
| > | Server\Networking\RRASWiz\wizrras.dll, version 5.2.2651.0
| > | Calling CRRASCommit::CommitEx
| > | Calling CRRASCommit::ValidatePropertyBag
| > | pdispPPPBag->QueryInterface returned OK
| > | PropertyBag 37930
| > | Reading property value for enabling Remote Access returned OK
| > | bRemoteAccess = 1
| > | Reading property value for VPN returned OK
| > | bVPN = 1
| > | Reading property value for RAS returned OK
| > | bRAS = 0
| > | Calling CRRASCommit::ValidateVPNProperties
| > | Reading VPN Server Name returned OK
| > | VPN Server Name is Server1.naturesharvestmarket.com
| > | Calling CRRASCommit::ValidateDHCPProperties
| > | DHCP server is installed on the box
| > | CRRASCommit::ValidateDHCPProperties returned OK
| > | CRRASCommit::ValidateVPNProperties returned OK
| > | CRRASCommit::ValidatePropertyBag returned OK
| > | pdispPPPBag->QueryInterface returned OK
| > | Pointer to the property bag 37930
| > | Calling CRRASCommit::CommitRRAS
| > | Arguments:
| > | PropertyBag 37930
| > | bRAS 0
| > | bVPN 1
| > | Getting the GUID of the private NIC returned OK
| > | Private NIC Guid is {F9244865-BFC3-4EE5-A738-DF07BA1B2A04}
| > | Checking whether RRAS is already running returned OK
| > | RRAS already running
| > | Stopping RRAS returned OK
| > | Installing RRAS returned OK
| > | Dhcp server is installed and running on this box
| > | Enabling DHCP client addressing returned OK
| > | Configuring ports returned OK
| > | Identifying the private NIC for RAS returned OK
| > | Setting the default authentication methods returned OK
| > | Disabling NETBIOS for RAS returned OK
| > | Changing RRAS startup type to automatic returned OK
| > | Configuring Remote Access Policy returned OK
| > | Starting RRAS service returned OK
| > | Saving RRAS method returned OK
| > | Method is 2
| > | Where 1 = RAS, 2 = VPN 3 = both
| > | Saving Dhcp Server IP returned OK
| > | CRRASCommit::CommitRRAS returned OK
| > | Calling CRRASCommit::CommitCMAK
| > | Arguments:
| > | PropertyBag 37930
| > | bRAS 0
| > | bVPN 1
| > | Template file name is sbsvpn
| > | Reading VPN Server name returned OK
| > | Reading VPN Server name is Server1.naturesharvestmarket.com
| > | Created temp directory CMP1C41.tmp
| > | Copying required template files to the temp directory returned OK
| > | Updating CMP template returned OK
| > | Updating CMS template returned OK
| > | Updating SED template returned OK
| > | Creating proxy configuration file returned OK
| > | *** Running IExpress to build the package returned ERROR 80004005
| > | *** ERROR: Cannot delete temp directory CMP1C41.tmp
| > | Specifying error location (in CMAK) returned OK
| > | *** CRRASCommit::CommitCMAK returned ERROR 80004005
| > | *** CRRASCommit::CommitEx returned ERROR 80004005
| > |
| > | I researched the error but found nothing to help.
| > |
| > | Any ideas as to what I need to do to fix this problem and get the RWW
| > | working so that I may logon after hours and do my work?
| > |
| > | Bob
| > |
| > |
| >
| >
|

.