Active Directory hell...

Why are you setting up AD in the first place? It's complete overkill for a home network, and no offence, but it sounds like you don't really know what you're doing with it anyway. If you want your server to share files, create normal windows shares like you would on any other machine.

well I finally got it installed and I can connect my workstations to the domain, I just made a stupid mistake and didn't change my ip settings...and yes I do feel like an idiot. However, now after I installed Active Directory on my mainframe server it does not connect to the internet. I have 2 network adapters. One holds the internet connection while the other one allows workstations to connect to the mainframe server's domain. Any ideas on why I can't connect to the internet? It was working before I installed Activer Directory. Thanks everyone.

Which Windows OS are you running? If you're running Windows 2003, you should go to:

Start -> Administrative Tools -> Routing and RAS

Before going there, make sure you rename both your network interfaces to Internet and Network, so you know which of the interfaces serves as internet NIC and which is for the network.

(From here, it's from the top of my head, since I can't go around messing with the routing and RAS settings from my clients)

Right click on your server name, and select "Enable Routing and RAS". A wizard will popup. In that wizard, you have to select something along the lines of "Use this machine as a router with NAT". Click next. It should now ask you which interface is used for the internet. Click on your internet NIC and hit next. If you get a different screen, before or after this, hit next, and stay away from those settings.

After this, it should finish the wizard, and you need to make sure you have the proper settings on your NICs. Go to the properties tab of your NETWORK interface. Give it the desired IP address of your network, fill in the subnet mask BUT DO NOT fill out a gateway. Keep the gateway entry EMPTY.

Next, go to your internet NIC. Either put it to a static IP address or dynamic(Depending on your router). But for god sake, make sure it's a different range than your network NIC(i.e. 192.168.2.1 for the NETWORK interface, and 192.168.1.2 for the INTERNET interface, assuming your modem takes 192.168.1.1).

If your modem is a router, look up what the IP range of it is. I'm assuming 192.168.1.1 for the router. Give the INTERNET nic the IP of 192.168.1.2, correct subnetmask and a gateway of 192.168.1.1.

After this, your Windows 2003 Router should be configured properly. No need to reboot, just go ahead, and test. Also, are you running DHCP? If yes, make sure to fill out the 'Router' entry in the DHCP settings, and give it the value of your internet NIC.

Toolmaker

On a sidenote: You do sound like you never did this before and you do sound like you don't really know what you do.

This kind of things aren't for the 'amateur'. If you want to continue to keep fiddling around, make sure to get a good book on Server Administration. It makes life a lot easier.

Toolmaker

I've been working for Windows Server 2003 for quite some time. I just never had to setup Active Directory b/c it was just served as a web host. But as my online buisness needs are growing, I need more enterprise applications, which seem to run with Active Directory in my case. But I'm not going to pretend I'm a professional or anything. But I wouldn't consider myself an amateur either. Thanks for the help I'll try what you guys said! *Crosses fingers* :)

Quote:

Original post by sathenzar I've been working for Windows Server 2003 for quite some time. I just never had to setup Active Directory b/c it was just served as a web host. But as my online buisness needs are growing, I need more enterprise applications, which seem to run with Active Directory in my case. But I'm not going to pretend I'm a professional or anything. But I wouldn't consider myself an amateur either. Thanks for the help I'll try what you guys said! *Crosses fingers* :)

What kind of enterprise applications do you need to run on it for it to be a domain controller?

I agree, it's fun to fiddle around with a server, esp. exploring the possibilities of the OS. However, it sounds to me, that you're dependant on the machine, so you shouldn't mess around too much with it.

Also, as you're not a pro, getting a good book on the subject might be a very good plan. I'm going to setup a W2k3 DC myself coming weekend, as I need it as a testbed for new settings for my clients. But: I won't be dependant on it ^_^.

Toolmaker

lol, well thanks again. I don't mean to bug you any more. But for some odd reason the last hurtle I need to clear is that prot 80 now is blocked, which is needed to run apache. It says it's being taken up by C:\WINDOWS\System32\svchost.exe. Any ideas on how to free this port? Thanks a million!

This is going to sound like a stupid question..


Is IIS running?

Yes, y? I have a feeling I'm going to feel stupid in a minute. Is that whats doing it?

Quote:

Original post by sathenzar Yes, y? I have a feeling I'm going to feel stupid in a minute. Is that whats doing it?

IIS is a webserver.. which runs on port 80 :)

Quote:

Original post by sathenzar Yes, y? I have a feeling I'm going to feel stupid in a minute. Is that whats doing it?

I told you the same in the PM, and even gave you instructions to remove it ;)