Joining Domain Problem

  • Thread starter Thread starter Ice Sickle
  • Start date Start date
I

Ice Sickle

My setup is Windows 2000 Server connected to a machine(crossover cable)
running Windows 2000 Pro which has 2 NICs one of which is connected to the
router and then the internet. Pro has dynamic IP and Server has static
192.168.0.2 address. I can see my Pro machine from Server and can even
access it from AD administation snapin. . I can see what disks I have and so
on. I can see the domain and ping the server from pro machine as well.
However when I try to join the domain from Pro machine I get error described
here:
http://www.microsoft.com/windows2000/dns/tshoot/dns_tshoot2A.asp

I've uninstalled firewall so that's not an issue.

since I have this somewhat weird setup maybe that's why my pro machine can't
connect. I'm thinking that maybe it's trying to lookup the domain through
the wrong NIC card--the one that is connected to the router instead of the
one that is connected to the Server machine.
 
If the Pro machine is getting an IP from the router's DHCP server, it is
probably being passed the DNS settings that come from your ISP. This won't
be able to resolve the address of the domain controller.

Either configure the router to pass the IP address of your Server as the DNS
server, or disable DHCP on the router and install it on the server.

Follow through the steps on that site and completely take your external DNS
out of the picture until the very very end. You will then want your
server to forward any requests outside of your namespace to your ISP's DNS
server.

Of course I've basically just restated what that article says but you didn't
mention having tried any of those steps... ;)
 
Of course, in order for that to work you would need to do some kind of
routing on the Pro box because of your weird topology. Internet Connection
Sharing would maybe work I guess but you could save yourself a headache by
just hooking them both into the router's switch. It's all firewalled behind
the router anyway right?
 
so basically if i would put the second NIC card into the server machine and
made it the gateway computer(Pro machine connected to Server rather than
server connected to pro) the whole setup would work. Am I understanding you
correctly?

Thank you for replying.
 
I guess....
But that's still a complicated way of doing it.
If you do that, you would need to run DHCP on the server, and configure the
scope to pass out the server's IP address as the DNS server.

See my other reply...

Of course it would be easier to just statically configure your Pro machine
since you only have the one client. Unless you are trying to simulate a
real enterprise network. :)

You would still need to configure some type of routing (and DNS forwarding)
through the Server if you want to access the web, etc. from the Pro machine.

Make sure you are using distinct subnets on each side of whatever your
'gateway' machine is. (i.e. make sure your router isn't handing out the
same subnet of local IPs that your gateway is.)
 
Ummm. I sort of misspoke when i said i have a router. Right now my Pro
machine is connected
to a cable modem(not router) and Server connected to pro. ICS is enabled on
the Pro machine and
server accesses internet through it.
 
Not sure if this will help, but if your looking to simulate a "Home" Network
Enviroment here is how I did it:

Take your W2K server, install 2 NICs
Take one NIC (1) and connect it to your Cable Modem
Take the other NIC (2), assign the following settings for your TCP/IP
properties: IP address: 192.168.0.1, Subnet mask: 255.255.255.0, No default
gateway
Connect the private NIC (2) and connect it to a hub\switch or in your case a
machine using a cross over cable
Enable the Routing and Remote Access Service, To configure the NAT server
for your internet connection sharing
In the Routing and Remote Access Server Setup Wizard, choose the options for
ICS and to set up a router with the NAT routing protocol.
Install DNS (which should be installed if you have a W2K domain) and DHCP
Configure a 192.168.0.0/24 DHCP scope that pushes DNS, Gateway of
192.168.0.1




Ummm. I sort of misspoke when i said i have a router. Right now my Pro
machine is connected
to a cable modem(not router) and Server connected to pro. ICS is enabled on
the Pro machine and
server accesses internet through it.
 
Back
Top