RE: Remote Access

From: Robert King [MSFT] (a-rking_at_online.microsoft.com)
Date: 03/02/04 

Date: Tue, 02 Mar 2004 19:47:08 GMT

This issue can be solved With Remote Web Workplace. Remote web workplace
needs port 4125 open on the firewall. Here is a link to a webcast that
should explain it for you.
http://support.microsoft.com/default.aspx?scid=kb;en-us;833983
Briefly, with RWW you access the companyweb from the internet, then connect
to computer(s) internally after logging on to the link for connecting to
remote computers. If you use XP machines as the clients inside your
network,the machines will automatically be added under the link for
connecting to, on the web site. Before using this feature, you will want
to ensure that you have all of your Microsoft updates complete and have
enabled remote connectivity to the XP machines.

http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us
/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmb_t
ol_xhiw.asp

Robert King
Microsoft Product Support Specialist
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
|
| Before joining my clients to my SBS Domain the setup I was
| using was to put 2 network cards in a PC. One had a
| static public IP with no gateway information and the other
| was assigned a private IP from the DHCP server, I only
| have 2 clients needing this setup and I thought it would
| be the easiest way to solve RDP access for them. The
| public IP used the firewall and now after joining the
| domain I do not have an advanced tab on my XP machines,
| meaning no firewall.
|
| Now they are having problems connecting and also I feel a
| little uneasy with out a firewall up on the public NIC.
|
| What is the preferred way to solve this issue, most times
| they use dial up from an offshore oil rig, connecting to
| the Internet, then to the server and then to the client
| seems a little much for a modem connection. It is against
| company policy to have a modem connected to a server.
|

Relevant Pages

  • Re: OMA not working - any pointers?
    ... Therefore it is outside the firewall ... Same device worked 100% connecting to an alternative SBS2003 Standard ... David ... >> Remote Web Workplace and Outlook Web Access work flawlessly however from ...
    (microsoft.public.windows.server.sbs)
  • Re: OMA not working - any pointers?
    ... I'm personally having some issues connecting my smartphone to SBS pe sp1 ... w/isa2004 from inside my network - but that's firewall related, ... > sender, EventArgs e) ... > Remote Web Workplace and Outlook Web Access work flawlessly however from ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange, Outlook and Firewall
    ... > I have had internet clients connecting via exchange connector thru the ... > firewall at thie location before with no issue, ...
    (microsoft.public.exchange.setup)
  • Exchange, Outlook and Firewall
    ... Exchange 2003, outlook 98. ... I have had internet clients connecting via exchange connector thru the ... firewall at thie location before with no issue, ...
    (microsoft.public.exchange.setup)
  • Re: Cant logon to computer in SBS Domain..
    ... "certificate" key on the server, and I am not sure whether it is the SBS ... I think we should delete this registry key on the workstation ... Does the user can access and log on to the Remote Web Workplace? ... On the Firewall page, ensure that Enable firewall is selected. ...
    (microsoft.public.windows.server.sbs)