Re: Help with non-standard SBS setup



Frank, can you give us an overview of VMWare's better networking for this
scenerio?

--
/kj
"Frank McCallister SBS MVP" <anonymous> wrote in message
news:CE760667-4A47-4F33-ACA3-D7090CB3D14D@xxxxxxxxxxxxxxxx
Use VMWare instead of Virtual Server for better networking to those
Virtual XP WS's

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC

<bweaverusenet@xxxxxxxxx> wrote in message
news:1165864837.765451.32760@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Okay. Looks like 2 GB is around $330.

It's got an 80GB 7200 rpm SATA drive with basically SBS 2003 and this
one app on it. I'll check the exact free space later. How much is "lots
of disk" and how fast is fast?

Thanks.

kj wrote:
Yeah that (XP) works, but use Virtual Server 2005 and you'll still need
to
triple or quadruple the memory.

How's the disk space? Each VM (virutal) drive eats lots of disk and
likes it
fast too.
--
/kj
<bweaverusenet@xxxxxxxxx> wrote in message
news:1165863568.133670.316040@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I believe it's 1GB, though upgrading RAM is no biggie. Are you talking
about Virtual PC and installing Server 2003 in that image?

Interesting option. Hadn't thought of it. Still requires more expense
than I'd hoped... but interesting.

What about running several XP Pro images in VPC, and allowing users to
remote into them? I have several XP Pro licenses...

On Dec 11, 12:07 pm, "Steve" <newsgr...@xxxxxxxxxx> wrote:
How much RAM in your server? Some folks have had success in setting
up a
virtual 2003 server running in TS application mode on the SBS box if
it
has
enough RAM (probably 3-4 GB). Of course you still have the expense of
the
additional server software and TS CALs.

<bweaveruse...@xxxxxxxxx> wrote in
messagenews:1165855909.286735.243130@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Hi, I need some help getting a non-standard environment working.

Our church has no building at the moment, and several (10-20)
people
must work remotely from their various home computers, mostly
running xp
pro and home. Probably not more than three to five concurrent
users.
The common server is a dual-Xeon PowerEdge 1800 w/ Win 2003 SBS
sitting
next to my XP Pro system, both behind my router and cable modem.
Anyway, these people need to share files and some need to run a
specific application. This application has a network mode that runs
from a mapped drive, but over VPN this is unusably slow. So I
installed
it on the server desktop and it runs acceptably through Remote
Desktop
over VPN like that. [I hear your screams now]

Terminal Services / Remote Desktop won't work on SBS except for
admins.
And I've managed to get RWW working, but to get the "Connect to
Server
Desktops" link the users apparently need to be domain admins.

I understand that users shouldn't remote into the server and run
apps,
etc. It's a bad idea. On the other hand, I don't see a way around
it
without building out a full and proper network in my house.

Given that I accept the danger, is there a way to create some
domain
admins and then narrow their permissions? Or is there a way to
create a
non-admin user that *does* have access to "connect to [the] server
desktop?" This would be a short-term solution until the network
moves
into an actual building with a proper network.

Over in the terminal services group I got some suggestions of
adding a
2003 Standard box with enough TS CALs (or stocking up on XP Pro
boxes)
and allowing them to log on that way. However, I'd *really* like to
use
the system we have, since the server is awfully beefy just to route
a
few users (literally) around to other boxes. (Even assuming we had
the
cash to blow on more servers and OS licenses. :-)

If if matters: remote users --(vpn)-->dyndns-->|myhouse|-->cable
modem-->router-->sbs server and xp pro box. I've got ports 80, 443,
1723 all routed to the sbs server.

Or, is there another solution that I'm overlooking?

Thank you. -bill




.



Relevant Pages

  • Re: Server/Network setup question
    ... Let's keep the P2P network and the ... SBS server's internal NIC to the switch. ... The internal NIC of the SBS server will default to 192.168.16.2 during the ... you change the IP of the rented printer to 192.168.16.8 (or some ...
    (microsoft.public.windows.server.sbs)
  • Re: DHCP Fails on Authorized Server
    ... The DHCP shutdowns may because the SBS detects another DHCP in network. ... How to configure Internet access in Windows Small Business Server 2003 ... On the Connection Type page, click Broadband, and then click Next. ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with Permissions
    ... And SBS server is only take ... the role of an internal server. ... they are all configured to connected to internal network. ... g. Run the Configure Email and Internet Connection Wizard on SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server & a WiFi Hotspot (some DHCP for good measure too)
    ... ISA2k4 is currently not supported on SBS ... To review - you have LAN clients that you want to have ... card for your server. ... > network with 5 client computers. ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN Connection Problems
    ... This newsgroup only focuses on SBS technical issues. ... | Subject: RE: VPN Connection Problems ... you can not ping anything on the SBS network from WAN. ... |> FQDN of the SBS server on the Web Server Certificate page. ...
    (microsoft.public.windows.server.sbs)