Re: Tips on setting up Remote Access
- From: "Leon Willard" <leonwill@xxxxxxxxxxx>
- Date: Tue, 28 Feb 2006 14:46:50 -0800
Merv,
Well, I guess I better roll up my sleeves and get busy!!
Thanks.
Leon
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uozku0KPGHA.1192@xxxxxxxxxxxxxxxxxxxxxxx
Running a domain is both easier and more difficult than a P2P network.
Make sure you read as much as you can first. It sounds like you have SBS
2003 installed as a domain server now. If you'r going to use the
preferred (2 NICs + router) network setup, you'll want to do that first.
If so, email (setting up Exchange or the POP3 Connector) and migrating the
current P2P user profiles to domain profiles may be your major challenges.
Migrating from a Peer-to-Peer Network to a Windows Small Business Server
2003 Network
http://www.microsoft.com/technet/prodtechnol/sbs/2003/deploy/sbs_p2p.mspx
Configure Email and Internet Connection Wizard (CEICW) Walthrough - Andy
Goodman
http://www.12c4pc.com/sbs2k3/sbs2k3-n2.htm
2 NICs + router setup diagram
http://www.smallbizserver.net/Default.aspx?tabid=266&articleType=ArticleView&articleId=76
--
Merv Porter [SBS MVP]
===================================
"Leon Willard" <leonwill@xxxxxxxxxxx> wrote in message
news:uHpzZEKPGHA.3064@xxxxxxxxxxxxxxxxxxxxxxx
Hello Merv,
Our peer-to-peer network is left over from our Win98 days, and as we
upgraded to a mix of Win98 and new WinXP machines. Even as we went to all
XP and SBS2003, it was easy to leave the peer-to-peer network as is, with
all printers and share connections in place. We didn't see any compelling
reason to join the workstations to the domain. But now that we're
contemplating remote access and other features in SBS2003, it sounds like
we now have a compelling reason. And we do have a fixed WAN IP address
for our broadband service. We also have Active Directory implemented.
It would seem to be only a matter of joining each XP Pro machine to the
domain, and upgrading any XP HE to Pro (we have licenses for that). Is it
that simple or am I overlooking additional complexities?
Leon
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23VyoMR$OGHA.3276@xxxxxxxxxxxxxxxxxxxxxxx
Hi Leon,
RWW requires that the workstations be joined to the domain and running
WinXP Pro (for remote desktop access).
Not sure why you're using a peer-to-peer connection for the LAN
computers insteaqd of joining them to the domain. Email should not be
the limiter here. If you have a broadband connection in office and even
a dynamic WAN IP address from your ISP, you can set up all SBS features
to work after you've joined all WinXp Pro workstations to the domain
(WinXP HE machines will need to be upgraded to Pro). External access
can be had by setting up a DDN (Dynamic DNS) account with a free service
such as www.dyndns.com. (Best to use SBS 2003 as it was designed).
In any event, the LAN computers to be used for remote access need to be
left on 24/7 in the office.
Another option for your current set up may be www.logmein.com Works
(relatively) securely over port 80 using a small piece of software
installed on the LAN workstation. This would work with any version of
the Windows OS on the office workstations (98, ME, XP HE, XP Pro). Each
user who needed remote access could be set up with a separate Logmein
account to access their specific office computer. Again, computers in
office must be turned on for remote access.
--
Merv Porter [SBS MVP]
===================================
"Leon Willard" <leonwill@xxxxxxxxxxx> wrote in message
news:uulewc%23OGHA.4052@xxxxxxxxxxxxxxxxxxxxxxx
Oops, maybe some complications. . . .
Our office has 14 XP workstations all running XP Pro except one of the
notebooks which is currently running Home version. The two notebooks
are carried back and forth from home. All office workstations are
turned off each night. Most other users also have home computers
running XP, and several of those would probably use remote access.
All workstations are connected to the SBS2003 domain as peer-to-peer,
and not as members of the domain. Presently, SBC provides access to
WebMail, although a connection to Exchange mailboxes would be nice.
Remote access is mainly needed to gain access to the work files on the
server. All server work files are stored under one general shared
folder which has many subfolders for projects, users, and other
on-going work.
Given these circumstances, is RWW is still a viable choice or even
possible? How about VPN?
I just received "Microsoft Windows Small Business Server 2003 -
Administrator's Companion", which seems to cover just about everything.
The only problem I have, is that it's sometimes not clear whether they
are talking about making settings on the server or settings on a
workstation.
So, once again, any help will be greatly appreciated.
Thanks -- Leon
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:OT2IljzOGHA.2088@xxxxxxxxxxxxxxxxxxxxxxx
If the notebook PC is going to be used as a LAN computer (joined to
the domain and remaining in the office), yes. If it's going to remain
outside the domain and used as a device to remotely control a LAN PC
via RWW, no.
--
Merv Porter [SBS MVP]
===================================
"Leon Willard" <leonwill@xxxxxxxxxxx> wrote in message
news:OdgO$SzOGHA.3936@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Merv,
I'm definitely going to do that. This sounds like it will make some
users very pleased.
Thanks. -- Leon
Ps - we do have one user with a new notebook PC running WinXP Home.
Will that need to be upgraded to Pro?
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:uzvxo7yOGHA.3408@xxxxxxxxxxxxxxxxxxxxxxx
Look into RWW Leon. You're going to like what you see. With a
dedicated (WinXP Pro) workstation on the LAN, a remote user can
securely log into and remotely control his office workstation from
an computer (Win98, Win2000, WinXP HE, WinnXP Pro, etc.) , anywhere
in the world that has Internet access. This is done through a web
browser like Internet Explorer. With a broadband connection at both
ends, it's almost like being right in the office. It's been the
"killer app" in SBS 2003 since it first hit the streets.
How to use Remote Web Workplace
http://www.smallbizserver.net/Articles/tabid/266/articleType/ArticleView/articleId/101/How-to-use-remote-web-workplace.aspx
Setting it up is as easy as running CEICW and selecting the RWW
service (and forwarding acouple of ports on your router to the SBS
server).
CEICW Walkthrough (Andy Goodman)
(see the Web Services Configuration screen)
http://www.12c4pc.com/sbs2k3/sbs2k3-n2.htm
--
Merv Porter [SBS MVP]
===================================
"Leon Willard" <leonwill@xxxxxxxxxxx> wrote in message
news:%238nwLyyOGHA.1532@xxxxxxxxxxxxxxxxxxxxxxx
Yes, all users have dedicated workstations in the office. Their
remote requirement is to have access to files on the server.
However, if Remote Web Workspace would give them access to files
and to their email on their workstations, that would be very
beneficial. I didn't even consider RWW and haven't looked into it
at all. Any suggestions would be great.
Leon
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in
message news:%23vVVtVyOGHA.2472@xxxxxxxxxxxxxxxxxxxxxxx
Do all the users have dedicated workstations in the office? If
so, Remote Web Workplace might be a better approach than VPN.
--
Merv Porter [SBS MVP]
===================================
"Leon Willard" <leonwill@xxxxxxxxxxx> wrote in message
news:ufvuLIyOGHA.344@xxxxxxxxxxxxxxxxxxxxxxx
Our SBS2003 is installed and working well, including Exchange,
and we are pleased with its performance. We are now ready to set
up Remote Access (VPN) and would like some tips from those of you
who have already done this. Our office has a DSL broadband
connection.
About 3-4 of our staff need to work from home occasionally,
although it's unlikely that all four would be connected at the
same time. They are all runnng XP and all have broadband
connections.
I've read the SBS2003 app notes on configuring both the server
and client settings, but have these questions:
1. Can the server be configured during regular work hours, or is
a reboot required somewhere during the process?
2. Is it as easy as the app notes seem to suggest, or are there
any 'gotcha's to watch out for?
3. We anticipate using DHCP to assign IP addresses to client
PCs - Is that preferred ?
4. Is it possible to have a modem connection along with the
broadband connection? - the app notes seem to indicate it is one
or the other, but not both.
Any tips or hints or warnings will be greatly appreciated!
Thanks.
Leon
.
- Prev by Date: Sending mail via RPC over HTTP
- Next by Date: Re: How to execute logon script / Can it be a poison pill?
- Previous by thread: Sending mail via RPC over HTTP
- Next by thread: Re: How to execute logon script / Can it be a poison pill?
- Index(es):
Relevant Pages
|
Loading
