Re: file and printer sharing with non-domain members

Tech-Archive recommends: Fix windows errors by optimizing your registry

BTW, have you been to techsoup to see what xppro upgrades cost? They're
$8.00 each.



--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Paul Pedersen" <nospam@xxxxxxx> wrote in message
news:uktvOL$YGHA.3400@xxxxxxxxxxxxxxxxxxxxxxx

Thank you.

"Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
wrote in message news:ecYf2d2YGHA.3532@xxxxxxxxxxxxxxxxxxxxxxx
One of the biggest differences for networking features between Windows XP
Professional and Windows XP Home Edition is the lack of domain membership
support in Home Edition.

Understood.


A Windows XP Professional computer can join a domain and function as a
domain member. Domain membership extends the benefits of distributed
security to the Windows XP desktop, enabling users to easily access
domain resources. It also lets the user share resources with other users
and authenticate those users against the domain rather than require
individual accounts on the local computer.

By contrast, computers running XP Home Edition cannot be domain members,
although they can access resources on a domain member in the same way
workgroup members running other Windows platforms can access domain
resources. They can connect to and use network file and printer shares,
provided they have a valid account in the domain.

Does not setting Print access to Everyone (on the printer sharing tab)
accomplish this? I thought Everyone meant "everyone who is connected to
the network". Is that a mistaken assumption?



Therefore, you need to set up user accounts on the SBS, and allow them
access to the resources (files, folders, printers, etc.). When a user
tries to access a resource, he is going to have to authenticate (prove
who he is). With XP Pro, the user is authenticated at logon, and these
credentials are all he needs. With XP home, the user may get repeatedly
prompted for credentials, but so long as he provides a username and
password for an account with access to the resource, it should be
availalbe.

The XP Home computers have multiple user accounts. In order for all of the
users to be able to use a printer shared by SBS, do I have to create an
account for every one of them?

What about guests, whose connection to the network may be temporary? Can
they use the printer?

Can I simply let guests and XP Home users access server resources through
the Guest account? How?

(BTW, I intend to limit access to certain server resources more
specifically through more complex permissions. Eventually, not now.)



Windows XP Professional defaults to using Kerberos for authentication.
Kerberos offers the ability to reuse authentication credentials,
providing single-sign-on capability. Although Home Edition provides
password caching just like other Windows platforms (although it's more
secure), it doesn't offer the same level of single-sign-on support
provided by Windows XP Professional.

SBS uses group policy extensively for user and computer account
configuration, including important security configurations. One of the
biggest drawbacks to the lack of domain support in Home Edition is the
corresponding lack of support for group policies. You can configure local
policies on a Home Edition computer, but the computer naturally can't
obtain group policies during domain logon because it can't be a domain
member. This means you can't apply change control or restrictions,
perform folder redirection, or accomplish any of the other feats of magic
made possible by group policies, and configured by default in SBS.

Sounds like a lot to learn... Folder redirection, for instance. I've never
heard that one before.

I have a new SBS book (SBS Unleashed, by Neale). I'd better get cracking
on it. In my free time, ha ha.





.

Relevant Pages

  • Re: file and printer sharing with non-domain members
    ... xphome on an SBS network. ... username and password as the corresponding domain user account. ... Professional and Windows XP Home Edition is the lack of domain membership ... It also lets the user share resources with other users ...
    (microsoft.public.windows.server.sbs)
  • RE: Can not view network neighborhood
    ... I am interested in accessing the resources on the ... I need to access SQL server, and a "file share" which are on ... Do I still need to VPN directly to the SBS? ...
    (microsoft.public.windows.server.sbs)
  • Re: << FYI about the Microsoft SBS community>>
    ... >> SBS consultants who freely share there expertise. ... >> needs to help the most, give the resources too. ... >> credential in the world of technology than the BTDT and everyone of YOU ... >> more about a network, more about a business, more about real technology ...
    (microsoft.public.windows.server.sbs)
  • RE: Can not view network neighborhood
    ... Welcome to SBS newsgroup. ... resources of SBS domain when connect via VPN connections. ... not access the SBS internal domain resources via file sharing. ... If you want to access the SBS internal resources via VPN connection, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2008 with Member Servers in Hyper-V
    ... Domain partner replication with two DC's and especially SBS can be tricky ... I'd configure it as a member server. ... You should NOT add additional tasks to the virtualization parent. ...
    (microsoft.public.windows.server.sbs)