Re: Workgroup Security Help Needed.

Tech-Archive recommends: Speed Up your PC by fixing your registry

Thanks again, this was of great help...
--
Kind Regards,
Mike


"Steve Winograd [MVP]" wrote:

> In article <975DFD03-8F0D-4050-A84D-CBDB4AAAC3EF@xxxxxxxxxxxxx>,
> "Michael A. Middei" <MichaelAMiddei@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >> >Please help solve this workgroup security problem…
> >> >
> >> >My network consists of the following;
> >> >A small network with 2 separate workgroups, workgroup A and workgroup B,
> >> >both workgroups have 6 computers each, two of the 6 computers are Windows XP
> >> >Pro Ser. PK. 2, two are Windows XP Home Edition Ser. PK. 2, and the last 2
> >> >have Windows 2000 Ser. PK. 4.
> >> >
> >> >THE IDEAL END RESULT - any computers in Workgroup A cannot access computers
> >> >in Workgroup B, and vise versa. Is this possible? Is it possible to isolate
> >> >the Workgroups from being able to access one another while sharing a
> >> >Broadband Connection through the router?
> >> >
> >> >Computers and hardware are as follows;
> >> >
> >> >1. DSL Modem
> >> >2. Linksys 4 port cable/DSL router model BEFSR4.
> >> >3. 12 port hub.
> >> >4. 9 Dell desktop PC’s and 1 Dell 9200 laptop.
> >> >
> >> >Here is the current issue;
> >> >The entire C drive on all machines are Shared within their own Workgroup,
> >> >the current problem is that all machines in both Workgroups can see one
> >> >another…
> >> >
> >> >How can I isolate the 2 Workgroups from seeing or accessing one another?
> >>
> >> Workgroups don't provide any type of security or access control. A
> >> computer in any workgroup can access a computer in any other workgroup
> >> on the same physical network.
> >>
> >> The simplest solution is to get two more broadband routers to set up
> >> independent and isolated physical networks that share a common
> >> Internet connection:
> >>
> >> 1. Connect the Workgroup A computers to the first new router.
> >> 2. Connect the Workgroup B computes to the second new router.
> >> 3. Connect the WAN (Internet) port of each new router to a LAN port of
> >> the original router.
> >>
> >> I use that setup at home. The first network is for my own computers.
> >> The second network is for working on a customer's computer that might
> >> have viruses and worms and needs to be isolated while using the
> >> Internet.
> >>
> >> Broadband routers usually have only four LAN ports, so you'll probably
> >> need to get another hub or switch with at least 6 ports.
> >
> >Hi Steve,
> >Thanks so much for your reply, sounds like a winner...
> >
> >2 Additional Questions:
> >
> >1. Original routers IP address is 192.168.1.1, do the 2 new routers get
> >changed to say 192.168.1.2, and 192.168.1.3 so the don’t conflict with each
> >other.
> >
> >2. Original router is doing DHCH, do the 2 new routers also do DHCH for
> >their own computers or must I disable the DCHP in new routers?
> >
> >Kind Regards,
> >Mike
>
> You're welcome, Mike. The new routers must use a different subnet
> than the original one. For example, if the original uses 192.168.1.1,
> change the new ones to 192.168.0.1 (subnet mask 255.255.255.0 on all).
> Since the new routers are completely isolated from each other, it's OK
> for them to have the same address.
>
> All three routers should do DHCP. The original one assigns IP
> addresses to the WAN (Internet) ports of the new routers. The new
> routers do DHCP for their own computers.
>
> An advantage of this setup is that you don't have to change settings
> on any of the computers.
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see. I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com
>
.

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)
  • 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)
  • Re: Problem with browsing the network for certain workgroup
    ... For Win98 this feature is on separate NetBIOS tab, ... workgroups browses his own workgroup as entire network without any problem. ... JUHID), from where it's impossible to browse entire>> network, and other computers can't browse computers from those ...
    (microsoft.public.windowsxp.general)