Domain Name conflict

[P. Prosper]

I recently moved our proxy server software (Winproxy) from a pc to one of
our 2 Win2K servers running active directory.
The server has two NIC one of wich is connected to a ADSL router.
Our local domain name cooperativa.com is in conflict with another internet
domain cooperativa.com. I am geting plenty of errors in the event log on my
server.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 9/9/2004
Time: 2:11:23 PM
User: NT AUTHORITY\SYSTEM
Computer: TELEVOZ
Description:
Windows cannot access the registry information at
\\cooperativa.com\sysvol\cooperativa.com\Policies\{31B2F340-016D-11D2-945F-0
0C04FB984F9}\Machine\registry.pol with (51).



I know changing the domain name for my network is not an easy task. How can
I fix this problem ?

Any help greatly appreciated, TX

The NICs on the server are configured as follows:

C:\Documents and Settings\Administrator>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : televoz
Primary DNS Suffix . . . . . . . : cooperativa.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cooperativa.com

Ethernet adapter Internet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : IBM 10/100 Ethernet Server
Adapter
Physical Address. . . . . . . . . : 00-0E-0C-32-A9-22
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.12
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Friday, September 03, 2004
10:14:39
AM
Lease Expires . . . . . . . . . . : Sunday, October 03, 2004
10:14:39 AM


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 8255x-based PCI Ethernet
Adapt
er (10/100)
Physical Address. . . . . . . . . : 00-02-55-A0-C3-BA
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.21
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1
Primary WINS Server . . . . . . . : 192.168.10.20

 

[Enkidu]

I'm inclined to think that the conflict with the external Domain Name
is not the problem. Can you open up a CMD window and type "nslookup
<theservername>.cooperativa.com"? Does it come up with the server's IP
address or does it fail?

Though having said that I've come across this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;258296

This implies that your problem may be the binding order of the NICs.

Cheers,

Cliff

 

[P. Prosper]

Here is the output for nslookup
C:\Documents and Settings\Administrator>nslookup cooperativa.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
Server: localhost
Address: 127.0.0.1

Name: cooperativa.com
Addresses: 192.168.10.21, 192.168.1.12, 192.168.10.22

....10.21 and 10.22 are my domain controllers
the problem I'm having is that my server can't access the group policy
because it's looking for it on cooperativa.com on the internet. If I disable
the NIC connected to the ADSL router everything works fine.

I tried to add my local DNS server address as primary DNS and the ADSL
router address as secondary for the NIC connected to the ADSL router but
then my clients PC start having problems accessing the NET.

 

[P. Prosper]

Thanks Cliff you were right, I just changed the binding order for the NICs
and it fixed the problem.

Thanks a lot.

 

[Enkidu]

OK, your DNS setup *may* be the problem. It's hard to tell. The DNS
entries for a NIC do not work the way that most people believe. A DNS
client always asks the first DNS server first. If it gets *any*
response, either an IP address or "DNS not found", it doesn't check
the second DNS server. It only uses the second DNS if and only if it
gets NO response at all from the first server. That is, the first
server is down or not responding.

This means that to work properly, the clients must be configured to
query the internal DNS *only*. If you only have one internal DNS
server you only have one entry in the NIC, not two.

The DNS servers themselves should have their own addresses in their
NICs. The DNS servers should also forward DNS requests for machines
outside the local network to an external DNS.

If all clients (including the DNS servers when they act as clients
themselves) are configured to look to the internal DNS service, and
the DNS Server has a zone for cooperativa.com then it should not look
for cooperativa on the Internet.

I don't know if the above actually has any bearing on your problem.
However, your reference to primary and secondary DNS makes me wonder.

Another thing - your DNS is not resolving the Domain Name for the DNS
server itself. You could try setting the domain name suffix to
cooperativa.com on the server NIC.

Cheers,

Cliff