Connection problems with Windows Server 2003 R2 Installation

Sorry, this post got posted when I had not finished writing it, but the
answer I already got helped a bit.
So, this is the new situation:

We (used to) have a Novell server (which means I am a Novell administrator,
Have worked with a windows network before, but never set up an
ActiveDirectory from scratch). We are going to use some software that makes
it necessary to have a windows network, so....

I am setting up the first Windows Server 2003 R2.
After installing the software and SP2, I got to the screen Manage your
Server
(In Dutch: "Uw Server beheren". The English terms I have to translate from
Dutch, so forgive me if the translations are a wee bit off)

My network setup:
1 Novell server: 192.168.0.250
1 adsl router (this is the only gateway in this subnet): 192.168.0.1

I have a Dell Poweredge 2950 III, with 2 Broadcom Gigabit Ethernet cards
These I have setup as follows:
LAN1:
Domain suffix:
IP address: 192.168.0.5
Gateway: 192.168.0.1
DNS Servers: 192.168.0.5


LAN2: Not connected

Now I run the "Standard configuration for the first server" in the network

Active Directory domain name: (say 'xxx.local'
(we have a 'xxx.nl' domain registered.This is to hold the local and public
networks apart.)
Netbios name: XXXLOCAL

forward DNS queries: 212.54.40.25
(primary DNS server from my ISP)

---------------------------------------
After this has finished and the server is restarted, then everything seems
to be OK on the server.
If I check the DNS log the last entry is: DNS server is started.
5 minutes later it has given several errors:
4 x error 32 while loading _mscd.xxx.local
4 x error 32 while loading xxx.local
1 x error 32 while loading _mscd.xxx.local
1 x error 32 while loading xxx.local
But here it is said in the error message that this might be a temporary
thing and it will try to load again in the next time out cycle and indeed,
15 minutes later there are no new error messages, so I will assume this is
OK
---------------------------
At this point the servers NIC that I had pointed to the DNS server
192.168.0.5 has been reconfigured to point to the loopback
(127.0.0.1) Is this how it should be?.

Now comes the problem of adding computers/users to the domain.
I go to the management console for the AD.
click on the container 'computers'
add a Computer to this container with the name xxx11

Now I go to the workstation xxx11
start -> configuration -> system
In the tab "Computer name" click on change
click radiobutton 'domain' and enter xxx.local
click OK

*** HERE IS THE PROBLEM ***
I get an error message saying "Cannot connect to a domain controller in the
domain xxx.local"

The following error occurred while requesting the Service Location
(SRV)-resource record in DNS that is being used to find a domain controller
in in the domain xxx.local
This operation was returned because the time out period has passed
(error code: 0x000005B4 ERROR_TIMEOUT)

(In Dutch: De volgende fout is opgetreden tijdens het opvragen van de
Service Location (SRV)-bronrecord in DNS dat wordt gebruikt om een
domeincontroller te vinden in het domein xxx.local:
De fout is: Deze bewerking is geretourneerd omdat de time-outperiode
verlopen is.
(foutcode 0x000005B4 ERROR_TIMEOUT))

Can somebody please help !!!
What am I doing wrong.
I have been searching the documentation and the book: windows 2003 unleashed
(about 1200 pages) but I cannot seem to find the mistake

TIA

Peter-Paul Jansen
Rijswijk, The Netherlands

--
Peter-Paul Jansen
Triple EEE Manageemnt Support BV
Rijswijk, The Netherlands

> LAN2: Not connected


Please disable the NIC if you are not going to use it. Or team it.

> At this point the servers NIC that I had pointed to the DNS server
> 192.168.0.5 has been reconfigured to point to the loopback
> (127.0.0.1) Is this how it should be?.
>

You should leave the actual IP address of the NIC not 127.0.0.1.

> I get an error message saying "Cannot connect to a domain controller in
> the
> domain xxx.local"

It sounds like the workstation is not pointed to the DNS server
(192.168.0.5) in your case.

These 3 articles will get your DNS set up and working correctly.
See:
Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default...b;en-us;237675

Best Practices for DNS Client settings in Windows 2000 server and in Windows
Server 2003

http://support.microsoft.com/default...b;en-us;825036

How to configure DNS for Internet access in Windows Server 2003

http://support.microsoft.com/default...b;en-us;323380





hth

DDS




"Peter-Paul Jansen" <> wrote in
message news:411C3C92-ABB9-486B-A0E6-...
> Sorry, this post got posted when I had not finished writing it, but the
> answer I already got helped a bit.
> So, this is the new situation:
>
> We (used to) have a Novell server (which means I am a Novell
> administrator,
> Have worked with a windows network before, but never set up an
> ActiveDirectory from scratch). We are going to use some software that
> makes
> it necessary to have a windows network, so....
>
> I am setting up the first Windows Server 2003 R2.
> After installing the software and SP2, I got to the screen Manage your
> Server
> (In Dutch: "Uw Server beheren". The English terms I have to translate from
> Dutch, so forgive me if the translations are a wee bit off)
>
> My network setup:
> 1 Novell server: 192.168.0.250
> 1 adsl router (this is the only gateway in this subnet): 192.168.0.1
>
> I have a Dell Poweredge 2950 III, with 2 Broadcom Gigabit Ethernet cards
> These I have setup as follows:
> LAN1:
> Domain suffix:
> IP address: 192.168.0.5
> Gateway: 192.168.0.1
> DNS Servers: 192.168.0.5
>
>
> LAN2: Not connected
>
> Now I run the "Standard configuration for the first server" in the network
>
> Active Directory domain name: (say 'xxx.local'
> (we have a 'xxx.nl' domain registered.This is to hold the local and public
> networks apart.)
> Netbios name: XXXLOCAL
>
> forward DNS queries: 212.54.40.25
> (primary DNS server from my ISP)
>
> ---------------------------------------
> After this has finished and the server is restarted, then everything seems
> to be OK on the server.
> If I check the DNS log the last entry is: DNS server is started.
> 5 minutes later it has given several errors:
> 4 x error 32 while loading _mscd.xxx.local
> 4 x error 32 while loading xxx.local
> 1 x error 32 while loading _mscd.xxx.local
> 1 x error 32 while loading xxx.local
> But here it is said in the error message that this might be a temporary
> thing and it will try to load again in the next time out cycle and indeed,
> 15 minutes later there are no new error messages, so I will assume this is
> OK
> ---------------------------
> At this point the servers NIC that I had pointed to the DNS server
> 192.168.0.5 has been reconfigured to point to the loopback
> (127.0.0.1) Is this how it should be?.
>
> Now comes the problem of adding computers/users to the domain.
> I go to the management console for the AD.
> click on the container 'computers'
> add a Computer to this container with the name xxx11
>
> Now I go to the workstation xxx11
> start -> configuration -> system
> In the tab "Computer name" click on change
> click radiobutton 'domain' and enter xxx.local
> click OK
>
> *** HERE IS THE PROBLEM ***
> I get an error message saying "Cannot connect to a domain controller in
> the
> domain xxx.local"
>
> The following error occurred while requesting the Service Location
> (SRV)-resource record in DNS that is being used to find a domain
> controller
> in in the domain xxx.local
> This operation was returned because the time out period has passed
> (error code: 0x000005B4 ERROR_TIMEOUT)
>
> (In Dutch: De volgende fout is opgetreden tijdens het opvragen van de
> Service Location (SRV)-bronrecord in DNS dat wordt gebruikt om een
> domeincontroller te vinden in het domein xxx.local:
> De fout is: Deze bewerking is geretourneerd omdat de time-outperiode
> verlopen is.
> (foutcode 0x000005B4 ERROR_TIMEOUT))
>
> Can somebody please help !!!
> What am I doing wrong.
> I have been searching the documentation and the book: windows 2003
> unleashed
> (about 1200 pages) but I cannot seem to find the mistake
>
> TIA
>
> Peter-Paul Jansen
> Rijswijk, The Netherlands
>
> --
> Peter-Paul Jansen
> Triple EEE Manageemnt Support BV
> Rijswijk, The Netherlands

>>Quote:
>>Please disable the NIC if you are not going to use it. Or team it.

That did it. Puilling the cable was not enough
Thanks a million

Peter-Paul

"Danny Sanders" <> schreef in bericht
news:%...
>> LAN2: Not connected
>
>
> Please disable the NIC if you are not going to use it. Or team it.
>
>> At this point the servers NIC that I had pointed to the DNS server
>> 192.168.0.5 has been reconfigured to point to the loopback
>> (127.0.0.1) Is this how it should be?.
>>
>
> You should leave the actual IP address of the NIC not 127.0.0.1.
>
>> I get an error message saying "Cannot connect to a domain controller in
>> the
>> domain xxx.local"
>
> It sounds like the workstation is not pointed to the DNS server
> (192.168.0.5) in your case.
>
> These 3 articles will get your DNS set up and working correctly.
> See:
> Setting Up the Domain Name System for Active Directory
>
> http://support.microsoft.com/default...b;en-us;237675
>
> Best Practices for DNS Client settings in Windows 2000 server and in
> Windows Server 2003
>
> http://support.microsoft.com/default...b;en-us;825036
>
> How to configure DNS for Internet access in Windows Server 2003
>
> http://support.microsoft.com/default...b;en-us;323380
>
>
>
>
>
> hth
>
> DDS
>
>
>
>
> "Peter-Paul Jansen" <> wrote in
> message news:411C3C92-ABB9-486B-A0E6-...
>> Sorry, this post got posted when I had not finished writing it, but the
>> answer I already got helped a bit.
>> So, this is the new situation:
>>
>> We (used to) have a Novell server (which means I am a Novell
>> administrator,
>> Have worked with a windows network before, but never set up an
>> ActiveDirectory from scratch). We are going to use some software that
>> makes
>> it necessary to have a windows network, so....
>>
>> I am setting up the first Windows Server 2003 R2.
>> After installing the software and SP2, I got to the screen Manage your
>> Server
>> (In Dutch: "Uw Server beheren". The English terms I have to translate
>> from
>> Dutch, so forgive me if the translations are a wee bit off)
>>
>> My network setup:
>> 1 Novell server: 192.168.0.250
>> 1 adsl router (this is the only gateway in this subnet): 192.168.0.1
>>
>> I have a Dell Poweredge 2950 III, with 2 Broadcom Gigabit Ethernet cards
>> These I have setup as follows:
>> LAN1:
>> Domain suffix:
>> IP address: 192.168.0.5
>> Gateway: 192.168.0.1
>> DNS Servers: 192.168.0.5
>>
>>
>> LAN2: Not connected
>>
>> Now I run the "Standard configuration for the first server" in the
>> network
>>
>> Active Directory domain name: (say 'xxx.local'
>> (we have a 'xxx.nl' domain registered.This is to hold the local and
>> public
>> networks apart.)
>> Netbios name: XXXLOCAL
>>
>> forward DNS queries: 212.54.40.25
>> (primary DNS server from my ISP)
>>
>> ---------------------------------------
>> After this has finished and the server is restarted, then everything
>> seems
>> to be OK on the server.
>> If I check the DNS log the last entry is: DNS server is started.
>> 5 minutes later it has given several errors:
>> 4 x error 32 while loading _mscd.xxx.local
>> 4 x error 32 while loading xxx.local
>> 1 x error 32 while loading _mscd.xxx.local
>> 1 x error 32 while loading xxx.local
>> But here it is said in the error message that this might be a temporary
>> thing and it will try to load again in the next time out cycle and
>> indeed,
>> 15 minutes later there are no new error messages, so I will assume this
>> is
>> OK
>> ---------------------------
>> At this point the servers NIC that I had pointed to the DNS server
>> 192.168.0.5 has been reconfigured to point to the loopback
>> (127.0.0.1) Is this how it should be?.
>>
>> Now comes the problem of adding computers/users to the domain.
>> I go to the management console for the AD.
>> click on the container 'computers'
>> add a Computer to this container with the name xxx11
>>
>> Now I go to the workstation xxx11
>> start -> configuration -> system
>> In the tab "Computer name" click on change
>> click radiobutton 'domain' and enter xxx.local
>> click OK
>>
>> *** HERE IS THE PROBLEM ***
>> I get an error message saying "Cannot connect to a domain controller in
>> the
>> domain xxx.local"
>>
>> The following error occurred while requesting the Service Location
>> (SRV)-resource record in DNS that is being used to find a domain
>> controller
>> in in the domain xxx.local
>> This operation was returned because the time out period has passed
>> (error code: 0x000005B4 ERROR_TIMEOUT)
>>
>> (In Dutch: De volgende fout is opgetreden tijdens het opvragen van de
>> Service Location (SRV)-bronrecord in DNS dat wordt gebruikt om een
>> domeincontroller te vinden in het domein xxx.local:
>> De fout is: Deze bewerking is geretourneerd omdat de time-outperiode
>> verlopen is.
>> (foutcode 0x000005B4 ERROR_TIMEOUT))
>>
>> Can somebody please help !!!
>> What am I doing wrong.
>> I have been searching the documentation and the book: windows 2003
>> unleashed
>> (about 1200 pages) but I cannot seem to find the mistake
>>
>> TIA
>>
>> Peter-Paul Jansen
>> Rijswijk, The Netherlands
>>
>> --
>> Peter-Paul Jansen
>> Triple EEE Manageemnt Support BV
>> Rijswijk, The Netherlands
>
>