Re: Domain authentication problem
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Mon, 7 Jan 2008 23:26:55 -0500
In news:C26B0389-F699-4993-AC21-D051820B31D2@xxxxxxxxxxxxx,
Newell White <NewellWhite@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
OK I guess that restarting DHCP service restored the default
configuration of Dynamic DNS, hence updates now enabled. My brain not
at full speed 8a.m. (UK time) on Monday morning!
So I will monitor memory usage of tcpsvcs.exe to see if MS have fixed
this bug, or to free up the memory as recommended in kb/939928 when
required.
Ok, so you followed the article's instructions to retrieve and install the
hotfix? If so, there's no need to disable DHCP's ability to automatically
perform updates for clients. Curious, what symptoms did you observed to
believe you needed this hotfix? So far I've handled a large client base and
have not ever had a problem or seen this issue. Maybe you can elborate so I
can understand.
Also, you mentioned this earlier:
/begin quote:
Somethimes when I ping some machine, the IP isnt returned. So I cant/end quote
reach those machines.
The bigest problem, is within shared folders. Even when I can find a
machine (my server i.e.), and I try to enter in \\server, windows ask for
my password! but I already input that at windows login, when I try again,
Here is a summarized list of possible causes:
1. Single label name.
2. SRV records missing.
3. Disjointed namespace.- AD domain name doesn't match the Primary DNS
Suffix and/or the zone name.
4. Using an ISP's DNS in IP properties of the DC and clients.
5. DHCP Client service disabled.
6. DCs are possibly multihomed (more than one NIC not teamed)
7. 3rd party firewalls
8. Antivirus software blocking functionality
9. Antispyware blocking functionality
10. etc....
I think we should help you with this issue, since it is your original
question. I am still curious about the memory leak issue. However, to help
with your original problem, please post the following information. This will
help us to help you better. - Thanks!
1. Unedited ipconfig /all from two of your DCs, and one of your clients..
2. The exact zone name spellng in DNS and whether updates are allowed on the
zone.
3. The AD DNS domain name as it shows up in ADUC.
4. If the SRV records exist under your zone.
5. Any errors in the Event logs on the DC under System, Replication Service
and Directory Services (post the Event ID# and Source names please)
6. Dcdiag /v /fix > c:\dcdiag.txt (post the dcdiag.txt as an attachment)
7. Netdiag /v /fix > c:\netdiag.txt (post the dcdiag.txt as an attachment)
8. More than one subnet?
9. Forwarder(s) configured?
Ace
.
- Follow-Ups:
- Re: Domain authentication problem
- From: Newell White
- Re: Domain authentication problem
- References:
- Domain authentication problem
- From: Feijó
- Re: Domain authentication problem
- From: Phillip Windell
- Re: Domain authentication problem
- From: Feijó
- Re: Domain authentication problem
- From: Phillip Windell
- Re: Domain authentication problem
- From: Bill Grant
- Re: Domain authentication problem
- From: Ace Fekay [MVP]
- Re: Domain authentication problem
- From: Newell White
- Re: Domain authentication problem
- From: Ace Fekay [MVP]
- Re: Domain authentication problem
- From: Newell White
- Domain authentication problem
- Prev by Date: Re: RRAS replacement
- Next by Date: how to mount NFS drive from Win XP to Solaris 10?
- Previous by thread: Re: Domain authentication problem
- Next by thread: Re: Domain authentication problem
- Index(es):
Relevant Pages
|
Loading