Re: DNS Error

Cris,

I am saying that my clients are configured with a private IP address

Static IP address (192.168.16.x)
Gateway (192.168.16.1)
Primary DNS (192.168.16.2)
Alternate DNS (192.168.16.1)



Randy



"Cris Hanna [SBS - MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:OjMHBEeEJHA.4900@xxxxxxxxxxxxxxxxxxxxxxx
Are you saying all your units have PUBLIC or PRIVATE static IPs and if you've got workstations pointing to anything other than the SBS server, then this outside the recommended configuration most likely why your having issues. Have tried only pointing to SBS server and seeing if this goes away?

--
Cris Hanna [SBS - MVP]
Co-Author, Windows Small Business Server 2008 Unleashed
http://www.amazon.com/Windows-Small-Business-Server-Unleashed/dp/0672329573/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1217269967&sr=8-1

------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.

"-Draino-" <guest@xxxxxxxxxxx> wrote in message news:OIlPz4cEJHA.3616@xxxxxxxxxxxxxxxxxxxxxxx
Hi Miles Li

Not sure if this matter but I use static IP's on all clients. I only have 3, but it allows me to set an alternate DNS server to the router in case the server goes down, my clients will still have an internet connection.


Randy



"Miles Li [MSFT]" <v-mileli@xxxxxxxxxxxxxxxxxxxx> wrote in message news:adNWmjYEJHA.1300@xxxxxxxxxxxxxxxxxxxxxxxxx

Hello Randy,

Thank you for posting here.

According to your description, I understand that:

On Windows XP SP3 client, you receive the Event ID 5789 with the error
message "The parameter is incorrect" that indicates the system fails to
update DNS Host Name of the computer object in Active Directory.

If I have misunderstood the problem, please don't hesitate to let me know.

Suggestions:
=====================
This error indicates that DNS Clients were unable to register A record in
DNS. By default, computers that are statically configured for TCP/IP
attempt to dynamically register host (A) and pointer (PTR) resource records
(RRs) for IP addresses configured and used by their installed network
connections. By default, all computers register records based on their
fully qualified domain name (FQDN). Typically, the event ID 5789 results
from the missing of the primary DNS suffix of a computer. Please try to
check the settings as follows:

1. For a DHCP client, please make sure the Option 15 DNS domain name is
properly configured in the DHCP server--->Scope options. If it is missing
or with incorrect value, manually create/correct it. Then renew the IP
address release on the client to check how it works.

2. Please make sure the primary DNS suffix for the computer is properly
configured in the client's system properties dialog box.
a) Click start--->control panel--->System--->computer name tab.
b) Click Change--->More.
c) Check whether the correct DNS suffix is placed in the "Primary DNS
suffix of this computer" textbox.
d) If it is incorrect, change it to check how everything works.


More information for your reference:

258503 Event ID 5788 and event ID 5789 occur when the DNS domain
name and the Active Directory domain name differ on a Windows-based computer
http://support.microsoft.com/kb/258503

Dynamic update
http://technet.microsoft.com/en-us/library/cc784052.aspx


If we cannot resolve the issue after we perform the steps above, please
help me collect some information for further investigation:

Information needed:
==================
1. Please help to collect the MPS report on the problematic client.

Microsoft Product Support's Reporting Tools (MPSRPT_DirSvc.EXE)
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en

2. On the client, try to reproduce the issue and capture the network
traffic to indentify the root cause. You can get the network monitor from
the following link and install it on the problematic client.

Download the NetMon3.1 from the following link:
http://www.microsoft.com/downloads/details.aspx?FamilyID=18b1d59d-f4d8-4213-
8d17-2f6dde7d7aac&DisplayLang=en

a) Start the capture and run "ipconfig /renew" to reproduce the issue.

b) Stop the capture and save the network trace file

3. Please send the log files to me at Miles Li
<mailto:v-mileli@xxxxxxxxxxxxx>.

If you have any questions or concerns, please do not hesitate to let me
know.





Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.




.

Relevant Pages

  • Re: 70-294 next week
    ... to another DNS ... server for at least ... client, which then ... configuration on the client. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Still strange not fully working DNS server
    ... If nothing helps I guess the only optuin is to reinstall server, ... Ive removed that just a few hours ago and the GPO and DNS problem ... I also have disjoined and rejoined the client to the domain with ... Computer configuration, administrative templates, System, ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Error
    ... Which as Cris says can lead to problems with DNS if you're not very careful. ... you've got workstations pointing to anything other than the SBS server, ... then this outside the recommended configuration most likely why your ... For a DHCP client, please make sure the Option 15 DNS domain name is ...
    (microsoft.public.windows.server.sbs)
  • Re: Clients cannot find sharepoint
    ... The client machines had an entry in the append DNS ... Get ipconfig/all result on SBS and client computer. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Satellite Branch Office Woes
    ... The client machine has a hard-coded IP address that includes the DNS entry ... for the central site. ... or I am stuck with an WAN configuration ...
    (microsoft.public.windows.server.active_directory)
Loading