Announcement

Collapse
No announcement yet.

Trying to get Remote Web Workplace working

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Trying to get Remote Web Workplace working

    Hi,

    We are running Windows Small Business Server as DC (Active Directory) and Windows Server 2003 as File and Print Server. Both servers have Novell Client installed (there is a Novell server on the LAN as well).

    I need to allow a supplier in New Zealand to access the File and Print Server to check out some software setup issues. After a lot of searching of the web in general and Petri in particular it seems that Remote Web Workplace might be the way to go. So I fired up IE, and keyed in https://domain-name/remote.

    Now, if I try and login as a normal user I get "You are not authorised to access this web page"
    Checking out the help for remote access it tells me "To access the Remote Web Workplace, users must be members of the Remote Web Workplace Users or Domain Admins Security Group"

    But I can't find a Remote Web Workplace Users Security Group anywhere in AD. Is this group supposed to already exist or do I need to do something to set it up?

    If I try logging on as a Domain Admin I get

    Server Error in '/Remote' Application.
    --------------------------------------------------------------------------------

    Runtime Error
    Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the

    application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server

    machine.

    Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a

    "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its

    "mode" attribute set to "Off".


    <!-- Web.Config Configuration File -->

    <configuration>
    <system.web>
    <customErrors mode="Off"/>
    </system.web>
    </configuration>


    Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the

    application's <customErrors> configuration tag to point to a custom error page URL.


    <!-- Web.Config Configuration File -->

    <configuration>
    <system.web>
    <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
    </configuration>



    and I'm stuck as my knowledge of HTML and web configuration is pretty close to zip.

  • #2
    Re: Trying to get Remote Web Workplace working

    Installation of Novell client on MS OS isnt supported and doesnt recommanded - particular on a DC.
    Also, there is no need to use Novell server due the fact that it do the same thing as Win 2003.
    Using Novell client etc. can lead to a strange problems etc.
    Also, the problem isnt from the TS side from my point of view, but IIS settings...

    Regards,

    Yuval
    Best Regards,

    Yuval Sinay

    LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

    Comment


    • #3
      Re: Trying to get Remote Web Workplace working

      Hi Yuval,

      It would be ironic if Novell Client were causing the problem. We are in the process of changing to a pure Windows 2K3 environment and the supplier wanting access is trying to check that his app, currently on the Novell box, will run under Windows without problems.

      Also ironic that I tried RWW first as its touted as a no-brainer solution for dumb admins. "That's for me" I thought But now I have no idea what's wrong.

      If it is something to do with IIS settings can anyone get me started on how to diagnose the problem?

      All the machines are behind a router - D-Link DI-804HV. Are there any settings on the router that could be causing problems? I checked and couldn't see anything but ....

      Should I give up and try VPN instead?

      Comment


      • #4
        Re: Trying to get Remote Web Workplace working

        1. If the problem occur when you try to access http://servername/exchange from
        the LAN, then there is no issue with the firewall/router.

        2. Novell client on DC/PC etc. isnt support.

        3. There should be "Remote Web Workplace" group. You may need to search
        it via the console.


        http://www.microsoft.com/technet/pro.../chapter4.mspx
        Best Regards,

        Yuval Sinay

        LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

        Comment


        • #5
          Re: Trying to get Remote Web Workplace working

          Hi Yuval,

          Okay, some updates

          1) From either inside the LAN or from home I can enter https://domain-name/exchange and access my mail via OWA. No problems

          2) From either inside the LAN or from home if I enter https://domain-name/remote I get the Server Error in '/Remote' Application message (In my first post I said I only got this when logging on as Domain Admin. That's not true. Its for any user).

          3) I get the same error if I try https://server-name/remote from inside the LAN

          4) There is definately no group, either distribution or security, called "Remote Web Workplace". I have the server console open in front of me as I type this. There are only 41 groups and "Qld Operators" is followed immediately by "Server Operators". This leads me to suspect something was skipped when the server was set up.

          We are planning to get rid of Novell but this can't happen until new Windows server is purchased. Meanwhile, for what its worth, Novell Client hasn't caused me any grief when I connect from the LAN using Remote Desktop.

          Thanks for giving your time to help with this.

          Comment


          • #6
            Re: Trying to get Remote Web Workplace working

            In case of missing groups etc. I recommanded to reinstall the SBS from 0.
            Also, I recommanded to move to regular Windows 2003 domain and not
            SBS.
            Best Regards,

            Yuval Sinay

            LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

            Comment


            • #7
              Re: Trying to get Remote Web Workplace working

              I'm very reluctant to try reinstall of SBS on the DC when I don't really know what I'm doing. Changing from SBS to full W2K3 is a management decision not up to me.

              While looking at the "To Do List" on the DC I saw the "Configure for Remote Acess" box was unchecked. Reading through the help files it talks about both RWW and VPN, leaving me confused. Reading the old forums on Petri I got the impression that RWW was an alternative to VPN but the server documentation appears to imply that VPN is a prerequisite for RWW. Can anyone unconfuse me on this?

              Giving the wizard a trail run it only talks about VPN and not RWW at all.

              Take pity. The more I read up on this the more confused I get.

              Comment


              • #8
                Re: Trying to get Remote Web Workplace working

                I try to reinstalled .Net Framework 2.0 but that did not work. Also to run the Internet setup Wizard. Help ??

                Comment


                • #9
                  Re: Trying to get Remote Web Workplace working

                  I have the fix. You must install .net 2.0 reboot the server. Open IIS and look for the Default web site and look for "remote" and right click and select properties and look for th asap.net tab and change it to version 2.0 and select apply wait. Browse the folder and you should be able to log in.

                  Comment

                  Working...
                  X