SBS 2003 monitoring and remote web workplace not working

I am administering a SBS 2003 server and cannot for the life of me get remote web worplace working properly.

I have the intranet, exchange server, remote desktop all working fine and if i try to login into remote web worplace while my laptop is connected to the office network(although it is not part of the domain) i get through ok. However, when i am on a remote networ, say at home, RWW cannot be accessed.

The errors i ahve notice in my setup are as follows:
1) when i go to the monitoring and reporting page in server management the main page cannot be displayed. It asks me to check that the MSSQL&SBSMONITORING services are running. I also cannot configure any of the alerts notifications, etc as they always display an error saying the same component is not running.
2) when i run the monitoring configuration wizard and try to reinstall the settings, it always fails(red crosses beside all the tasks).
3) when trying to check the built in firewall settings I get the error " windows firewall cannot run because another program or service is running that might use the network address translation component(Ipnat.sys) - there is no other firewall software installed but i am using the firewall and dhcp server of my router, which all the other computers are also connected to.

I have tried doing a repair install(in-place upgrade) but still no go.

Any advice will be much appreciated.

Regards
Matt
dreamcreativeAsked:
Who is Participating?
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You ALWAYS need to apply service packs... the number of people has nothing to do with it.  It has to do with extending the support cycle of the server.  Because mainstream support for SBS 2003 WITHOUT Service Pack 1 has ended already.  SO if you dind't have SP1 installed the server would not be in a supported state.  The same thing will happen later next year when they will end general support of SBS 2003 WITHOUT Service Pack 2.  

This explains it a bit more:
http://msmvps.com/blogs/bradley/archive/2007/07/07/so-why-do-we-need-sp2.aspx

Anyhow... I wouldn't uninstall SP2, but rather REINSTALL it.  (which was one of the recommendations listed for fixing RWW -- http://blogs.technet.com/sbs/archive/2007/06/01/unable-to-rdp-rww-into-the-sbs-server-after-applying-sp2.aspx)

Jeff
TechSoEasy
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
When you say repair install, are you saying you went to Add/Remove and ran the reinstall via the SBS 2003 found there for the Monitoring features?

If you can get to RWW from within the SBS network by typing: rwww.mysbsdomain.com/remote and not from the outside, then there is a problem with the setup.

Rerun the CEICW (via ToDo --> connect to Internet) and reset all of the settings. This should fix any blocks from the outside.

Did you verify DNS for RWW? That is, does rww.mysbsdomain.com resolve to the external IP for your SBS network?

Google DoDig Mice Men to get a tool to help you diagnose whether you are having DNS issues via the Internet.

Philip
0
 
dreamcreativeAuthor Commented:
Thanks for the quick response Philip.

By repair install, I mean I booted from the main disk and performed the repair install thinking something may have not loaded correctly.

I will perform the taks you suggested and see what results i get.

Regards
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Before you go reinstalling stuff...  can you please first give a few more details about what you mean by "RWW cannot be accessed".

What is the EXACT error you are getting?

What URL are you using?  ie, are you using http:// or https://? 

and just FYI, regarding: "when trying to check the built in firewall settings I get the error"
The Windows Firewall is never used on an SBS.  If you only have on NIC then you have told SBS that you are using an external firewall device.  If you have two NICs then Routing and Remote Access is your firewall. (or ISA Server is with Premium Edition).

Jeff
TechSoEasy
0
 
dreamcreativeAuthor Commented:
Hi Jeff

Thanks for clarifying the firewall thing, thought that may have been the case but wasn't 100% sure.

With regards to RWW, here's the senario:
When i am using any computer connected to the same router that the server is connected to, i can open a web browser, type in my remote address and RWW opens up fine. I am assuming this has something to do with the fact that both computers are behind the firewall. However, when i am connected to the internet from a totally different location I just get the usual "internet explorer cannot display the webpage" error.

I have all the neccessary tcp ports open in my router for the services that I'm using(25, 80, 443, 444, 4125) and pointing to my server. I just can't work out why i cannot connect. Am I just simply using the wrong internet address details or what?

I can access Remote desktop with no problems and have also done a VPN test which also worked fine, although i do not at this stage intend to use the VPN function.

Regards
Matt
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
So, if you can access Remote Desktop you also have port 3389 open, right?

Can you please post a COMPLETE ipconfig /all from both the SBS as well as a workstation?

Also, what is the make/model of the router?

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Let me also ask... you say that within the LAN you "type the remote address".  Is your internal Active Directory domain name the same as your Internet domain?  Or are you just using http://servername/remote?  or from the server itself, http://localhost/remote?

Jeff
TechSoEasy
0
 
dreamcreativeAuthor Commented:
The router is a Netgear DG834 and, yes port 3389 is open on the router and is working fine. Our external website is currently hosted off site(which i will change once i can get things running properly) so our Active Directory domain name is different. What I did was create a sub domain(http://remote.domainname.com) and am pointing it to the office at https://ipaddress/remote. This is the address I have been using both while connected to the network and externally. Our ip address is static and as part of my test i have also tried simply using our ip address with /remote at the end. Neither of these work form an external location but both work fine from within the network.

I am currently away until Thursday so I will post the ip config detials then.

Thanks for your assistance
Matt
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
FYI, I wouldn't recommend that you change where your website is hosted.  You are much better off not having that on your SBS.

Will be able to know more about your problem though when you post the ipconfig /all.

Jeff
TechSoEasy
0
 
dreamcreativeAuthor Commented:
Hi Jeff

Below are the ipconfig details you asked for:

Server:
Windows IP Configuration

   Host Name . . . . . . . . . . . . : voodooserver
   Primary Dns Suffix  . . . . . . . : voodoocoffeeco.local
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : voodoocoffeeco.local

Ethernet adapter Server Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-11-25-A4-76-50
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.0.10
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.10


Workstation:
Windows IP Configuration

        Host Name . . . . . . . . . . . . : VOODOO1
        Primary Dns Suffix  . . . . . . . : voodoocoffeeco.local
        Node Type . . . . . . . . . . . . : Mixed
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : voodoocoffeeco.local

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
        Physical Address. . . . . . . . . : 00-03-9D-73-2C-69
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.0.3
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
        DHCP Server . . . . . . . . . . . : 192.168.0.1
        DNS Servers . . . . . . . . . . . : 192.168.0.10
        Lease Obtained. . . . . . . . . . : Thursday, 2 August 2007 10:31:56 AM
        Lease Expires . . . . . . . . . . : Friday, 3 August 2007 10:31:56 AM

Ethernet adapter Wireless Network Connection 3:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Intel(R) PRO/Wireless LAN 2100 3B Mi
ni PCI Adapter
        Physical Address. . . . . . . . . : 00-04-23-82-0D-69


Is it possible that it is some sort of security issue on the server, maybe a service or policy i have not enabled? I am still able to use Remote Desktop with no problems at all, and i tested connecting via VPN again which also worked fine.

Anyway I hope this is able to give you some clue.

Thanks
Matt
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Have you rerun the CEICW as Philip suggested?

Also, please see if you can access RWW from inside your lan by going to http://voodooserver/remote

As an aside... something that's definitely not related to this specific issue... but should be noted, you do not have WINS configured on your SERVER's NIC.  It should be set to 102.168.0.10.  You also should really have DHCP running from your server instead of the router so that things like the WINS setting will get pushed out to the clients.  See the bottom of http://sbsurl.com/dhcp for instructions on how to move it back to your server.

Any time you make changes like that, the CEICW should be rerun.

Jeff
TechSoEasy
0
 
dreamcreativeAuthor Commented:
Thanks for the info Jeff, have updated WINS as suggested. I thought the other day that I should move DHCP to the server so I will do that next week.

I checked http://voodooserver/remote from a worksstation and it worked fine. I have tried rerunning CEICW a number of times but with no luck. I do however have a new little issue in that even though i can get to RWW locally I can no longer access Outlook Web Access which i could before.

One other thing, should the SQL Server Service Manager be connected? The icon in the task tray says not connected and there are no details in the drop down lists for Server and Service to connect to.

I do apologise for sounding a bit dumb but i am quite new to all this. I didn't realize just how complicated this would be.

Thanks
Matt
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
No problem... it would be easier for me to answer your questions though if you could post the output from running SYSTEMINFO at a command prompt.  

Thanks.

Jeff
TechSoEasy
0
 
dreamcreativeAuthor Commented:
Host Name:                 VOODOOSERVER
OS Name:                   Microsoft(R) Windows(R) Server 2003 for Small Business Server
OS Version:                5.2.3790 Service Pack 2 Build 3790
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Primary Domain Controller
OS Build Type:             Multiprocessor Free
Registered Owner:          Voodoo Coffee Company
Registered Organization:   Voodoo Coffee Company Pty Ltd
Product ID:                74995-OEM-4212946-15049
Original Install Date:     2/05/2006, 1:31:04 PM
System Up Time:            0 Days, 16 Hours, 55 Minutes, 30 Seconds
System Manufacturer:       IBM
System Model:              IBM eServer 206m -[8485I3A]-
System Type:               X86-based PC
Processor(s):              2 Processor(s) Installed.
                           [01]: x86 Family 15 Model 4 Stepping 1 GenuineIntel ~
3000 Mhz
                           [02]: x86 Family 15 Model 4 Stepping 1 GenuineIntel ~
3000 Mhz
BIOS Version:              PTLTD  - 6040000
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-au;English (Australia)
Input Locale:              en-us;English (United States)
Time Zone:                 (GMT+10:00) Canberra, Melbourne, Sydney
Total Physical Memory:     1,022 MB
Available Physical Memory: 385 MB
Page File: Max Size:       2,469 MB
Page File: Available:      1,832 MB
Page File: In Use:         637 MB
Page File Location(s):     c:\pagefile.sys
Domain:                    voodoocoffeeco.local
Logon Server:              \\VOODOOSERVER
Hotfix(s):                 55 Hotfix(s) Installed.
                           [01]: File 1
                           [02]: File 1
                           [03]: File 1
                           [04]: File 1
                           [05]: File 1
                           [06]: File 1
                           [07]: File 1
                           [08]: File 1
                           [09]: File 1
                           [10]: File 1
                           [11]: File 1
                           [12]: File 1
                           [13]: File 1
                           [14]: File 1
                           [15]: File 1
                           [16]: File 1
                           [17]: File 1
                           [18]: File 1
                           [19]: Q147222
                           [20]: KB933854 - QFE
                           [21]: SP1 - SP
                           [22]: KB911829 - Update
                           [23]: KB912442 - Update
                           [24]: KB916803 - Update
                           [25]: KB924334 - Update
                           [26]: KB926666 - Update
                           [27]: KB931832 - Update
                           [28]: KB917283 - Update
                           [29]: KB922770 - Update
                           [30]: KB928365 - Update
                           [31]: Q827429
                           [32]: Q927978
                           [33]: IDNMitigationAPIs - Update
                           [34]: NLSDownlevelMapping - Update
                           [35]: KB925398_WMP64
                           [36]: KB933566-IE7 - Update
                           [37]: KB889101 - Service Pack
                           [38]: KB914961 - Service Pack
                           [39]: KB925876 - Update
                           [40]: KB925902 - Update
                           [41]: KB926122 - Update
                           [42]: KB927891 - Update
                           [43]: KB929123 - Update
                           [44]: KB930178 - Update
                           [45]: KB931784 - Update
                           [46]: KB931836 - Update
                           [47]: KB932168 - Update
                           [48]: KB933854 - Update
                           [49]: KB935839 - Update
                           [50]: KB935840 - Update
                           [51]: KB935966 - Update
                           [52]: KB936357 - Update
                           [53]: KB832880 - Update
                           [54]: KB872769 - Update
                           [55]: XpsEPSC
Network Card(s):           1 NIC(s) Installed.
                           [01]: Broadcom NetXtreme Gigabit Ethernet
                                 Connection Name: Server Local Area Connection
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.0.10
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Okay, that helps... you've installed Windows Server 2003 SP2 without first studying the release notes and known issues.  A Service Pack is a MAJOR upgrade that should always be applied, but only after you understand how it's pack of fixes will affect your server.  SP2 has about 80 different items that it changes, some are minor and some a bit more extensive.  There are some common known issues with how it reacts on an SBS, and then there may be other issues based on other things running on your server or what your specific hardware configuration may be.

You'll find a comprehensive list of all the issues and fixes for SP2 on SBS here:  http://sbsurl.com/sp2

Jeff
TechSoEasy
0
 
dreamcreativeAuthor Commented:
Thanks for the link, I'll go through it and see what i can do. Unfortunately the server was never installed with a real implementation plan and now I am left with trying to tidy it all up. Hopefully I can find the necessary fixes to get it all running properly.

Thanks very much for your assistance.
Matt
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
SBS's don't really need a "real" implementation plan.  But they DO need to be installed according to their documentation which is actually a pre-configured implementation plan.  There are a few worksheets that are part of the Getting Started Guide  that can be filled out which would help as well.  See:  http://sbsurl.com/start

Jeff
TechSoEasy
0
 
dreamcreativeAuthor Commented:
I've just tried the appropriate fixes on that blog but problem still exists. Do you think it would be worthwhile uninstalling SP2 to see if I can get things running without it? Considering the company only has a small number of people in the office I was wondering whether it needs SP2 at all.

Thanks
Matt
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.