No Client or Server Desktop Access Through RWW SBS 2003 SP2



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

.



Relevant Pages

  • RE: Failure to install remote access capability of SBS 2003
    ... > Thank you for posting to the SBS Newsgroup. ... > From the RRAS Log file you have pasted, ... This was installed through the windows update server as part of the process ... we strongly suggest that customers install the full patches ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Access Wizard fails to complete with error in rraslog f
    ... You might also try downloading and re-applying Windows 2003 SP2 ... Windows Server 2003 SP2 is also now on the server which was ... Reading VPN Server Name returned OK ... Checking whether RRAS is already running returned OK ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Access Wizard fails to complete with error in rraslog f
    ... Windows Server 2003 SP2 is also now on the server which was ... Reading VPN Server Name returned OK ... Checking whether RRAS is already running returned OK ... Enabling DHCP client addressing returned OK ...
    (microsoft.public.windows.server.sbs)
  • Re: RAS Problem
    ... Download and install the SBS BPA. ... I have Windows Server 2003 SP2. ... Reading VPN Server Name returned OK ... Checking whether RRAS is already running returned OK ...
    (microsoft.public.windows.server.sbs)
  • RE: Failure to install remote access capability of SBS 2003
    ... Thank you for posting to the SBS Newsgroup. ... >From the RRAS Log file you have pasted, ... there are some known issues after you applied Windows Server 2003 SP1 on ... 897342 Known issues that may occur if you install Windows Server 2003 SP1 ...
    (microsoft.public.windows.server.sbs)

Loading