Re: Lesson learned for Remote Web Access

From: Javier Gomez [SBS MVP] (javier_gomez_at_remove.this.engineer.com)
Date: 02/23/04 

Date: Mon, 23 Feb 2004 09:14:49 -0500

Cool! Thanks for the heads up... I'm glad you solved your issue.

There is always a tendency of blaming our setup when something goes wrong...
and sometimes the problem is not in the SBS box. I had a similar problem
with a Zyxel ADSL router-> I created a "DMZ" and it just forwarded like 5
ports. The inteface of that routers is the worse thing I have ever seen...
the worse part was that the interface to forward ports was hidden (and it
had a strange name like SOA - Single User Account). I spent like 2 days
googling and messing with the router to find how to do it! 

-- 
Javier [SBS MVP]
<< SBS ROCKS !!! >>
"Attila Csokai" <acsokai-nospam@yahoo.com> wrote in message
news:O$C%23yTh%23DHA.452@TK2MSFTNGP11.phx.gbl...
> I saw various posts (including mine) with problems using RWW or
configuring
> it. Well it took me a week but I figured out why I could not connect to
the
> server via the Remote Web Workplace, but locally on my network via
> http://servername/remote was not a problem.
>
> No matter what I tried initially, I could not get it to work, but here is
> what I did over the week to finally get it.
>
> I opened the relevant ports on the router as suggested on this board and
in
> the SBS help files, but eventually I just ran the UnPNP on my router which
> discovered the ports SBS needed open.
>
> However, despite all this www.GRC.com ShieldsUp still reported all my
ports
> to be in STEALTH mode and I could still not access my server via RWW, so
> figured something must have been still blocking them.
>
> I was suspecting the Verizon DSL modem (CSU/DSU really) to be at fault and
> finally figured out that by
> typing 192.168.1.1 in the browser would access the modem. I had to login
> using my Verizon username and password.
>
> Important Lesson: Do not change the modem's IP address, even if its on a
> different subnet then your SBS. I had to re-run the Verizon setup CD to
> reconfigure the modem.
>
> On the modem's setup page, there is a section for port forwarding. Even
> though I first asked it to forward all traffic to the router, it did not
> work, so I manually
> setup port forwarding to the router for each relevant port SBS needed.
>
> It seems simple now that I figured out. This last step did the trick.
Right
> now, I am at work, using RWW to access my SBS at home.
>
> This was a huge accomplishment in my confidence trying to sell SBS to my
> clients!
>
> Thank you all for the help!
>
> Attila
>
>
>
>
>
>

Relevant Pages

  • Re: Remote web workplace wont work
    ... Opening the ports isn't the right approach. ... VPN configuration on the SBS is fine, ... remove the router. ... >> If it is working inside your network, you will have to check the router ...
    (microsoft.public.windows.server.sbs)
  • Re: RDP and Terminal service
    ... you still need to open the necessary ports on your router. ... This server only has one nic. ... >>> SBS. ... >>>>> Henry and Adam used to suggest me to configure the ports and RRAS. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: DHCP server and netgear router problems
    ... default so you can access the router setup at ... I am currently using the old hardware setup but it is important that it is ... >> the existing setup instead of installing the SBS DHCP, ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW interal not external
    ... a soho gateway router and utilize RRAS is the least expensive ... Les Connor [SBS Community Member - SBS MVP] ... or the ISP is blocking ports. ... >>> Outlook via the Internet ...
    (microsoft.public.windows.server.sbs)
  • Re: Hardware VPN: 2 NICS --> 1 NIC - Non-Profit Needs HELP!
    ... VPN Router. ... I DMZed the Server and all web services are working. ... I'm by no means an expert on SBS, but been in networking for years. ... setup a site-to-site VPN with a new Club we opened. ...
    (microsoft.public.windows.server.sbs)