i've screwed up remote access and can't get in

Discussion in 'Windows Small Business Server' started by TBW, Aug 19, 2007.

  1. TBW

    TBW Guest

    In the rushed process of unjoining and then rejoining a a laptop to my SBS
    network I have apparently killed remote access. I'm sure this had something
    to do with my mucking around with the security settings in IIS so that I
    could access the "ConnectComputer" functionality.

    Unfortunately, I did not realize this unitl sitting in the airport lounge
    this morning waiting for aconnecting flight about a thousand miles from the
    server. Noticed that my BlackJack stopped synching last night at home, but
    just thought I'd mucked up my individual account. Now I realize that I (nor
    anything else) can get on remotely. Typing the usual mail.domain.com/remote
    gives me the following:

    HTTP Error 403.6 - Forbidden: IP address of the client has been rejected.
    Internet Information Services (IIS)

    Will a simple re-running of a Wizard fix my boo-boo? If so I can "get a
    body" to the server console and have them run it with my coaching them over
    the phone. I'm not scheduled to be home again for almost 2 weeks. I MAY also
    be able to VPN into my network (albeit into a different subnet) later today,
    but I'm not sure I'll be able to get to my SBS that way either, especially
    since I seem to have locked her up tighter than dick's hatband.

    Thanks in advance!
    TBW, Aug 19, 2007
    1. Advertisements

  2. TBW

    Iakov Guest

    HTTP Error 403.6 - Forbidden: IP address of the client has been rejected.
    This magic often happens after meddling with the configuration under IIS, as
    you admit. The default configuration lists the address space permitted AND
    denied. Have somebody read that screen to you - the IIS screen where you
    mucked up - and verify that the configuration makes sense. I.e., verify that
    the permitted and denied address spaces make sense for your network.

    If you mucked up somewhere else, other than the particular screen I am
    thinking of, then wait for suggestions from others here.
    Iakov, Aug 19, 2007
    1. Advertisements

  3. Hi,

    To isolate the root cause, please let me know:

    1. Do you mean you're not able to access RWW
    (http://public.domain.name/remote) from an external computer?
    2. What about an internal computer (http://servername/remote)?
    3. What about OWA and other web sites?
    4. Did the problem happen on all clients or only a specific client?

    Please check:

    1. Run inetmgr.
    2. Expand Servername/Web Sites/Default Web Site/Remote.
    3. Right click Remote and click Properties.
    4. Click Edit under "IP address and domain name rsetrictions".
    5. Make sure that "Granted access" has been selected and there's not

    If the problem persists, please also gather the following info:

    [Note] Please use the following subject for your e-mail: SBS Public
    Newsgroup: i've screwed up remote access and can't get in (40221223)

    Info 1. IIS Metabase.

    1. Download the IIS Resource Kit tools from the following page:
    2. Install it, run MBExplorer (Metabase Explorer)
    3. Right click the "LM" node and choose "Export to file".
    4. Specify a file name, specify the password and finish the export.
    5. Send the file and the password to .

    Info 2. Public Domain Name.

    Please send your Public Domain Name to me for a test.

    Thanks for your time and I look forward to your update.


    Bill Peng
    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security
    The public newsgroup only focuses on SBS related technical issues, for
    other Microsoft products, we recommend you to post to appropriate newsgroup
    to get most qualified responses.

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive notification. 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 PSS 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.

    Bill Peng [MSFT], Aug 21, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.