Networking Forums

Networking Forums > Computer Networking > Windows Networking > New DC in workgroup environment

Reply
Thread Tools Display Modes

New DC in workgroup environment

 
 
Steven Cooke
Guest
Posts: n/a

 
      06-18-2004, 02:50 PM
Hi guys, I need to install a Windows 2003 domain controler (active
directory) onto my workgroup network. The problem is that it was done once
before(I have just started here) and apparently as soon as the domain
controler came online, it took control of the WINS and therefore none of the
pcs could access the network, so I dont want to just do it and then find out
theat it crashes my network.
Is there a way to get around this?
Network running DHCP with windows 2000/2003 servers, windows 98/2000/xp
clients and Macs



--
TIA
Steven


 
Reply With Quote
 
 
 
 
Phillip Windell
Guest
Posts: n/a

 
      06-18-2004, 03:10 PM
I think you have a wrong impression. AD is not related to, nor has any
effect on WINS,...the same is true for DHCP. AD is related only to DNS, and
even at that, it only effects machines that are specifically made members of
the Domain and which are also pointed to the AD DNS Server for thier DNS.
Other than that, all the other machines couldn't care less if the DC existed
or not.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Steven Cooke" <stevenc"at"fishwicks.co.za> wrote in message
news:(E-Mail Removed)...
> Hi guys, I need to install a Windows 2003 domain controler (active
> directory) onto my workgroup network. The problem is that it was done

once
> before(I have just started here) and apparently as soon as the domain
> controler came online, it took control of the WINS and therefore none of

the
> pcs could access the network, so I dont want to just do it and then find

out
> theat it crashes my network.
> Is there a way to get around this?
> Network running DHCP with windows 2000/2003 servers, windows 98/2000/xp
> clients and Macs
>
>
>
> --
> TIA
> Steven
>
>



 
Reply With Quote
 
Steven Cooke
Guest
Posts: n/a

 
      06-21-2004, 06:46 AM
Thats what I thought, but apparently the DC takes over the WINS requests,
and seeing as the clients are still pointing at another machine for WINS
resolution, and that machine no longer handles the WINS requests, the
clients can't connect.
I guess I'll just have to give it a go and hope that the network doesn't
fall over.

--
Steven Cooke


"Phillip Windell" <@.> wrote in message
news:O%(E-Mail Removed)...
> I think you have a wrong impression. AD is not related to, nor has any
> effect on WINS,...the same is true for DHCP. AD is related only to DNS,

and
> even at that, it only effects machines that are specifically made members

of
> the Domain and which are also pointed to the AD DNS Server for thier DNS.
> Other than that, all the other machines couldn't care less if the DC

existed
> or not.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Steven Cooke" <stevenc"at"fishwicks.co.za> wrote in message
> news:(E-Mail Removed)...
> > Hi guys, I need to install a Windows 2003 domain controler (active
> > directory) onto my workgroup network. The problem is that it was done

> once
> > before(I have just started here) and apparently as soon as the domain
> > controler came online, it took control of the WINS and therefore none of

> the
> > pcs could access the network, so I dont want to just do it and then find

> out
> > theat it crashes my network.
> > Is there a way to get around this?
> > Network running DHCP with windows 2000/2003 servers, windows 98/2000/xp
> > clients and Macs
> >
> >
> >
> > --
> > TIA
> > Steven
> >
> >

>
>



 
Reply With Quote
 
Phillip Windell
Guest
Posts: n/a

 
      06-21-2004, 01:52 PM
"Steven Cooke" <stevenc"at"fishwicks.co.za> wrote in message
news:(E-Mail Removed)...
> Thats what I thought, but apparently the DC takes over the WINS requests,
> and seeing as the clients are still pointing at another machine for WINS
> resolution, and that machine no longer handles the WINS requests, the
> clients can't connect.


That is not what is happening. It just simply doesn't work that way. WINS
requests are "directed" by the client making the request based on the
clients WINS setting. It is not possible for it to go anywhere else,...it
cannot be "hyjacked".

You also need to define "can't connect" in this context.

Whatever you have happening isn't what you think it is, but from here and
can't possibly guess at what it would be.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


 
Reply With Quote
 
Steven Cooke
Guest
Posts: n/a

 
      06-21-2004, 03:23 PM
I'm going to connect it and see what happens, I'll let you know as soon as I
do,

Thanks

--
Steven Cooke


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> "Steven Cooke" <stevenc"at"fishwicks.co.za> wrote in message
> news:(E-Mail Removed)...
> > Thats what I thought, but apparently the DC takes over the WINS

requests,
> > and seeing as the clients are still pointing at another machine for WINS
> > resolution, and that machine no longer handles the WINS requests, the
> > clients can't connect.

>
> That is not what is happening. It just simply doesn't work that way. WINS
> requests are "directed" by the client making the request based on the
> clients WINS setting. It is not possible for it to go anywhere else,...it
> cannot be "hyjacked".
>
> You also need to define "can't connect" in this context.
>
> Whatever you have happening isn't what you think it is, but from here and
> can't possibly guess at what it would be.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>



 
Reply With Quote
 
Steven Cooke
Guest
Posts: n/a

 
      06-23-2004, 12:59 PM
I removed the WINS server role, and everything seems to be OK.

--
Steven Cooke


"Steven Cooke" <stevenc"at"fishwicks.co.za> wrote in message
news:%(E-Mail Removed)...
> I'm going to connect it and see what happens, I'll let you know as soon as

I
> do,
>
> Thanks
>
> --
> Steven Cooke
>
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > "Steven Cooke" <stevenc"at"fishwicks.co.za> wrote in message
> > news:(E-Mail Removed)...
> > > Thats what I thought, but apparently the DC takes over the WINS

> requests,
> > > and seeing as the clients are still pointing at another machine for

WINS
> > > resolution, and that machine no longer handles the WINS requests, the
> > > clients can't connect.

> >
> > That is not what is happening. It just simply doesn't work that way.

WINS
> > requests are "directed" by the client making the request based on the
> > clients WINS setting. It is not possible for it to go anywhere

else,...it
> > cannot be "hyjacked".
> >
> > You also need to define "can't connect" in this context.
> >
> > Whatever you have happening isn't what you think it is, but from here

and
> > can't possibly guess at what it would be.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >

>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DNS and IPv6 environment Gary Windows Networking 0 01-06-2008 03:12 PM
802.1x in wired environment landrew5@comcast.net Wireless Networks 0 11-22-2006 06:45 PM
Using b and g within the same environment Jamie Crilly Wireless Networks 2 05-17-2006 01:44 PM
How to 'clone' 2k3 environment (AD, LAN, etc..) for lab? Steve Jacobs Windows Networking 1 04-11-2006 09:30 PM
bluetooth and 802.11B/G in same environment. KraftDiner Wireless Internet 2 01-01-2006 12:15 AM



1 2 3 4 5 6 7 8 9 10 11