I had noticed this before in BackupExec but didn't really pay any attention
to it at the time. This is not a BE question. But I saw it again today and
thought I'd look into it more. I'm the only IT person at this company, and
have only been here for a short while.

Our internal domain name in AD is BD.local
In BE I saw BD and BD.local
In AD Users and Computers, I only see BD.local
In Network Neighborhood>Microsoft Windows Network I see BD and BD.local
Why would it show up this way? With the dot-local, and without it?

Under MS Windows Network if I double-click on BD.local I see only 2
computers. And they are in a different building then our 2 DC's. The
building is connected via fiber, from switch to switch. Same subnet.
When I double-click on BD I see all the rest of our computers.

Why is it showing up this way? Seems very odd to me.

Hi JohnB,

Windows traditionally maintain two name resolution systems:

a) NetBIOS name resolution
This is what you see as BD. NetBIOS has a single level name space. The names
consist of 15 characters + 1 character that identifies service, unique or
group type.

b) DNS
This is what you see as BD.local
DNS has a hierarchical name space, like
bd.local
projects.bd.local
special.projects.bd.local
etc

You may find more about mentioned name resolution systems on the Internet by
using your prefered web search.

"JohnB" <jbrigan@newsgroup> wrote in message
news:OuKJudwXKHA.3612@newsgroup

> I had noticed this before in BackupExec but didn't really pay any
> attention to it at the time. This is not a BE question. But I saw it
> again today and thought I'd look into it more. I'm the only IT person at
> this company, and have only been here for a short while.
>
> Our internal domain name in AD is BD.local
> In BE I saw BD and BD.local
> In AD Users and Computers, I only see BD.local
> In Network Neighborhood>Microsoft Windows Network I see BD and BD.local
> Why would it show up this way? With the dot-local, and without it?
>
> Under MS Windows Network if I double-click on BD.local I see only 2
> computers. And they are in a different building then our 2 DC's. The
> building is connected via fiber, from switch to switch. Same subnet.
> When I double-click on BD I see all the rest of our computers.
>
> Why is it showing up this way? Seems very odd to me.
>

"Dusko Savatovic" <savatovic@newsgroup> wrote in message
news:%23c2TrYzXKHA.1280@newsgroup

> Hi JohnB,
>
> Windows traditionally maintain two name resolution systems:
>
> a) NetBIOS name resolution
> This is what you see as BD. NetBIOS has a single level name space. The
> names consist of 15 characters + 1 character that identifies service,
> unique or group type.
>
> b) DNS
> This is what you see as BD.local
> DNS has a hierarchical name space, like
> bd.local
> projects.bd.local
> special.projects.bd.local
> etc
>
> You may find more about mentioned name resolution systems on the Internet
> by using your prefered web search.
>

Dusko,

Doesn't this sounds like Windows 2000? IIRC, the dsfolders.dll was pulled
from 2003, XP and newer operating systems, which provided the ability to see
the AD DNS name in Network Neighborhood, unless someone got a hold of that
DLL and registered it into a newer OS.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

I realize there's the DNS domain name and the NetBIOS domain name but, I had
never seen the DNS domain name show up in Windows Explorer.

And yes, there is a 2000 Server box here. Not sure what you're saying;
should I look for a file named dsfolders.dll?
It isn't causing any kind of problems. I was just curious, as I had never
seen it at other places that I've worked.

>
> Dusko,
>
> Doesn't this sounds like Windows 2000? IIRC, the dsfolders.dll was pulled
> from 2003, XP and newer operating systems, which provided the ability to
> see the AD DNS name in Network Neighborhood, unless someone got a hold of
> that DLL and registered it into a newer OS.
>
>
> --
> Ace

>
>

"JohnB" <jbrigan@newsgroup> wrote in message
news:OBD7K9TYKHA.3428@newsgroup

>I realize there's the DNS domain name and the NetBIOS domain name but, I
>had never seen the DNS domain name show up in Windows Explorer.
>
> And yes, there is a 2000 Server box here. Not sure what you're saying;
> should I look for a file named dsfolders.dll?
> It isn't causing any kind of problems. I was just curious, as I had never
> seen it at other places that I've worked.
>

That featuer was in 2000, to see the AD DNS name in the neighborhood, but
was pulled in subsequent releases. NOthing to worry about. You can actually
find that DLL in 2000, copy it to a newer OS and register the DLL to get the
same functionality. However, it exposes the AD structure, which why it was
pulled. I would leave it alone.

:-)

Ace