Hi,

I have a very small network (2 DCs, 1 of which is the GC), switched (no
VLANs) and approx. 850 PC's.

DNS appears to be setup correctly, however, some PC's can ping the name of
the server and get a response, while a few others cannot ping the name of the
server without using the FQDN...
this is causing some havoc on the PC's with ODBC connections because the
connector was initially set with just the hostname (it did work approx 3
weeks ago).

Here is what has changed: Replaced old DC with new DC (hardware), Brought
online a new DC, installed DNS, removed DNS from old DC (allowed 24 hrs
before decommission and removal of DNS) and then decommissioned the old DC.
All roles were moved over successfully. Event viewer logs do not indicate a
problem with name resolution, but I am having a problem on a few PC's in the
district.

(I did not keep the same DC name; new DC has new name)

Any greatly appreciated,
thanks,
Mel

Mel wrote:
> Hi,
>
> I have a very small network (2 DCs, 1 of which is the GC), switched
> (no VLANs) and approx. 850 PC's.
>
> DNS appears to be setup correctly, however, some PC's can ping the
> name of the server and get a response, while a few others cannot ping
> the name of the server without using the FQDN...
> this is causing some havoc on the PC's with ODBC connections because
> the connector was initially set with just the hostname (it did work
> approx 3 weeks ago).
>
> Here is what has changed: Replaced old DC with new DC (hardware),
> Brought online a new DC, installed DNS, removed DNS from old DC
> (allowed 24 hrs before decommission and removal of DNS) and then
> decommissioned the old DC. All roles were moved over successfully.
> Event viewer logs do not indicate a problem with name resolution, but
> I am having a problem on a few PC's in the district.
>
> (I did not keep the same DC name; new DC has new name)

Short hostname resolution is a function of WINS, NetBIOS, or have the proper
DNS suffix search list.
If all clients are not getting host name resolution check the DNS suffix
search list in the ipconfig /all of those clients.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This s
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oe.com/OEBackup/Default.aspx
===================================

I have re-introduced WINS back in to the environment and made the changes to
all static PC's and servers...I believe this may have been the piece I missed
when bringing the new DC/DNS server online. I have been able to notice a
difference already.

thanks for the ,

Mel



"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Mel wrote:
> > Hi,
> >
> > I have a very small network (2 DCs, 1 of which is the GC), switched
> > (no VLANs) and approx. 850 PC's.
> >
> > DNS appears to be setup correctly, however, some PC's can ping the
> > name of the server and get a response, while a few others cannot ping
> > the name of the server without using the FQDN...
> > this is causing some havoc on the PC's with ODBC connections because
> > the connector was initially set with just the hostname (it did work
> > approx 3 weeks ago).
> >
> > Here is what has changed: Replaced old DC with new DC (hardware),
> > Brought online a new DC, installed DNS, removed DNS from old DC
> > (allowed 24 hrs before decommission and removal of DNS) and then
> > decommissioned the old DC. All roles were moved over successfully.
> > Event viewer logs do not indicate a problem with name resolution, but
> > I am having a problem on a few PC's in the district.
> >
> > (I did not keep the same DC name; new DC has new name)
>
> Short hostname resolution is a function of WINS, NetBIOS, or have the proper
> DNS suffix search list.
> If all clients are not getting host name resolution check the DNS suffix
> search list in the ipconfig /all of those clients.
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This s
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oe.com/OEBackup/Default.aspx
> ===================================
>
>
>