VPN vs. RWW in SBS 2003 Premium
|
From: Mike in Nebraska on 11 Dec 2009 15:03 Looking for advice on how best to handle the following situation: One of the office computers will be moved to a telecommuter's home, and we need it to act as if it's still part of the LAN. There's no budget. Do we use VPN or RWW? I know that RWW is much better than VPN; but, without a computer to remote into, how else can the tele-worker be part of the LAN? -- Mike Webb Platte River Whooping Crane Maintenance Trust, Inc. a conservation non-profit (501 (c)(3)) organization Wood River, NE
From: Lanwench [MVP - Exchange] on 11 Dec 2009 15:10 Mike in Nebraska <Mike_in_Nebraska(a)newsgroup.nospam> wrote: > Looking for advice on how best to handle the following situation: One of > the office computers will be moved to a telecommuter's home, > and we need it to act as if it's still part of the LAN. There's no > budget. Do we use VPN or RWW? > > I know that RWW is much better than VPN; but, without a computer to > remote into, how else can the tele-worker be part of the LAN? VPN, but unless you're going to set up a site-to-site VPN this probably isn't going to work well at all and you will not be able to manage his workstation. What are the actual requirements? Why does it need to act as though it's still part of the LAN (and what does that mean, specifically)? Ideally I'd say a Terminal Services or Citrix box is in order here. It's not inexpensive, though, so the alternative would be to get him his own cheap and cheerful home PC which is *not* part of the domain and let him use RWW to get to his desktop in the office via RDP.
From: Mike in Nebraska on 11 Dec 2009 15:43 Well, the worker is (probably) me. The economy is forcing hard times for our nonprofit so I'll probably have to get a new job, but they can afford to pay me P/T to manage the network, and do some other minor work. The assets I'd need to get to are: shared folders on the server, and the SharePoint sites (MOSS). I figured it's be efficient, time-wise, if I could act as if I was still on-site rather than RWW'ing into each server/computer to get what I need. As the one and only IT guy, I could vouch for the security actions of the user (me), but am still quite concerned about VPN. Mike > > VPN, but unless you're going to set up a site-to-site VPN this probably > isn't going to work well at all and you will not be able to manage his > workstation. What are the actual requirements? Why does it need to act as > though it's still part of the LAN (and what does that mean, specifically)? > > Ideally I'd say a Terminal Services or Citrix box is in order here. It's > not inexpensive, though, so the alternative would be to get him his own > cheap and cheerful home PC which is *not* part of the domain and let him > use RWW to get to his desktop in the office via RDP. >
From: Lanwench [MVP - Exchange] on 11 Dec 2009 15:53 Mike in Nebraska <Mike_in_Nebraska(a)newsgroup.nospam> wrote: > Well, the worker is (probably) me. The economy is forcing hard times > for our nonprofit so I'll probably have to get a new job, but they > can afford to pay me P/T to manage the network, and do some other > minor work. The assets I'd need to get to are: shared folders on the > server, and the SharePoint sites (MOSS). I figured it's be > efficient, time-wise, if I could act as if I was still on-site rather > than RWW'ing into each server/computer to get what I need. As the > one and only IT guy, I could vouch for the security actions of the > user (me), but am still quite concerned about VPN. > Mike Sorry to hear about this. You can use VPN, sure, but it's not going to be just as though you were in the office - I generally don't even join 'home-worker' PCs to the domain unless there's a site link set up between the two networks. All the server admin you can do via RDP to the server. If they want you to do the work super-efficiently they should leave a PC available for you to remote into, I'd say. > >> >> VPN, but unless you're going to set up a site-to-site VPN this >> probably isn't going to work well at all and you will not be able to >> manage his workstation. What are the actual requirements? Why does >> it need to act as though it's still part of the LAN (and what does >> that mean, specifically)? Ideally I'd say a Terminal Services or Citrix >> box is in order here. >> It's not inexpensive, though, so the alternative would be to get him >> his own cheap and cheerful home PC which is *not* part of the domain >> and let him use RWW to get to his desktop in the office via RDP.
From: Mike in Nebraska on 11 Dec 2009 16:11
Thanks, Lanwench. I like your idea and will push to have the PC I normally use set aside for me to remote into. I've had it for about 5 years and I know it inside-and-out. "Lanwench [MVP - Exchange]" <lanwench(a)heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message news:%23YaRVTqeKHA.1824(a)TK2MSFTNGP04.phx.gbl... > Mike in Nebraska <Mike_in_Nebraska(a)newsgroup.nospam> wrote: >> Well, the worker is (probably) me. The economy is forcing hard times >> for our nonprofit so I'll probably have to get a new job, but they >> can afford to pay me P/T to manage the network, and do some other >> minor work. The assets I'd need to get to are: shared folders on the >> server, and the SharePoint sites (MOSS). I figured it's be >> efficient, time-wise, if I could act as if I was still on-site rather >> than RWW'ing into each server/computer to get what I need. As the >> one and only IT guy, I could vouch for the security actions of the >> user (me), but am still quite concerned about VPN. >> Mike > > Sorry to hear about this. You can use VPN, sure, but it's not going to be > just as though you were in the office - I generally don't even join > 'home-worker' PCs to the domain unless there's a site link set up between > the two networks. All the server admin you can do via RDP to the server. > If they want you to do the work super-efficiently they should leave a PC > available for you to remote into, I'd say. >> >>> >>> VPN, but unless you're going to set up a site-to-site VPN this >>> probably isn't going to work well at all and you will not be able to >>> manage his workstation. What are the actual requirements? Why does >>> it need to act as though it's still part of the LAN (and what does >>> that mean, specifically)? Ideally I'd say a Terminal Services or Citrix >>> box is in order here. >>> It's not inexpensive, though, so the alternative would be to get him >>> his own cheap and cheerful home PC which is *not* part of the domain >>> and let him use RWW to get to his desktop in the office via RDP. > > > |