Windows 2003 can ping server with fqdn but not with netbios name

  • Thread starter Thread starter Ehren
  • Start date Start date
E

Ehren

Hi-

I have a very strange issue going on. I installed a new server today and
added it to the domain as a member server for hosting user home directories.
(Will replace our old slow and crappy server). I can access it just fine
using \\servername\share from almost any computer I can come in contact with.
However from both of our domain controllers the only way I can ping it or
access its shares is by using the fqdn (\\servername.domain.edu.local\share)
which is annoying.

Both domain controllers serve as AD integrated DNS servers each with itself
as its primary and the other as the secondary. ALl IP's are static. all the
servers are plugged into the same switch, there is no routing involved. I
flushed the NB cache as well as the dns cache and it all does the same.

Im annoyed and out of ideas, anyone have any others?
 
On Jul 13, 11:10 am, Ehren <Eh...@discussions.microsoft.com> wrote:
> Hi-
>
> I have a very strange issue going on. I installed a new server today and
> added it to the domain as a member server for hosting user home directories.
> (Will replace our old slow and crappy server). I can access it just fine
> using \\servername\share from almost any computer I can come in contact with.
> However from both of our domain controllers the only way I can ping it or
> access its shares is by using the fqdn (\\servername.domain.edu.local\share)
> which is annoying.
>
> Both domain controllers serve as AD integrated DNS servers each with itself
> as its primary and the other as the secondary. ALl IP's are static. all the
> servers are plugged into the same switch, there is no routing involved. I
> flushed the NB cache as well as the dns cache and it all does the same.
>
> Im annoyed and out of ideas, anyone have any others?

if the new server is 2003 and the clients are NT (did you mentioned
netbios names) you might look at running the newer servers in "mixed"
mode?
 
No, Everything is 2003. Every other computer in the network can "see" the
new server when you ping its name only. But for some reason only the two
domain controllers can not see it or ping it as the name only but can when
you use its fqdn.

The domain controllers are 2003 sp2, the new server is 2003 sp2, and the
clients are vista, xp and 2000.

Hopefully I made it clearer this time.

"wilscott1st@yahoo.com" wrote:

> On Jul 13, 11:10 am, Ehren <Eh...@discussions.microsoft.com> wrote:
> > Hi-
> >
> > I have a very strange issue going on. I installed a new server today and
> > added it to the domain as a member server for hosting user home directories.
> > (Will replace our old slow and crappy server). I can access it just fine
> > using \\servername\share from almost any computer I can come in contact with.
> > However from both of our domain controllers the only way I can ping it or
> > access its shares is by using the fqdn (\\servername.domain.edu.local\share)
> > which is annoying.
> >
> > Both domain controllers serve as AD integrated DNS servers each with itself
> > as its primary and the other as the secondary. ALl IP's are static. all the
> > servers are plugged into the same switch, there is no routing involved. I
> > flushed the NB cache as well as the dns cache and it all does the same.
> >
> > Im annoyed and out of ideas, anyone have any others?
>
> if the new server is 2003 and the clients are NT (did you mentioned
> netbios names) you might look at running the newer servers in "mixed"
> mode?
>
>
 
Ehren <Ehren@discussions.microsoft.com> wrote:
> Hi-
>
> I have a very strange issue going on. I installed a new server today
> and added it to the domain as a member server for hosting user home
> directories. (Will replace our old slow and crappy server). I can
> access it just fine using \\servername\share from almost any computer
> I can come in contact with. However from both of our domain
> controllers the only way I can ping it or access its shares is by
> using the fqdn (\\servername.domain.edu.local\share) which is
> annoying.
>
> Both domain controllers serve as AD integrated DNS servers each with
> itself as its primary and the other as the secondary. ALl IP's are
> static. all the servers are plugged into the same switch, there is
> no routing involved. I flushed the NB cache as well as the dns cache
> and it all does the same.
>
> Im annoyed and out of ideas, anyone have any others?

So, just to clarify -

You *can* ping servername.domain.edu.local successfully...
but
You *can't* ping servername and get a reply from servername.domain.edu.local
?

If so, check to ensure that both DCs have the same primary DNS suffix -
compare an ipconfig /all on each. They should both have domain.edu.local
listed at the top.
 
Hello! Thanks for your response.

Yes you are exactly correct, from both domain controllers I can ping
server.sd.domain.edu.intranet and get a response however can not ping
"server" and get a response.

Also like I said I can ping both from any other computer in the domain
(including mac and linux) and get a successful response (of course to ping
the fqdn on mac and linux or non domain computers I had to change the dns
servers temporarily).

I did ipconfig /all on both DC's and both list the dns suffix as
"sd.domain.edu.intranet" (where sd stands for Subdomain).

Any further options or ideas? Thanks kindly again for your response.

/Ehren

"Lanwench [MVP - Exchange]" wrote:

> Ehren <Ehren@discussions.microsoft.com> wrote:
> > Hi-
> >
> > I have a very strange issue going on. I installed a new server today
> > and added it to the domain as a member server for hosting user home
> > directories. (Will replace our old slow and crappy server). I can
> > access it just fine using \\servername\share from almost any computer
> > I can come in contact with. However from both of our domain
> > controllers the only way I can ping it or access its shares is by
> > using the fqdn (\\servername.domain.edu.local\share) which is
> > annoying.
> >
> > Both domain controllers serve as AD integrated DNS servers each with
> > itself as its primary and the other as the secondary. ALl IP's are
> > static. all the servers are plugged into the same switch, there is
> > no routing involved. I flushed the NB cache as well as the dns cache
> > and it all does the same.
> >
> > Im annoyed and out of ideas, anyone have any others?
>
> So, just to clarify -
>
> You *can* ping servername.domain.edu.local successfully...
> but
> You *can't* ping servername and get a reply from servername.domain.edu.local
> ?
>
> If so, check to ensure that both DCs have the same primary DNS suffix -
> compare an ipconfig /all on each. They should both have domain.edu.local
> listed at the top.
>
>
>
 
Ehren <Ehren@discussions.microsoft.com> wrote:
> Hello! Thanks for your response.
>
> Yes you are exactly correct, from both domain controllers I can ping
> server.sd.domain.edu.intranet and get a response however can not ping
> "server" and get a response.
>
> Also like I said I can ping both from any other computer in the domain
> (including mac and linux) and get a successful response (of course to
> ping the fqdn on mac and linux or non domain computers I had to
> change the dns servers temporarily).
>
> I did ipconfig /all on both DC's and both list the dns suffix as
> "sd.domain.edu.intranet" (where sd stands for Subdomain).

Does this work from a Windows workstation?
Can you post an unedited ipconfig /all from one of these servers, and from a
workstation?

>
> Any further options or ideas? Thanks kindly again for your response.
>
> /Ehren
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Ehren <Ehren@discussions.microsoft.com> wrote:
>>> Hi-
>>>
>>> I have a very strange issue going on. I installed a new server
>>> today and added it to the domain as a member server for hosting
>>> user home directories. (Will replace our old slow and crappy
>>> server). I can access it just fine using \\servername\share from
>>> almost any computer I can come in contact with. However from both
>>> of our domain controllers the only way I can ping it or access its
>>> shares is by using the fqdn (\\servername.domain.edu.local\share)
>>> which is annoying.
>>>
>>> Both domain controllers serve as AD integrated DNS servers each with
>>> itself as its primary and the other as the secondary. ALl IP's are
>>> static. all the servers are plugged into the same switch, there is
>>> no routing involved. I flushed the NB cache as well as the dns
>>> cache and it all does the same.
>>>
>>> Im annoyed and out of ideas, anyone have any others?
>>
>> So, just to clarify -
>>
>> You *can* ping servername.domain.edu.local successfully...
>> but
>> You *can't* ping servername and get a reply from
>> servername.domain.edu.local ?
>>
>> If so, check to ensure that both DCs have the same primary DNS
>> suffix - compare an ipconfig /all on each. They should both have
>> domain.edu.local listed at the top.
 
Ok, with your guidance I think I have figured it out. It was something to do
with the dns suffixes. Whoever set up these servers put in the proper
suffixes but neglected to put the .intranet at the end. I added that and now
at least at first glance it seems to work as expected.

Thanks very much for your patience and leading me in the right direction!


U:\>
"Lanwench [MVP - Exchange]" wrote:

> Ehren <Ehren@discussions.microsoft.com> wrote:
> > Hello! Thanks for your response.
> >
> > Yes you are exactly correct, from both domain controllers I can ping
> > server.sd.domain.edu.intranet and get a response however can not ping
> > "server" and get a response.
> >
> > Also like I said I can ping both from any other computer in the domain
> > (including mac and linux) and get a successful response (of course to
> > ping the fqdn on mac and linux or non domain computers I had to
> > change the dns servers temporarily).
> >
> > I did ipconfig /all on both DC's and both list the dns suffix as
> > "sd.domain.edu.intranet" (where sd stands for Subdomain).
>
> Does this work from a Windows workstation?
> Can you post an unedited ipconfig /all from one of these servers, and from a
> workstation?
>
> >
> > Any further options or ideas? Thanks kindly again for your response.
> >
> > /Ehren
> >
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> Ehren <Ehren@discussions.microsoft.com> wrote:
> >>> Hi-
> >>>
> >>> I have a very strange issue going on. I installed a new server
> >>> today and added it to the domain as a member server for hosting
> >>> user home directories. (Will replace our old slow and crappy
> >>> server). I can access it just fine using \\servername\share from
> >>> almost any computer I can come in contact with. However from both
> >>> of our domain controllers the only way I can ping it or access its
> >>> shares is by using the fqdn (\\servername.domain.edu.local\share)
> >>> which is annoying.
> >>>
> >>> Both domain controllers serve as AD integrated DNS servers each with
> >>> itself as its primary and the other as the secondary. ALl IP's are
> >>> static. all the servers are plugged into the same switch, there is
> >>> no routing involved. I flushed the NB cache as well as the dns
> >>> cache and it all does the same.
> >>>
> >>> Im annoyed and out of ideas, anyone have any others?
> >>
> >> So, just to clarify -
> >>
> >> You *can* ping servername.domain.edu.local successfully...
> >> but
> >> You *can't* ping servername and get a reply from
> >> servername.domain.edu.local ?
> >>
> >> If so, check to ensure that both DCs have the same primary DNS
> >> suffix - compare an ipconfig /all on each. They should both have
> >> domain.edu.local listed at the top.
>
>
>
>
 
Ehren <Ehren@discussions.microsoft.com> wrote:
> Ok, with your guidance I think I have figured it out. It was
> something to do with the dns suffixes. Whoever set up these servers
> put in the proper suffixes but neglected to put the .intranet at the
> end. I added that and now at least at first glance it seems to work
> as expected.
>
> Thanks very much for your patience and leading me in the right
> direction!
>

No problem glad you found the culprit.


>
> U:\>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Ehren <Ehren@discussions.microsoft.com> wrote:
>>> Hello! Thanks for your response.
>>>
>>> Yes you are exactly correct, from both domain controllers I can ping
>>> server.sd.domain.edu.intranet and get a response however can not
>>> ping "server" and get a response.
>>>
>>> Also like I said I can ping both from any other computer in the
>>> domain (including mac and linux) and get a successful response (of
>>> course to ping the fqdn on mac and linux or non domain computers
>>> I had to change the dns servers temporarily).
>>>
>>> I did ipconfig /all on both DC's and both list the dns suffix as
>>> "sd.domain.edu.intranet" (where sd stands for Subdomain).
>>
>> Does this work from a Windows workstation?
>> Can you post an unedited ipconfig /all from one of these servers,
>> and from a workstation?
>>
>>>
>>> Any further options or ideas? Thanks kindly again for your
>>> response.
>>>
>>> /Ehren
>>>
>>> "Lanwench [MVP - Exchange]" wrote:
>>>
>>>> Ehren <Ehren@discussions.microsoft.com> wrote:
>>>>> Hi-
>>>>>
>>>>> I have a very strange issue going on. I installed a new server
>>>>> today and added it to the domain as a member server for hosting
>>>>> user home directories. (Will replace our old slow and crappy
>>>>> server). I can access it just fine using \\servername\share from
>>>>> almost any computer I can come in contact with. However from both
>>>>> of our domain controllers the only way I can ping it or access its
>>>>> shares is by using the fqdn (\\servername.domain.edu.local\share)
>>>>> which is annoying.
>>>>>
>>>>> Both domain controllers serve as AD integrated DNS servers each
>>>>> with itself as its primary and the other as the secondary. ALl
>>>>> IP's are static. all the servers are plugged into the same
>>>>> switch, there is no routing involved. I flushed the NB cache as
>>>>> well as the dns cache and it all does the same.
>>>>>
>>>>> Im annoyed and out of ideas, anyone have any others?
>>>>
>>>> So, just to clarify -
>>>>
>>>> You *can* ping servername.domain.edu.local successfully...
>>>> but
>>>> You *can't* ping servername and get a reply from
>>>> servername.domain.edu.local ?
>>>>
>>>> If so, check to ensure that both DCs have the same primary DNS
>>>> suffix - compare an ipconfig /all on each. They should both have
>>>> domain.edu.local listed at the top.
 
On Jul 16, 8:36 am, Ehren <Eh...@discussions.microsoft.com> wrote:
> Hello! Thanks for your response.
>
> Yes you are exactly correct, from both domain controllers I can ping
> server.sd.domain.edu.intranet and get a response however can not ping
> "server" and get a response.
>
> Also like I said I can ping both from any other computer in the domain
> (including mac and linux) and get a successful response (of course to ping
> the fqdn on mac and linux or non domain computers I had to change the dns
> servers temporarily).
>
> I did ipconfig /all on both DC's and both list the dns suffix as
> "sd.domain.edu.intranet" (where sd stands for Subdomain).
>
> Any further options or ideas? Thanks kindly again for your response.
>
> /Ehren
>
> "Lanwench [MVP - Exchange]" wrote:
>
>
>
> > Ehren <Eh...@discussions.microsoft.com> wrote:
> > > Hi-
>
> > > I have a very strange issue going on. I installed a new server today
> > > and added it to the domain as a member server for hosting user home
> > > directories. (Will replace our old slow and crappy server). I can
> > > access it just fine using \\servername\share from almost any computer
> > > I can come in contact with. However from both of our domain
> > > controllers the only way I can ping it or access its shares is by
> > > using the fqdn (\\servername.domain.edu.local\share) which is
> > > annoying.
>
> > > Both domain controllers serve as AD integrated DNS servers each with
> > > itself as its primary and the other as the secondary. ALl IP's are
> > > static. all the servers are plugged into the same switch, there is
> > > no routing involved. I flushed the NB cache as well as the dns cache
> > > and it all does the same.
>
> > > Im annoyed and out of ideas, anyone have any others?
>
> > So, just to clarify -
>
> > You *can* ping servername.domain.edu.local successfully...
> > but
> > You *can't* ping servername and get a reply from servername.domain.edu.local
> > ?
>
> > If so, check to ensure that both DCs have the same primary DNS suffix -
> > compare an ipconfig /all on each. They should both have domain.edu.local
> > listed at the top.- Hide quoted text -
>
> - Show quoted text -

Perhaps in the network connections on the DCs you go to TCP/IP
properties, then advanced, then DNS and append the DNS suffix in the
box provided. Also you could try using the DNS suffix in registration
(tick the box on the same page).
 
Back
Top