Server 2003 Configuration Issues

I'm building a small text network at home with Server 2003 & a few XP Pro workstations. I've completed installation and the network topology includes the workstations and server connected to a switch which is connected to a router.

I have finished all the installations and ran DCPROMO to build up my AD on the Server. I have the Server configured as a DNS Server and it is pointing to itself. Its secondary DNS Server is the router, still running that feature.

The workstations are configured to pick up IPs from the router through DHCP. I statically entered in the ip address of the Server for the primary DNS and have the router as the secondary.

Here is where I ran in to some problems. I wasn't able to ping anything. I figured that it had to do with the firewalls, so I configured each workstation to allow Remote Desktop & allow ICMP.

Now I'm able to ping the desktops from the Server, but unable to ping the Server.

I decided to try and do the same to the Server. I clicked on the Windows Firewall icon and it gave me the message, "Windows Firewall cannot run because another program or service is running that might use the network address translation component (Ipnat.sys).

BTW, I have three NICs on my Server.

I also tried adding my workstations to my domain, but was given a DNS error that basically said that the domain did not exist.

Thanks in advance.

I would plug one of the Server nic s into the router, another into the switch...all your clients into the switch and let your server handle the dns, internet, dhcp....

KISS ;)

MLF

In keepin with MLF's KISS

connect everything to the switch [server / router / stations] set IP to automatic at first.
set router to hand out IP's in the range you want, set to permanent IP when it all runs.

you HAVE set a domain ? :eek:
AND joined the workstations to it ?

My system is set the same as yours [more or less] and I too had this same problem, I put the workstations back to workgroup and then re-joined to the domain.

Still not sure why they flopped in the first place, but it was my first set up attempt :)

I created a domain and I'm attempting to add the workstations to it. The trouble is, there isn't any connectivity between workstations and Server. I think it has to be the Firewall on the Server. I can ping workstations and not the Server.

disable the F/W

disconnect from the WWW first :)
try it now .......

* me racks what little is left of brain to remember WTF I did to get mine up and running ..........

[edit]
just go in and check that all settings for IP are set to be done automatically

II tried Disabling the Firewall, but it gave me the error, "Windows Firewall cannot run because another program or service is running that might use the network address translation component (Ipnat.sys)."

I also figured it could possibly be a DNS issue. I know that every says that if a server is hooked up to an intranet, you should only use your DNS Servers IP and create a Foward Lookup. I set up the Forward Lookup and Reverse Lookup with the DNS Manager and have all 4 folders. I also ran DCDiag.exe to see if there was an issue, but my server passed all perameters.

Edit: i also tried disabling my NIC card before I disabled the Firewall, but it gave me the same error.

have you tried to disable the server from DNS ?
just let the router do it for a while ?

and again, set stations to get IP's automatically at first.
lets get it all joined up first :)

can you access the web from the server ?
can you access the web from a station ?

what is ipconfig/all telling you on the stations / server ?

[eddit]
when my station wouldn't see the domain / the DNS error you are getting coming up .....

I set a fixed IP, within the range I'd set into the ADSL router I use [10.0.0.1 / 10.0.0.25]
then I joined the domain ............

I can't remember what else I'd bolloxed up :( sorry

but it was basically, that I'd tried to set fixed IP's, with server as DNS and DCHP.
with, at first, an ADSL modem as the link.
ADSL router fitted

router > switch
server > switch
stations > switch

set network connections to get IP automatically
set up router as DNS

all ran good

am in the process of setting fixed IP's and having all services in house as it were ....

On the Server:

The Server is set up as its own DNS server, but also has the router as the secondary DNS Server.

I could be wrong here, but I was always under the impression that Active Directory needs to have its own DNS server. I usually create my zones before I set up through DCPromo, but I do know dcpromo sets one up for you (unless it's an option).

The Server is able to access the web.
IPConfig tells me the ip address of the Server
192.168.1.149
255.255.255.0
DNS:192.168.1.149
DNS:192.168.1.1


The workstations are able to access the web.
They are dynamically assigned IP addresses from the router.
I manually assigned them to use the DNS Server first and then the router.
ipconfig:
192.168.1.110
255.255.255.0
DNS:192.168.1.149
DNS:192.168.1.110

what name have you given the domain ?

I used 'home'
the system added '.local' to the address
I join to 'home.local'

Quote:

---

DNS:192.168.1.149
DNS:192.168.1.1

DNS:192.168.1.110

---

is this a typo ?
can you just use the one DNS for now ?
the 149 = server ?
110 = a workstation ??

Hey,

Is your DCOM service running (check in services) ...if it's not then your firewall will also not be running.

The Windows 2003 Firewall depends on that service. So if the firewall isn't running then this will not be the reason for the communications error I guess ??

You're right about AD needing it's own DNS, without it , it will not work ...although it is theoretically possible to use an existing DNS server (even a linux one), but does not come recommended by M$ :D.

Also ..I do not see a gateway anywere ... the router is the gateway right ? ...So the gateway should be the same as 192.168.1.1 (if that is the router) ... And I think it's not necessary to have the secondary DNS pointing to the router ...you use forwarding so ...

Anyway ...if you can check the DCOM ...maybe it will help , help on the way ;)

C.

Disable RRAS and restart the box to get to the firewall.

Do like the Watery Tart says and simplify your architecture. ;)

Don't set up your zones in DNS and then DCPromo let Win2k3 set up it's own zone.

You are correct - AD does not work without fully functioning DNS since this is where the information about your zone are kept. It is always best to store the AD DNS information within AD itself - it's more tightly integrated and Win2X manages it more efficiently than you can.

Sorry, I made a mistake when I wrote the DNS Server IP addresses. I wasn't in front of the system and just tried to remember off hand.

First DNS Server running (Server 2003) Domain Server
Second Router

I did this on each work station as well as the Server.

I figured it would be a DNS issue. I checked zone lookup and I have my 4 folders. Also ran DCdiag and passed all tests.

I'll try the other suggestions to see what is going on. I figured that it might be the firewall because I'm unable to ping and the error given was the portion of the firewall that seems to deal with Layers 1 - 3 traffic. In the case of my ping, ICMP seems to be blocked.

I'll know later on. This thing is really getting to me. I've never been stuck on a step like this when setting up a network. I've always installed Server 2003 myself. This server came preinstalled from Dell, so I don't know what to think.

Thanks a lot for all your help. I'll message back with an update.

Yep... Mine was preinstalled by Dell too..... There is no access to the server from the network in terms of pinging etc. in it's default config when it comes from Dell.....

I'm still not sure if that is a good thing or not..... It's going to confuse the hell out of inexperienced people and it sure added time to the contract job I was doing before I realized it was the default security settings stopping me from doing those "basics" you do when installing a server. Then the silly Ipnat.sys issue that is badly documented by MS really racks up the chargable hours.... Bummer ;)

Thanks a lot for everyone's help. I got rid of RRAS, rebooted and was able to get to my Firewall to reconfigure it to allow ICMP & Remote Desktop. I checked connectivity on all stations, pings worked both ways. Everything looked good.

Now I tried joining the domain from my workstation.

I right click My Computer; went into properties; clicked on the Computer Name tag, change name and then put in the domain name. A log on prompt popped up and I entered in my login information for my Administrator account. An error message came back saying, "The following error occurred attempting to join the domain "mydomain name". The specific server cannot perform the requested operation"

I figured it had to be a DNS issue. I ran DCdiag and it showed everything was running fine but Services. The services RPLocator; TrkWks and TrkSvr were stopped. I'm hestiant to run a net start on any of these because I haven't been able to figure out what they are used for. I tried googling and haven't found much. I search my 2000 books and nothing.

I'm not sure if those are the problems or if it's something else. I went back and turned off the firewall completely and tried adding my workstation and after I entered my login information to join the domain, it authenticated for a minute or so and then said the domain was unable to be found.

Thanks a lot for all your help guys.

Are you trying to change the PC name AND join the domain wthout a re-boot ?

One thing at a time
rename
re-boot
join domain
re-boot

long winded, yes, but it's the way it's done .........

I wasn't trying to change the name, just join the domain. That's just one step that I've always used to join a domain and it has work well for me up until now. Looks like a DNS issue. I figured I would just run dcpromo again to get rid of the domain and then reapply it. Only problem, it seemed to have reset my password as well.

Anyone here know where I can get a copy of Super ERD?