Re: Windows 2000 Server and XP Home Clients - Am I missing something??

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Paul, and welcome to this NG

Apart from your share issues (have you verified it is usename\password on pc
is same as domain hence only some users only able to access certain
directories), one extremely useful part of SBS2003 is connections to pc
desktops via RWW which you will not be able todo with XP home as they do not
support remote connections.




"Paul Goldman" <paulgoldman1948@xxxxxxxxxxx> wrote in message
news:TSrnf.4282$ka.2366@xxxxxxxxxxxxxxxxxxxxxxx
> The reason I posed the question in this newsgroup is that I'm planning on
> migrating to Win2K3 SBS, and need to figure out this Windows Home thing
> before I proceed.
>
> "Maxibo" <totallyanon@xxxxxxxxx> wrote in message
> news:%23uOQ76O$FHA.3316@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi Paul,
>>
>> Pcs could be in a different 'workgroup ' and they would still get on the
>> server if they knew / have a domain username and password. Being in the
>> same workgroup helps browsing in network places.
>>
>> The pcs I assume are all in the same IP range (you could have them in a
>> different IP range and with some tweaking get them to the server). They
>> are now talking on TCP. If they require a server resource it will prompt
>> for a valid Domain username and password. Initially they will be trying
>> to authenticate by computername\username which wouldn't be allowed. When
>> you change the prompt to domain\username and password you do get the
>> option to save password.
>>
>> Not being in the domain does cause this problem that there maybe regular
>> prompts for username and password because the pcs are transmitting
>> computername\username which of course are not authorised.
>>
>> Being in the domain does help maintenance of the site and saves alot of
>> issues, internet access is one area that can cause issues as they are not
>> ' ISA firewall clients ' per say and may find some sites / internet
>> usuage doesn't work properly. Unsure if putting the firewall client would
>> solve any issues as do not have any XP home in a domain..lol
>>
>> Finally, this is the Small Business Server newsgroup, more specifically
>> 2003 and you mention just Server 2000, SBS2000 is in a different NG, our
>> configurations are slightly different to plain 2000 server and if you
>> have plain 2K my mention of ISA may confuse you...lol
>>
>>
>>
>>
>>
>>
>>
>> "Paul Goldman" <paulgoldman1948@xxxxxxxxxxx> wrote in message
>> news:jJjmf.1894$pE4.527@xxxxxxxxxxxxxxxxxxxxxxx
>>>I understand that they named the workgroup the same as the domain. Isn't
>>>a workgroup named X and a domain named X 2 different entirely different
>>>things even though they are one the same network?
>>>
>>> I am also faced with the fact that the owner does not want to spring for
>>> the expense of upgrading everyone to XP Pro and joining the domain.
>>>
>>> My question is if you have an XP Home machine with a userid/password of
>>> someone that is in a domain, does the domain controller know that this
>>> is the same user? I didn't think that was possible.
>>>
>>> "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
>>> wrote in message news:u10FdhI$FHA.272@xxxxxxxxxxxxxxxxxxxxxxx
>>>> They've probably named the 'workgroup' the same as the domain.
>>>>
>>>> XP Homes can't join a domain. Upgrade them to XP Pro for the control
>>>> you need.
>>>>
>>>> Paul Goldman wrote:
>>>>> I made my first visit to a new client today. They have a network with
>>>>> a Windows 2000 Server with AD with a domain name of ARS. They have
>>>>> users and security groups defined in AD and File Shares with access
>>>>> controlled by those users and groups. "Everyone" has full access to
>>>>> all of the shares, but further down in the subdirectory tree rights
>>>>> are restricted to certain users and groups. So far so good. Here's the
>>>>> problem. All of their client PCs are running Windows XP Home edition,
>>>>> and are members of a workgroup, ARS. Since no one is logging into the
>>>>> domain, I can't figure out how certain users have rights to certain
>>>>> subdirectories on the file shares. I can see how they can map to
>>>>> drives, because of the full access for Everyone, but can't figure out
>>>>> how the server knows who is who to restrict access to the
>>>>> subdirectories. Can someone help me out? What am I missing??
>>>>>
>>>>> Thanks.
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Windows 2000 Server and XP Home Clients - Am I missing something??
    ... The reason I posed the question in this newsgroup is that I'm planning on ... > same workgroup helps browsing in network places. ... > different IP range and with some tweaking get them to the server). ... If they require a server resource it will prompt ...
    (microsoft.public.windows.server.sbs)
  • Re: Windows 2000 Server and XP Home Clients - Am I missing something??
    ... Pcs could be in a different 'workgroup ' and they would still get on the ... server if they knew / have a domain username and password. ... different IP range and with some tweaking get them to the server). ...
    (microsoft.public.windows.server.sbs)
  • Re: Workgroups and connecting to a server
    ... >I just set up a server in a workgroup. ... When 3 of the 4 computers connect to any netork resouce ... they get an Administrator prompt to login and enter ...
    (microsoft.public.windows.server.general)
  • Re: Workgroup and connecting to network resources
    ... >I just set up a server in a workgroup. ... When 3 of the 4 computers connect to a network drive ... > get an Administrator prompt to login and enter the administrator password. ...
    (microsoft.public.windows.server.networking)
  • Re: Access from Win2K server to XP desktop in a workgroup
    ... I don't think what the workgroup name is on either machine should make any ... I can access the file system of the ... > server from the XP desktop. ... > the WG\userID and PW and get the log in prompt back ...
    (microsoft.public.security)