4 replies
by ltop
Hi,
Just so that I am understanding what you have achieved so far, you have your lab environment with a DC and a connection to a client pc you have joined to the new domain on the DC.
So far so good. Now the problems.
What is the router connected to other than the DC and client pc?
You ping the client pc from the DC?
What is also connected to the workgroup. The DC or client pc? . Is your test lab on the same LAN as your workgroup? or is there no connection between the domain lab and the workgroup
Sorry, but just trying to get a better picture of your network layout,
cheers,
by ltop
Hi again,
Lets try using one NIC - having a spare already installed is handy in case the one being used happens to fail. Disable the second NIC at this point. Also if you were to use two NIC's at once, they should have different IP addresses.
Aquire a switch from somewhere and connect your DC and the client pc (the one you attached to the domain) to the switch.
Remember that this is supposed to be a Lab setup to allow you to test the setup of the domain. As you sound uncertain regards your setup of the AD and DNS, the idea is to ensure you get it right before you attach it to the rest of the network.
I don't know how many ports you have available on your router/firewall?
I would attach the switch then to the router/firewall. You already have the DNS set as your DC then ISP. What about the default gateway on the DC and client pc (the routers IP).
Once you have the client and DC talking okay you could go ahead and attach the other workgroup pc's to the switch and start setting them up on the domain.
This workgroup all in one location? Same subnet.
How is the IP addressing. Do you need to change anything on the workgroup pc's. Duplicate what ever you did on the one client pc you setup on the domain on the rest of the pc's.
Any network printers - use network print servers and setup the printers on the DC rather than connecting them to pc's.
Again, the idea behind a lab is to test, test, and test again, before you replicate this into the live situation.
keep in touch,
cheers
by gregb
Ltop,
Thanks for the response, I will try and answer your question, and paint a better picture. The thing is my DC has 2 NIC's, should I be utilizing both NIC's? Or can I hook my DC to the Router/Firewall used now by my workgroup?
I have 2 NICs within my DC, I set both NICs with the same static IPs, the primary DNS being the new DC and the secondary as the ISP's DNS. When I connect my DC (NIC 2) to the workgroup I am able to connect to the entire workgroup, when I connect the same workgroup to NIC 1, nothing??
My question is then probably, why do I need 2 NIC's for a Domain Controller? One would work fine connected to the router?
Thanks for your help!
by gregb
Thanks Ltop for your help...But I am still having a strange issue.
To answer your question I do have my lab connected to the switch, which is connected to my current network, I have been able to join current workgroup pc's to my new domain. The problem I am having is when I ping my new DC by name from my network it gives a timeout and is trying to resolve the IP from my disabled NIC. I disable and re-enable my NIC I am using and then I can ping it, if I restart the PC it drops the ping again, until a disable and re-enable the NIC. Would you have any idea why this happens??
Hope this makes some sense?
Thanks so much!
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending