• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

A little domain help needed

D

DaiShan

Diamond Member
Hey guys, my school gave me an MSDN account which allowed me to get a copy of server 2003. I've been doing a lot of reading lately trying to buff up on the basics of setting up and administering a domain, and I figure the best way to learn would be to actually do some of the stuff.

I set up one computer as a domain controller for the domain vision-point.org. I've registered the domain name and pointed the name servers I use to my static IP. I'm running AD (obviously) on this computer and also a DNS with a forward look up zone for vision-point.org pointing to the IP of that box which is 192.168.2.108 (statitc internal) I've also configured forwarders to my ISP's DNS servers for all other DNS stuff.

My problem is, I have a secondary server running the web server version of server 2003 and I'm trying to connect it to the domain. I have it set with a static internal IP and the DNS is 192.168.2.108 but I cannot get it to join the domain vision-point.org as it keeps saying that it cannot find a domain controller. The IP of the web server box is 192.168.2.113. I can ping this fine from the domain controller, but when I ping the domain controller from the web server box it times out. I think this has something to do with it.

My questions are: can I even use internal IP's like I am now? What can I do to get the web server to join the domain? My laptop is also unable to join the domain. I've disabled the ISA service (also free thanks to MSDN LOL) and I've removed the VPN role from the server thinking that it was blocking access. I'm kind of at my wits end here, any of you networking gurus have some advice for a newb?
 
Check if you have a firewall enabled on the DC. It could be in the same spot as XP, or it could be in "Routing and Remote Access" under Admin. Tools. If you can't ping the DC then there is no way you can join the domain, so you need to resolve that issue first.
 
Check the cable.
Ping the loopback address.
Ipconfig /all the DC and webserver and look for inconsistencies.
Check your default gateway.

Have you made any computer accounts for the joining machines?

Hope this helps!
 
Loopback responds to ping, 192.168.2.108 still does not respond to ping. I've added a computer account for the webserver using its computer name. The gateway is the same on both computer (192.168.2.1) The DC can still ping the other computers, but not vice versa. I've stopped the Microsoft firewall service as well as the ISA service and still no dice.

Any other ideas?
 
I've done a little more research. The name of the DC is wicked and the name of the webserver is forsaken. On wicked I can type \\forsaken and access it. on forsaken I can type \\wicked and access it. Pings are still denied and I still cannot join the domain.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top