In my case, the alias must be attached to a network interface.
Each machine has several network interface. One of these interfaces has been
declared
automatically in the DNS when the machine has been inserted in the domain.
The idea is to split the IP flow between the different interfaces (for
security reason). Each application has to use one network interface. Each
application use directory sharing. So the idea is to use an alias mapping on
one IP address in order to force the flow to go throught this subnet.
Didier
"Brendon Rogers" <(E-Mail Removed)> a écrit dans le message de
news: %23WaqTJx%(E-Mail Removed)...
> http://www.jsifaq.com/SUBA/tip0000/rh0062.htm
>
> "Didier P" <(E-Mail Removed)> wrote in message
> news:OptvNAx%(E-Mail Removed)...
>> Hi All,
>>
>> We have a Windows 2003 domain with several machines (all of these
>> machines are Windows 2003 machines). These machines have each several
>> network interfaces. On the domain controler, we have a DNS server.
>> In the DNS server records we have :
>> - some for hostname and its IP address : these records have been created
>> automatically when these machines have been inserted in the 2003 domain
>> - some for "alias" and its IP address : these records have been created
>> manually, to map the other network interfaces of the machine and their IP
>> address.
>>
>> When on a machine we use commands like : net view \\hostname we can see
>> the shared directories. But if we use : net view \\alias (where alias is
>> the alias declared manually in the DNS records) we have an error ( error
>> type 52). The command : net view \\IPaddress (where IPAddress is the
>> address of alias) works well.
>>
>> Is there a way to have this (net view \\alias) working? Do we need to
>> install WINS server?
>>
>> Thanks for your help
>>
>> Didier
>>
>
>