Re: VPN user unable to browse domain shares

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

From: Todd J Heron (todd_heron_no_spam_at_hotmail.com)
Date: 12/13/04

  • Next message: Marco Singer: "Re: NetLimiter does not work on WS 2003" 
    Date: Mon, 13 Dec 2004 03:46:04 -0500

    Let me correct myself. I said: a computer account in Active Directory has
    no direct correlation with the appearance of the browse list as displayed by
    Network Places. Obtaining access into each of the computers shown in the
    browse list and enumerating it's shares does require domain membership (or a
    trust to the domain). In this case, having an actual machine account in
    Active Directory can in fact be relevant.

    This statement is wrong. A machine's workgroup or domain membership will
    effect how the Microsoft Windows Network is displayed in Network Places.
    When a machine is part of a workgroup, it will send out an announcement to
    the subnet stating it is part of that workgroup and retrieve the list of all
    other computers in the workgroup from the subnet browser responsible for
    that workgroup name. The same thing occurs when in a domain. This list
    will look different depending on what workgroup, or domain, a machine is a
    member of. In any event, access into the shared resources of any other
    machine in the workgroup or domain will then be governed by rights
    (controlled by policy), share and NTFS Permissions. See what happens when
    you post past 3:00AM and you live in the eastern time zone? :-) 

    -- 
Todd J Heron, MCSE
Windows Server 2003/2000/NT
  • Next message: Marco Singer: "Re: NetLimiter does not work on WS 2003"

    Relevant Pages

    • Re: Networks : Workgroups and Domains. How Do I Use Them?
      ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
      (microsoft.public.windowsxp.network_web)
    • Re: Network Connection Problem - Intermittent
      ... Master browser name is: SERVER ... This may occur if the workgroup name and the domain name are the different. ... Starting Computer Browser Service on one of w2k/xp computers should fix the problem. ... How to Setup Windows, Network, VPN & Remote Access on ...
      (microsoft.public.windows.vista.networking_sharing)
    • Re: 2000 server and 2000 pro network
      ... I set up accounts from the server using ... these are in a workgroup called CMT. ... but a regular user cannot login using network ... Microsoft Windows MVP - Active Directory ...
      (microsoft.public.win2000.dns)
    • Cant get at my own shared files under XP SP2
      ... I hope that you can help - I'm running Windows XP SP2, ... (And can't see other computers on the corporate ... network, but that's possibly for another day). ... I can see the workgroup, when I click on the workgroup name, I get the ...
      (microsoft.public.windowsxp.network_web)
    • Re: File Permissions, Domain Problems
      ... >> workgroup in a peer-to-peer network environment, ... You cannot locate other computers in the workgroup. ... >>> "Folder is not accessible, ...
      (microsoft.public.windowsxp.network_web)