Re: 2003 SBS server Licenses

Thanks Patrick,

I did realize that there are other methods. In fact I learned from the MS website that there is a web browser based solution that is potentially even more lightweight. What I was trying to get at was whether the Consultant was full -o- bull.

Having concluded that the answer was "yes", I was taken off the project.

Oh well, Thanks again.

JH

on 10/17/2005 12:17 AM picsinc said the following: 
John,

You can do that as well but keep in mind that must ISPs for home use limit the upload speed and direct network connection over VPN is quite challanging. The remote control method I discribed earlier will leave most of your network traffic in your office. Only the remote control commands are sent through the VPN. You do need 2 computers in this scenario to work for one connection but no additional licensing is required.

Regards,

Patrick


"John Hyde" wrote:


Thanks Patrick. I guess I'm still confused. Perhaps you or someone will indulge my example:

My workstation, in the office, is a laptop plugged to a port replicator with an ethernet wire to the network.

I need a SBS2003 access license (CAL) to log into the server. Right?

Now, I take the laptop home. Since the firewall at the office is a Sonicwall and I have VPN enabled on the sonicwall, I start the SonicWall VPN client on my laptop and connect to the Network. Once I'm connected, doesn't the VPN link just take the place of the ethernet wire?

Do I need another License to access the server?

I realize that this is really basic stuff, but I need to know if this consultant really knows his stuff. I'm beginning to think maybe not.

Thanks,
John

On 10/14/2005 6:37 PM, picsinc wrote:

John,

That is just one of many ways you can work remotely. Also VPN itself is just the technology to access your private network using the internet and once you have access to your private network, how you log on to the server and access the resources and the licensing that goes along with that is another story. Terminal Server will work but does not work well on the SBS server itself and is not recommended. To add another terminal server will be quite costly including the hardware and the licensing. Another alternative is to provide the owners with desktops running XP Pro, which allows remote desktop. Then they can use any laptops (which do not even need to be joined to the domain and can be a Windows 2000, XP home or Pro) remotely with VPN to connect to your internal network. Once connected they have full control of the desktops remotely. I hope this will help.

Regards,

Patrick




"John Hyde" wrote:



I'm new to this group so please forgive if I'm posting to the wrong place. If so, perhaps a pointer?

We are building a network with Small Business Server 2003 and 5 users, But geting 10 licenses so I'm not sure how the count works out.(By "users" i mean people) The owners of the company will have laptops with docking stations that they can use at the office. Then they can take home the laptop and VPN to the firewall and work at home.

The consultant tells me that for that to work, we must also have "Windows 2000 Terminal Server" Licenses (minimum purchase 5) in order to make this work.

Can that be right? I always thought that VPN was just like another wire to the network switch and that once in, its just like being there (but with a smaller bandwidth on the network connection)

If this is right, can anyone explain why it makes sense? If I have a license for my laptop to connect to the server, what possible difference does it make where that laptop is located. IOW, why should the server care where I am?

Any thoughts greatfully received.

John


.

Relevant Pages

  • Re: [Full-disclosure] Remote Desktop Command Fixation Attacks
    ... This set of steps is redundant in many places, and it's also enormously expensive, since you're using no less than three different expensive bits of networking hardware (AP, PIX, VPN Concentrator), in addition to a bunch of x86 server hardware, windows server licenses, and at least one ISA license. ... Your computers necessarily don't have full access to your network infrastructure when they aren't logged on, so GPOs, software updates, etc can't be applied at the times you want them to be applied. ... Turning on, enabling, and implementing every possible security setting and device you think of is not defence in depth, and will probably only have two effects - your users won't use your wireless network, and you'll burn so much cash you won't have any left to spend on *useful* security measures. ...
    (Full-Disclosure)
  • Re: VPN with SBS 2003 (not R2) and DSL.
    ... Reading property value for VPN returned OK ... Reading VPN Server Name returned OK ... identical network cards. ... it seems doubtful that SBS will work properly with two NICs ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problems
    ... Note that we are able to successfully VPN into the office. ... to browse the network, RDP to the server or even ping the server. ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... on the SBS 2003 server just not sure where to go for help on it. ... Next time I'm at my home PC, I'll VPN in and see what IP info I'm getting ... client PC on your LAN, you should be able to do so from a remote VPN client, ... get the network path was not found. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Error 800
    ... The VPN client IP is 10.0.1.40, this is a private IP address. ... server IP address is 81.137.105.244, this is a Internet IP address. ... not test VPN connection from your perimeter network. ... SBS on your switch to make it work. ...
    (microsoft.public.windows.server.sbs)