Re: Remote Access

Tech-Archive recommends: Fix windows errors by optimizing your registry

denniscking wrote:
Robert,

I have a new problem. I was successful publishing the site to the internet for remote access. However, when I try to access the web server remotely in an IE browser it is not found. I neglected to tell you that SBS R2 is behind a router which I thought would be configured properly using the CEICW wizard. Now I read in another post that if SBS is behind a router, I need to configure the port forwarding settings on the router to forward port 4125 to SBS external network adapter. Is this so or did the CEICW wizard handle that for me? And if it did why cant I access the server remotely from a client using the URL assigned? Thanks for all your help.


A brief word on uPnP: don't.

It's great for configuring multiple ports dynamically for game-players,
but on a business network... well, would you trust a firewall which has
been configured to be remotely controlled by games?

Always turn off uPnP in the router and configure port forwarding
manually, then you know for sure what has been done and what hasn't.

Port 4125 is the one used to carry RDP for logging in to workstations
through RWW. If it isn't open, that won't work, but you will get the
web page itself. Port 443 is the https port, which gives you the web
page and must also be forwarded. Don't bother scanning for port 4125,
as nothing is listening on it until you tell the RWW web page which
machine you want to connect to.

I don't think you've mentioned whether the SBS has ISA running. ISA is
quite fussy about web access, and may be causing some trouble. Can you
get the RWW web page from the LAN?

One other point, but not one which you seem to have hit yet: the first
time IE connects to RWW, it needs to download an ActiveX control. The
IE security policy may stop that happening, but if so it will give you
a useful error message saying so. Because this control is needed, only
IE can be used to access RWW. On the other hand, any browser with Java
can use Outlook Web Access, so it's a bit simpler to test. The URL
is https://<FQDN>/exchange. That will confirm port 443 is forwarded,
and that ISA, if installed, is not blocking access.
.

Relevant Pages

  • Re: Remote Desktop
    ... Wireless router that I have set up to forward port 3389 to the IP address I ... If so its possible the firewall is configured to only allow Remote ... Al Jarvi (MS-MVP Windows Networking) ...
    (microsoft.public.windowsxp.network_web)
  • Re: Remote Desktop
    ... Wireless router that I have set up to forward port 3389 to the IP address I ... If so its possible the firewall is configured to only allow Remote ... Al Jarvi (MS-MVP Windows Networking) ...
    (microsoft.public.windowsxp.network_web)
  • Re: Remote Connection Issue
    ... the main reason many inidividuals went to 2003 is the RWW (remote web ... > If you want to connect to connect to the SBS server box and the LAN client ... >>through port number 3389 and a workstation on the LAN through port number ...
    (microsoft.public.windows.server.sbs)
  • Re: Accessing Multiple Desktops At Office Via XP VPN
    ... Does your router setup look something like this (just change the ... System and on the Remote page -> Remote Desktop section put a ... Remote Desktop is checked. ... > not put anything in Port Forwarding or Port Triggering? ...
    (microsoft.public.windowsxp.network_web)
  • Re: Remote desktop & Netgear router
    ... if you can connect to the PC from another PC using the "private LAN IP address" over your ... local LAN then Remote Desktop is obviously setup right and working. ... The issue then is the port forwarding on the router. ...
    (microsoft.public.windowsxp.work_remotely)