Re: WINS server

From: Terry (it_at_REMOVETHISfloydautomatic.co.uk)
Date: 12/02/04 

Date: Thu, 2 Dec 2004 14:29:02 -0000

I have one server 2003 as the PDC for domain FLOYD, 2 NICs 192.168.1.1 &
192.168.2.1, a handfull of Win98 clients on 192.168.1.xxx with an old
workgroup name of OFFICE but running the AD client, a number of WinXPpro
clients on 192.168.1.xxx on the FLOYD domain, a WinXPpro client on the FLOYD
domain sitting at 192.168.2.248. Each server NIC is connected to it's own
100MB Switch.

All clients on the .1.xxx can browse each others shares in the FLOYD domain
and the OFFICE workgroup. They cannot see the .2.248 XP client in the
Windows Network under the FLOYD domain, but can Start|Run connect to it's
shares.

The .2.248 XP client in the Windows Network can see all the FLOYD domain XP
clients and connect to shares, it can also see the OFFICE workgroup but is
denied access to browse it. It can however connect to Win98 client shares
using Start|Run.

So how do I get to have full browsing, at least between all the XP clients
on .1.xxx and .2.xxx?

Assuming I have a spare WinXPpro machine or two to use as master browsers,
could I achieve the following? and are you saying that the domain name on
these machines == workgroup name on Win98 clients?
>You must have at least one domain-NT-class machine on
>each subnet (with same domain name as the workgroup.)
>This machine much end up as master browser for that subnet.

Regards
Terry

"Herb Martin" <news@LearnQuick.com> wrote in message
news:e$Nkb2$1EHA.1296@TK2MSFTNGP10.phx.gbl...
> "Terry" <yoo_hoo_2000@REMOVETHISntlworld.com> wrote in message
> news:uu#HVc#1EHA.1404@TK2MSFTNGP11.phx.gbl...
>> Hi Herb,
>>
>> From experience I have determined that a separate NIC and switch removes
> the
>> problem experienced by Sage users when a large amount of data is being
> moved
>> on their subnet, just move it across another subnet instead. Hence the
>> reason to have a multi-homed PDC.
>
> You made a leap (of logic) there from needing two subnets to the
> PDC needing two NICs.
>
>> I still need to be able to connect to any
>> other client on either of the subnets which Routing handles brilliantly
> for
>> WinXP clients, but is poor for Win98 and workgroups.
>
> Workgroups do not (directly) support multiple subnets.
>
> You must have at least one domain-NT-class machine on
> each subnet (with same domain name as the workgroup.)
>
> This machine much end up as master browser for that subnet.
>
>> There is also a
>> Netpilot on subnet 1 which handles all connections to the internet via a
>> non-nat router, that with a static route or two does the job.
>>
>> However it is not recommended to run WINS in this server scenario. Now I
>> have some choices, forget the older Win98 machines and the workgroup
> knowing
>> that they are to be upgraded sometime in the near future, or slap a WINS
>> server on the network. I'm just trying to get a handle on the cost and
> work
>> involved to see if it is justified in doing. At this moment I see no
> reason
>> to add a WINS server due to cost even though I have a spare server grade
>> machine to hand (ex Novell 6.0).
>
> But nothing you said above forces the machine to be the DC.
>
>> So I guess I have my answer thanks to all who posted.
>>
>> Regards
>>
>> "Herb Martin" <news@LearnQuick.com> wrote in message
>> news:uMDlDa61EHA.1860@TK2MSFTNGP15.phx.gbl...
>> > "Terry" <it@REMOVETHISfloydautomatic.co.uk> wrote in message
>> > news:OILq3v51EHA.3816@TK2MSFTNGP09.phx.gbl...
>> >> I need a separate subnet for moving large amounts of data which if
>> >> done
>> >> on
>> >> the subnet that our Sage users are on will cuase that app to slow
>> >> down.
>> >> (it's a DOS app) Sometime in the near future I will be able to ditch
> the
>> > DOS
>> >> app for a Windows version and then be able to do something else
>> >> usefull
>> > with
>> >> the network.
>> >
>> > You still haven't explained why the DC needs to
>> > be the multi-homed machine instead of an ordinary
>> > router or other Windows server, or even workstation,
>> > doing that job.
>> >
>> > --
>> > Herb Martin
>> >
>> >
>> >> regards
>> >>
>> >>
>> >> "Lanwench [MVP - Exchange]"
>> >> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
>> > message
>> >> news:uu14aa11EHA.1408@TK2MSFTNGP10.phx.gbl...
>> >> > Terry wrote:
>> >> >> I need to take WINS off the PDC which is multi-homed and put it
>> >> >> onto
>> >> >> another machine. Can I use XPpro as the OS
>> >> >
>> >> > No.
>> >> >
>> >> >> or do I need another
>> >> >> 2003 server?
>> >> >
>> >> > Or 2000 or NT, even, I think....
>> >> >
>> >> >> Regards
>> >> >
>> >> > Why does your PDC/DC need to be multihomed, if I may ask? I don't
>> >> > recommend
>> >> > this.
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>

Relevant Pages

  • Re: newbie
    ... The workgroup support that is mentioned for sp1 is only for advanced ... clients, and no not all clients have to be a member of the same ... directory environment then try network discovery, ... And does all the machines that are going to be connecting to the SMS ...
    (microsoft.public.sms.setup)
  • Re: Another Best Practice Questioen
    ... No doubt the reason they don't install is that SMS 2003 RTM does not support ... Workgroup support is for Advanced Clients only. ...
    (microsoft.public.sms.setup)
  • Re: domain client login
    ... deployed are members of the domain? ... On most of clients in the network ... see Help and Support Center at ... > available for domain WORKGROUP. ...
    (microsoft.public.win2000.active_directory)
  • Re: DNS A records not registering in workgroup environment
    ... XP Clients (workgroup also) also have a Primary DNS suffix. ... because the client needs to know what domain to register the A record into. ...
    (microsoft.public.win2000.dns)
  • track netbios to ip addres
    ... is there an easy way to track down a rouge netbios broadbaster on our subnet? ... our clients are all set to workgroup "ABCD". ... and someone bring in their home computer set to "MSHOME" or "Workgroup". ...
    (microsoft.public.security)