RE: need help on this one



Hello Stephane,

Thank you for posting to the SBS Newsgroup.

Thanks for Russ's input!

>From your description, I understand that you want to know how to maintain
SBS 2K3 Standard Server remotely. If I have misunderstood your concern,
please let me know.

I think the best way for you is using RWW (https://public_IP/remote) or
Remote Desktop (RDP). SBS 2K3 includes the Remote Web Workplace to
streamline and simplify use and administration of all remote features. It
provides a single access point that users can access anytime, anywhere and
from any device. All you have to do is remember a single URL.

For detail information about Remote Web Workplace, please go to the server
box, Start -> Help and Support for detail information.

For RDP features, please read the following KB article:

White Paper: Remote Desktop Protocol (RDP) Features and Performance
http://support.microsoft.com/?id=810737

The steps for you to do so, please see:

1. You can contact no-ip to assign you a dynamic DNS (No-IP.com is a
dynamic DNS service provider).

Due to your Router has dynamic IP address, you need to have a dynamic DNS.
The dynamic DNS service does not change anything in the router, it just
updates your dynamic DNS domain name to whatever your current IP address
from your ISP as it changes.

2. Configure TCP ports.

As you mentioned, you have a router in front of your SBS server, make sure
the inbound TCP port 4125 is opened (all traffic on that port being
forwarded to the SBS server).When you connect to RWW, the HTTPS protocol
with port 443 is used. However when you try to connect to client desktops
or server desktops, the SBS server tells the clients to initialize a
connection on port 4125. If the connection is establishes the server will
deliver the terminal service connection to the destination computer on the
normal Terminal Service port 3389. This is a by-design in RWW

If you have already turned on the port 4125, the issue still exists, the
issue can occur if certain process running on the SBS server has assumed
the port 4125. For detailed information and resolution, please read the
following KB article:

886209 Users cannot connect to remote desktops by using the Windows Small
http://support.microsoft.com/?id=886209

3. Set up RWW or RDP on your workstation.

a) First of all, you need to have a domain account for you to log in the
RWW and RDP remotely. I assume you have already a domain account. If no,
please go to Server Management\Standard Management\Users, click the Add a
User to run the Add User Wizard.

b) If you are using Windows XP system, go to Start\All Programs
\Accessories\Communications\Remote Desktop Connection, and enter the
External IP address in the blank. For more information, please see:

Remote Desktop in Windows XP
http://www.microsoft.com/windowsxp/remotedesktop/

For Windows 2000 operation system, you need to download RDP 5.0 protocol to
have the Remote Desktop feature. To download the software, please see:

Windows XP Remote Desktop Connection software [XPSP2 5.1.2600.2180]
http://www.microsoft.com/downloads/details.aspx?familyid=80111f21-d48d-426e-
96c2-08aa2bd23a49&displaylang=en

Hope this information helps. If anything is unclear, please feel free to
let me know. I am looking forward to hearing from you!

Best regards,

Brandy Nee

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

.



Relevant Pages

  • RE: Port Forwarding With 2 NIC Configuration
    ... Can SBS do 1-to-1 Natting? ... > and incoming/outgoing port, ... > automatically redirected from the SBS server to port 81 of the internal ... > Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • RE: ISA access rules, help
    ... please let me know whether you're using ISA 2000 or ISA 2004 ... (SBS SP0 or SBS SP1). ... the ISA server will not be used as a proxy server. ... Since SBS already used port 80, ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA Problem
    ... Firewall and publish your OWA to internet. ... Click Start on your SBS server, ... the appropriate port should be forwarded. ...
    (microsoft.public.windows.server.sbs)