Re: Problem With Win2K Server/DNS
- From: "Kurt" <lorentzenkurt@xxxxxxxxxxxxxxxxxx>
- Date: Sat, 17 Jun 2006 23:23:10 -0700
Sorry for the late reply, been offline for a week or so.
Some of what you say doesn't jive. If you are not connected to a public
network, there is no way you could be resolving public names. Also, to be
able to browse outside your local network, you must be connected to
something outside your local network. this suggests a DNS setting error.
Redirector failures are usually related to RPC, which usually falls back to
unresolved SRV records. Did you name your internal domain the same as some
public domain? That could be an issue. Can yo resolve your domain name (with
no host, i.e. "nslookup domain.local")? Does it resolve to your DC's IP
address? Do you have multiple NICs in the DC? If so, do they both have an IP
address in the same subnet? It's certain that you have a connectivity
problem, either physical or logical. If you've eliminated the possibility of
a bad switch, switchport, NIC, etc (the easy part), DNS is your next place
to look.
....kurt
"MKerr" <someone@somewhere> wrote in message
news:eWkQ3RbhGHA.4864@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
I posted a message on the networking thread as well, but I'm not
certain I explained myself well and a responder there thought I might have
a DNS problem...so, here goes: I have a Win2K Server DC, 1 W2K Advanced
Server member and 2 Win2K Server members on my network. There are 8
WinXP SP2 workstations. There is only the one DC.
I decided to format and reinstall the DC. I did so and brought it up
under a new domain name, re-created all user accounts, and joined the
member systems to the new domain. They joined up just fine. However,
accessing the DC is extremely slow. If I try to transfer files to it, a
progress bar will come up and it will make it approximately 50% through
the transfer and then fail. Transfers from the DC to any of the other
systems in the network go well.
We are not on any sort of public network, but external references for
addresses seem to resolve ok. The only method I'm using to prove this is
that I can pull up a web browser and browse outside our local network.
I've installed DCDiag on both the DC and an XP client. Using the
/test:DNS option, everything passes both when run locally on the DC and
when run from an XP client logged into the domain. I do get a warning on
security for dynamic updates. Netdiag tests all pass as well. The DNS
zone is AD Integrated.
In addition to the copy problem mentioned above, accessing data on the DC
is extremely slow....browsing its event logs from an XP client, for
example. It takes a long time just to access the log, however, if I choose
any other computer in the domain, no slowness is noted.
When a user logs into the domain I do get an event 537 with a code of
0xC000005E. Which, after researching seems to be a nonspecific failure
during logon. However, the user is still logged in. Also, I'm getting
Event 3019 occuring from multple clients, which would seem to imply that
their redirectors can't determine their connection type. Which seems odd
to me.
I've been trying to go over everything everday this week hoping to resolve
the problem(s), but I'm completely stumped. Any help is greatly
appreciated. Please let me know if you need further information and I
will be happy to provide it.
.
- References:
- Problem With Win2K Server/DNS
- From: MKerr
- Problem With Win2K Server/DNS
- Prev by Date: Re: solution - active directory and dns problem - no _msdcs etc srv records
- Next by Date: Re: Duplicate name on the network, dns resolved
- Previous by thread: Problem With Win2K Server/DNS
- Next by thread: Utility/tool to resolve a list of names
- Index(es):
Relevant Pages
|
