Re: Domain controller not found

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello Jim,

Sorry for asking again about the 192.168.0.1 Did you use it anywhere in the network? You said the router is x.x.1.4 and now you say the gateway "knows"? the address. This address has nothing to do with your network.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

No, the gateway/router is the only device that "knows" that IP.

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb666457d8c9e42b3e1ce408@xxxxxxxxxxxxxxxxxxxxxxx

Hello Jim,

So the 192.168.0.1 is not longer used on any server or workstation?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
1.4 is the only default gateway/router. It's WAN port is hooked up
to the DSL modem and it gets it's external IP and DNS info from the
modem. But all that should be transparent to the office network, and
it has worked fine for quite some time. It just seems that the DNS
and/or Active Directory services have been slowly degrading.

Again, the forwarders on the DC's DNS properties are the external
ones QWest uses for the DSL connection.

Thanks again,
Jim
"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66643908c9e3dcc1fc19e0@xxxxxxxxxxxxxxxxxxxxxxx
Hello Jim,

Coming back to the ip settings. Your workstations and server works
with ip's like 192.168.1.4 192.168.1.10 192.168.1.102

The router (Default gateway) ip 192.168.0.1

And you specify also 192.168.1.4 as a default gateway. Can you give
some more info about the network setup please. You can not work
with two default gateways in one network that have different ip
ranges.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers no rights.
Okay, I have only the DC given out as a DNS. But, I am getting the
same error messages on startup.

But, with the DHCP server giving out only the DC as the DNS, my
browser cannot resolve DNS requests. So either the DNS on the
server is not forwarding or something.

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66640c68c9e3a0c62b7c4f@xxxxxxxxxxxxxxxxxxxxxxx

Hello Jim,

see inline

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers no rights.
Thanks for getting back to me!

The modem IP was not in the forwarders list. Only two DNS's that
belong to QWest.

The 192.168.0.1 ip was in the network card TCP/IP properties as
the secondary DNS. I changed that to 192.168.1.4 which is the
gateway. Unless I should just leave it blank

The NIC should only point to your INTERNAL DNS server, that's
all.

Here are the startup errors now on the XP workstation, which
takes, again, about 5 minutes to get a functional desktop:

Windows cannot determine the user or computer name. (The
specified domain either does not exist or could not be
contacted. ). Group Policy processing aborted.

Automatic certificate enrollment for local system failed to
contact the active directory (0x8007054b). The specified domain
either does not exist or could not be contacted.

The PrintQueue Container could not be found because the DNS
Domain name could not be retrieved. Error: 54b

This will depend on the ip address from the router, remove it
like i wrote before. DNS settings should only point to the
internal DNS. In the moment the computer tries to find the domain
also outside your network, what will not work.

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb6663f788c9e360c93c57f0@xxxxxxxxxxxxxxxxxxxxxxx

Hello Jim,

Is the first problem solved? Other wise lets go on with that.
Did you remove the entry from DNS settings?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no
warranties,
and
confers no rights.
Well, the external DNS is already set up in the forwarders
tab. I rechecked the IP's, and they are what the DSL modem is
using.

Another symptom: now my XP machine is taking 30 to 60 seconds
just to open programs. But, when I'm off the net, they come
right up, as does the desktop.

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb6663be58c9e2eddcd97c4c@xxxxxxxxxxxxxxxxxxxxxxx

Hello Jim,

You have to configure a forwarder to your ISP's DNS server on
the
DNS
server properties in the DNS management console. Here you
find
a
tab
called "Forwarders". If it is greyed out inside just remove
the
.zone
in
DNS, close the DNS console and reopen it. Then you can add
the
ISP's
DNS
server, not your router ip address. It should be an external
internet
ip
address.
So all internal request from the machines go to your inside
DNS
server, if
that can't provide the information it will forward the
request
to
the
ISP's DNS server and get theire the answer.
Remove the modem ip address and your internal errors should
go
away.
But
you also be aible to browse the internet.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no
warranties,
and
confers no rights.
That is a DSL modem, on the other side of the gateway, which
is supposed to forward to an external DNS if 192.168.1.10 is
unable to fulfill the request. What is the ideal setting for
the secondary DNS? What would this have to do with finding
the DC?

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb6662eaf8c9e0cb6d3afa70@xxxxxxxxxxxxxxxxxxxxxxx

Hello Jim,

What is the 192.168.0.1 for a machine? It is a different
network
address
and can cause your problems.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no
warranties,
and
confers no rights.
192.168.0.1



.

Relevant Pages

  • Random Network Disconnects
    ... network and the only way I can seem to get it back up is to restart the box. ... Testing IpConfig - pinging the Secondary WINS server... ... DNS Host Name: itdspstest01.itd.edited.edited ... Provider Version:2 ...
    (microsoft.public.windows.server.dns)
  • RE: Server 2003 Network problems since IP address change
    ... Rightclick "My Computer", properties, Computer name or network identification, ... Is there any firewall running on client or server? ... Is the Primary DNS ... of zone WSW.local. ...
    (microsoft.public.windows.server.networking)
  • Re: Single NIC configuration with cable modem/router
    ... Internal or single network adapter configuration ... Verify the Domain Name System (DNS) pointers. ... Right-click Server Local Area Connection, ...
    (microsoft.public.windows.server.sbs)
  • RE: Strange Irregular DNS/Networking Problems
    ... My network is not a complicated set up and only has one domain controller. ... problems with DNS resolving after changing DNS servers. ... I was already using the server for DHCP. ...
    (microsoft.public.windows.server.dns)
  • Re: .com domain not accessible from .local workstations. Server O
    ... I was able to get rid of it by resetting it up as the only gateway ... DNS server listed for both the Lan nic and the Internet nic should list ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)