IP to hostname resolution

I have purchased a few External Drives from Western Digital which are IP
based.

While a lot of people can access the device via hostname either seeing
through browsing or file, run and then \\name, but for some reason some
machines cannot access it by name. But they can access by the ip address i.e.
run and then \\x.x.x.x . One solution was to modify each person’s ‘hosts’
file, which did work, but I find it cumbersome and like giving up. I did
modify the ‘hosts’ of the root DC, which did help some machines, but not all.

--
Thanks
am7777


am7777

Hello,

i am pretty sure the DC hosts file is for nothing in making workstation
reaching the NAS.

This is a netbios resolution issue. You may work around it by adding your
NAS name in your DNS (in the integrated zone of your AD).


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"am7777" <(E-Mail Removed)> wrote in message
news:EBB5186E-3915-4FE3-9586-(E-Mail Removed)...
>I have purchased a few External Drives from Western Digital which are IP
> based.
>
> While a lot of people can access the device via hostname either seeing
> through browsing or file, run and then \\name, but for some reason some
> machines cannot access it by name. But they can access by the ip address
> i.e.
> run and then \\x.x.x.x . One solution was to modify each person’s ‘hosts’
> file, which did work, but I find it cumbersome and like giving up. I did
> modify the ‘hosts’ of the root DC, which did help some machines, but not
> all.
>
> --
> Thanks
> am7777

Thanks for the response. Where will I find the Integration Zone in the AD?


--
Thanks
am7777


"Mathieu CHATEAU" wrote:

> Hello,
>
> i am pretty sure the DC hosts file is for nothing in making workstation
> reaching the NAS.
>
> This is a netbios resolution issue. You may work around it by adding your
> NAS name in your DNS (in the integrated zone of your AD).
>
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "am7777" <(E-Mail Removed)> wrote in message
> news:EBB5186E-3915-4FE3-9586-(E-Mail Removed)...
> >I have purchased a few External Drives from Western Digital which are IP
> > based.
> >
> > While a lot of people can access the device via hostname either seeing
> > through browsing or file, run and then \\name, but for some reason some
> > machines cannot access it by name. But they can access by the ip address
> > i.e.
> > run and then \\x.x.x.x . One solution was to modify each person’s ‘hosts’
> > file, which did work, but I find it cumbersome and like giving up. I did
> > modify the ‘hosts’ of the root DC, which did help some machines, but not
> > all.
> >
> > --
> > Thanks
> > am7777
>
>

your DC would be also a DNS Server.
In the DNS console (MMC), you will find your domain in the lookup forward.
Add your host there.


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"am7777" <(E-Mail Removed)> wrote in message
news:77F6CF90-2921-41AA-91BA-(E-Mail Removed)...
> Thanks for the response. Where will I find the Integration Zone in the AD?
>
>
> --
> Thanks
> am7777
>
>
> "Mathieu CHATEAU" wrote:
>
>> Hello,
>>
>> i am pretty sure the DC hosts file is for nothing in making workstation
>> reaching the NAS.
>>
>> This is a netbios resolution issue. You may work around it by adding your
>> NAS name in your DNS (in the integrated zone of your AD).
>>
>>
>> --
>> Cordialement,
>> Mathieu CHATEAU
>> http://lordoftheping.blogspot.com
>>
>>
>> "am7777" <(E-Mail Removed)> wrote in message
>> news:EBB5186E-3915-4FE3-9586-(E-Mail Removed)...
>> >I have purchased a few External Drives from Western Digital which are IP
>> > based.
>> >
>> > While a lot of people can access the device via hostname either seeing
>> > through browsing or file, run and then \\name, but for some reason some
>> > machines cannot access it by name. But they can access by the ip
>> > address
>> > i.e.
>> > run and then \\x.x.x.x . One solution was to modify each person’s
>> > ‘hosts’
>> > file, which did work, but I find it cumbersome and like giving up. I
>> > did
>> > modify the ‘hosts’ of the root DC, which did help some machines, but
>> > not
>> > all.
>> >
>> > --
>> > Thanks
>> > am7777
>>
>>