Active directory adn Wins server

Hello everybody

Can you confirm that the following network configuration fon an active
direcory controller is an error? (wins configuration particulary)

DOMAIN-1 Active directory domain
DOMAIN-2 Nt domain

No relation or trust


server A (DOMAIN-A AD controller windows 2003 server)
ip 192.168.1.10
primary dns 192.168.1.10
secondary (dns another domain-1 AS controller windows 2003 server)
WINS SERVER 192.168.1.200 (DOMAIN-2 server B - PDC Windows 2000 server)


Is there an official documentation from Microsoft about this?

Thanks
Daniele

Hello Daniele,

Please post the complete ipconfig /all so we can verify it from all servers
in each domain.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Hello everybody
>
> Can you confirm that the following network configuration fon an active
> direcory controller is an error? (wins configuration particulary)
>
> DOMAIN-1 Active directory domain
> DOMAIN-2 Nt domain
> No relation or trust
>
> server A (DOMAIN-A AD controller windows 2003 server)
> ip 192.168.1.10
> primary dns 192.168.1.10
> secondary (dns another domain-1 AS controller windows 2003 server)
> WINS SERVER 192.168.1.200 (DOMAIN-2 server B - PDC Windows 2000
> server)
> Is there an official documentation from Microsoft about this?
>
> Thanks
> Daniele

"Daniele" <> wrote in message
news:hf0pfp$2uq$...
> Hello everybody
>
> Can you confirm that the following network configuration fon an active
> direcory controller is an error? (wins configuration particulary)
>
> DOMAIN-1 Active directory domain
> DOMAIN-2 Nt domain
>
> No relation or trust
>
>
> server A (DOMAIN-A AD controller windows 2003 server)
> ip 192.168.1.10
> primary dns 192.168.1.10
> secondary (dns another domain-1 AS controller windows 2003 server)
> WINS SERVER 192.168.1.200 (DOMAIN-2 server B - PDC Windows 2000 server)
>
>
> Is there an official documentation from Microsoft about this?
>
> Thanks
> Daniele
>
>


A WINS server address in IP properties should only be pointing to a WINS
server in its own domain/forest that has reference for all machines in its
own environment, not another domain/forest.

If you need to be able to resolve NetBIOS names in another forest, it's
recommended to create a two way trust, and create a WINS replication
partnership with the other forest's WINS server.

Configuring WINS replication: Windows Internet Name Service (WINS)Jan 21,
2005 ... A pull replication trigger is sent to other WINS servers based on
the configured Replication interval set in Replication Partners Properties
....
http://technet.microsoft.com/en-us/l...54(WS.10).aspx

Best Practices for WINS Replication. Configuring replication correctly can
avert many problems, and doing so enables a group of WINS servers to
function ...
http://technet.microsoft.com/en-us/l.../cc959260.aspx

Also, if a machine is a WINS server, whether it is a domain controller or
not, should only point to itself. If a WINS server is pointing to something
else other than itself, or in addition to itself, registration problems
occur. Non-WINS server machines can be set to use more than one safely, but
a WINS server must always point to itself.

Setting Primary and secondary WINS server optionsWe recommend that a WINS
server point to itself as Primary WINS in the TCP/IP configuration. If you
try to specify the same WINS address in the Secondary ...
http://support.microsoft.com/kb/150737

WINS Best Practices: Windows Internet Name Service (WINS)Jan 21, 2005 ...
Best practices. Use default settings to configure WINS servers. ... For best
results in WINS replication and convergence time, ...
http://technet.microsoft.com/en-us/l...59(WS.10).aspx

However, as Meinolf requested, it is still best for us to see an ipconfig
/all from all of your DCs. You can easily copy/paste it from the command
prompt, or you can run the command wtih the following method to put it into
a text file called ipconfig.txt on C: drive, which you can copy and paste to
your reply.

ipconfig /all > c:\ipconfig.txt


--
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.

Ace Fekay [MCT] ha scritto:
> "Daniele" <> wrote in message
> news:hf0pfp$2uq$...
>> Hello everybody
>>
>> Can you confirm that the following network configuration fon an active
>> direcory controller is an error? (wins configuration particulary)
>>
>> DOMAIN-1 Active directory domain
>> DOMAIN-2 Nt domain
>>
>> No relation or trust
>>
>>
>> server A (DOMAIN-A AD controller windows 2003 server)
>> ip 192.168.1.10
>> primary dns 192.168.1.10
>> secondary (dns another domain-1 AS controller windows 2003 server)
>> WINS SERVER 192.168.1.200 (DOMAIN-2 server B - PDC Windows 2000 server)
>>
>>
>> Is there an official documentation from Microsoft about this?
>>
>> Thanks
>> Daniele
>>
>>
>
>
> A WINS server address in IP properties should only be pointing to a WINS
> server in its own domain/forest that has reference for all machines in its
> own environment, not another domain/forest.
>
> If you need to be able to resolve NetBIOS names in another forest, it's
> recommended to create a two way trust, and create a WINS replication
> partnership with the other forest's WINS server.
>
> Configuring WINS replication: Windows Internet Name Service (WINS)Jan 21,
> 2005 ... A pull replication trigger is sent to other WINS servers based on
> the configured Replication interval set in Replication Partners Properties
> ...
> http://technet.microsoft.com/en-us/l...54(WS.10).aspx
>
> Best Practices for WINS Replication. Configuring replication correctly can
> avert many problems, and doing so enables a group of WINS servers to
> function ...
> http://technet.microsoft.com/en-us/l.../cc959260.aspx
>
> Also, if a machine is a WINS server, whether it is a domain controller or
> not, should only point to itself. If a WINS server is pointing to something
> else other than itself, or in addition to itself, registration problems
> occur. Non-WINS server machines can be set to use more than one safely, but
> a WINS server must always point to itself.
>
> Setting Primary and secondary WINS server optionsWe recommend that a WINS
> server point to itself as Primary WINS in the TCP/IP configuration. If you
> try to specify the same WINS address in the Secondary ...
> http://support.microsoft.com/kb/150737
>
> WINS Best Practices: Windows Internet Name Service (WINS)Jan 21, 2005 ...
> Best practices. Use default settings to configure WINS servers. ... For best
> results in WINS replication and convergence time, ...
> http://technet.microsoft.com/en-us/l...59(WS.10).aspx
>
> However, as Meinolf requested, it is still best for us to see an ipconfig
> /all from all of your DCs. You can easily copy/paste it from the command
> prompt, or you can run the command wtih the following method to put it into
> a text file called ipconfig.txt on C: drive, which you can copy and paste to
> your reply.
>
> ipconfig /all > c:\ipconfig.txt
>
>
Thanks for your reply

My goal is to resolve 'domain-2' machine names
from my Acrive direcotry domain (domain-1)

Somebody from our stuff put wins server into domain-1 as controller tcp
properties. this solutions one day works ,another day don't works.

I think it's an error because the wins server is from another older nt
domani without any trust with our.

here is ipconfig /all from domain-1 AD controller,(it's in italian but i
think it's clear anyway)

172.19.19.177/178/179 domain-1 ad controller
172.18.19.254/200 nt domain-2 pdc/bdc


Nome host . . . . . . . . . . . . . . : ssv-lap-svr3
Suffisso DNS primario . . . . . . . . : ssv-lab.loc
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Elenco di ricerca suffissi DNS. . . . : ssv-lab.loc

Scheda Ethernet Lan-BackEnd.Nodo3:

Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : HP NC7782 Gigabit Server
Adapter #2
Indirizzo fisico. . . . . . . . . . . : 00-14-C2-61-CE-26
DHCP abilitato. . . . . . . . . . . . : No
Indirizzo IP. . . . . . . . . . . . . : 172.19.19.179
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . : 172.19.19.15
Server DNS . . . . . . . . . . . . . : 172.19.19.177
172.19.19.178
172.19.19.179
Server WINS primario . . . . . . . . : 172.19.19.254
Server WINS secondario . . . . . . . : 172.19.19.200

Daniele

Hello Daniele,

Configure in the DNS servers of each domain a conditional forwarder or a
stub zone to the other domain. This should give you the option to resolve
the names.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Ace Fekay [MCT] ha scritto:
>
>> "Daniele" <> wrote in message
>> news:hf0pfp$2uq$...
>>
>>> Hello everybody
>>>
>>> Can you confirm that the following network configuration fon an
>>> active direcory controller is an error? (wins configuration
>>> particulary)
>>>
>>> DOMAIN-1 Active directory domain
>>> DOMAIN-2 Nt domain
>>> No relation or trust
>>>
>>> server A (DOMAIN-A AD controller windows 2003 server)
>>> ip 192.168.1.10
>>> primary dns 192.168.1.10
>>> secondary (dns another domain-1 AS controller windows 2003 server)
>>> WINS SERVER 192.168.1.200 (DOMAIN-2 server B - PDC Windows 2000
>>> server)
>>> Is there an official documentation from Microsoft about this?
>>>
>>> Thanks
>>> Daniele
>> A WINS server address in IP properties should only be pointing to a
>> WINS server in its own domain/forest that has reference for all
>> machines in its own environment, not another domain/forest.
>>
>> If you need to be able to resolve NetBIOS names in another forest,
>> it's recommended to create a two way trust, and create a WINS
>> replication partnership with the other forest's WINS server.
>>
>> Configuring WINS replication: Windows Internet Name Service (WINS)Jan
>> 21,
>> 2005 ... A pull replication trigger is sent to other WINS servers
>> based on
>> the configured Replication interval set in Replication Partners
>> Properties
>> ...
>> http://technet.microsoft.com/en-us/l...54(WS.10).aspx
>> Best Practices for WINS Replication. Configuring replication
>> correctly can
>> avert many problems, and doing so enables a group of WINS servers to
>> function ...
>> http://technet.microsoft.com/en-us/l.../cc959260.aspx
>> Also, if a machine is a WINS server, whether it is a domain
>> controller or not, should only point to itself. If a WINS server is
>> pointing to something else other than itself, or in addition to
>> itself, registration problems occur. Non-WINS server machines can be
>> set to use more than one safely, but a WINS server must always point
>> to itself.
>>
>> Setting Primary and secondary WINS server optionsWe recommend that a
>> WINS server point to itself as Primary WINS in the TCP/IP
>> configuration. If you try to specify the same WINS address in the
>> Secondary ... http://support.microsoft.com/kb/150737
>>
>> WINS Best Practices: Windows Internet Name Service (WINS)Jan 21, 2005
>> ... Best practices. Use default settings to configure WINS servers.
>> ... For best results in WINS replication and convergence time, ...
>> http://technet.microsoft.com/en-us/l...59(WS.10).aspx
>>
>> However, as Meinolf requested, it is still best for us to see an
>> ipconfig /all from all of your DCs. You can easily copy/paste it from
>> the command prompt, or you can run the command wtih the following
>> method to put it into a text file called ipconfig.txt on C: drive,
>> which you can copy and paste to your reply.
>>
>> ipconfig /all > c:\ipconfig.txt
>>
> Thanks for your reply
>
> My goal is to resolve 'domain-2' machine names
> from my Acrive direcotry domain (domain-1)
> Somebody from our stuff put wins server into domain-1 as controller
> tcp properties. this solutions one day works ,another day don't works.
>
> I think it's an error because the wins server is from another older
> nt domani without any trust with our.
>
> here is ipconfig /all from domain-1 AD controller,(it's in italian but
> i think it's clear anyway)
>
> 172.19.19.177/178/179 domain-1 ad controller
> 172.18.19.254/200 nt domain-2 pdc/bdc
> Nome host . . . . . . . . . . . . . . : ssv-lap-svr3
> Suffisso DNS primario . . . . . . . . : ssv-lab.loc
> Tipo nodo . . . . . . . . . . . . . . : Ibrido
> Routing IP abilitato. . . . . . . . . : No
> Proxy WINS abilitato . . . . . . . . : No
> Elenco di ricerca suffissi DNS. . . . : ssv-lab.loc
> Scheda Ethernet Lan-BackEnd.Nodo3:
>
> Suffisso DNS specifico per connessione:
> Descrizione . . . . . . . . . . . . . : HP NC7782 Gigabit Server
> Adapter #2
> Indirizzo fisico. . . . . . . . . . . : 00-14-C2-61-CE-26
> DHCP abilitato. . . . . . . . . . . . : No
> Indirizzo IP. . . . . . . . . . . . . : 172.19.19.179
> Subnet mask . . . . . . . . . . . . . : 255.255.255.0
> Gateway predefinito . . . . . . . . . : 172.19.19.15
> Server DNS . . . . . . . . . . . . . : 172.19.19.177
> 172.19.19.178
> 172.19.19.179
> Server WINS primario . . . . . . . . : 172.19.19.254
> Server WINS secondario . . . . . . . : 172.19.19.200
> Daniele
>

"Daniele" <> wrote in message
news:...
> Ace Fekay [MCT] ha scritto:
>> "Daniele" <> wrote in message
>> news:hf0pfp$2uq$...
>>> Hello everybody
>>>
>>> Can you confirm that the following network configuration fon an active
>>> direcory controller is an error? (wins configuration particulary)
>>>
>>> DOMAIN-1 Active directory domain
>>> DOMAIN-2 Nt domain
>>>
>>> No relation or trust
>>>
>>>
>>> server A (DOMAIN-A AD controller windows 2003 server)
>>> ip 192.168.1.10
>>> primary dns 192.168.1.10
>>> secondary (dns another domain-1 AS controller windows 2003 server)
>>> WINS SERVER 192.168.1.200 (DOMAIN-2 server B - PDC Windows 2000
>>> server)
>>>
>>>
>>> Is there an official documentation from Microsoft about this?
>>>
>>> Thanks
>>> Daniele
>>>
>>>
>>
>>
>> A WINS server address in IP properties should only be pointing to a WINS
>> server in its own domain/forest that has reference for all machines in
>> its own environment, not another domain/forest.
>>
>> If you need to be able to resolve NetBIOS names in another forest, it's
>> recommended to create a two way trust, and create a WINS replication
>> partnership with the other forest's WINS server.
>>
>> Configuring WINS replication: Windows Internet Name Service (WINS)Jan 21,
>> 2005 ... A pull replication trigger is sent to other WINS servers based
>> on the configured Replication interval set in Replication Partners
>> Properties ...
>> http://technet.microsoft.com/en-us/l...54(WS.10).aspx
>>
>> Best Practices for WINS Replication. Configuring replication correctly
>> can avert many problems, and doing so enables a group of WINS servers to
>> function ...
>> http://technet.microsoft.com/en-us/l.../cc959260.aspx
>>
>> Also, if a machine is a WINS server, whether it is a domain controller or
>> not, should only point to itself. If a WINS server is pointing to
>> something else other than itself, or in addition to itself, registration
>> problems occur. Non-WINS server machines can be set to use more than one
>> safely, but a WINS server must always point to itself.
>>
>> Setting Primary and secondary WINS server optionsWe recommend that a WINS
>> server point to itself as Primary WINS in the TCP/IP configuration. If
>> you try to specify the same WINS address in the Secondary ...
>> http://support.microsoft.com/kb/150737
>>
>> WINS Best Practices: Windows Internet Name Service (WINS)Jan 21, 2005 ...
>> Best practices. Use default settings to configure WINS servers. ... For
>> best results in WINS replication and convergence time, ...
>> http://technet.microsoft.com/en-us/l...59(WS.10).aspx
>>
>> However, as Meinolf requested, it is still best for us to see an ipconfig
>> /all from all of your DCs. You can easily copy/paste it from the command
>> prompt, or you can run the command wtih the following method to put it
>> into a text file called ipconfig.txt on C: drive, which you can copy and
>> paste to your reply.
>>
>> ipconfig /all > c:\ipconfig.txt
>>
>>
> Thanks for your reply
>
> My goal is to resolve 'domain-2' machine names
> from my Acrive direcotry domain (domain-1)
>
> Somebody from our stuff put wins server into domain-1 as controller tcp
> properties. this solutions one day works ,another day don't works.
>
> I think it's an error because the wins server is from another older nt
> domani without any trust with our.
>
> here is ipconfig /all from domain-1 AD controller,(it's in italian but i
> think it's clear anyway)
>
> 172.19.19.177/178/179 domain-1 ad controller
> 172.18.19.254/200 nt domain-2 pdc/bdc
>
>
> Nome host . . . . . . . . . . . . . . : ssv-lap-svr3
> Suffisso DNS primario . . . . . . . . : ssv-lab.loc
> Tipo nodo . . . . . . . . . . . . . . : Ibrido
> Routing IP abilitato. . . . . . . . . : No
> Proxy WINS abilitato . . . . . . . . : No
> Elenco di ricerca suffissi DNS. . . . : ssv-lab.loc
>
> Scheda Ethernet Lan-BackEnd.Nodo3:
>
> Suffisso DNS specifico per connessione:
> Descrizione . . . . . . . . . . . . . : HP NC7782 Gigabit Server
> Adapter #2
> Indirizzo fisico. . . . . . . . . . . : 00-14-C2-61-CE-26
> DHCP abilitato. . . . . . . . . . . . : No
> Indirizzo IP. . . . . . . . . . . . . : 172.19.19.179
> Subnet mask . . . . . . . . . . . . . : 255.255.255.0
> Gateway predefinito . . . . . . . . . : 172.19.19.15
> Server DNS . . . . . . . . . . . . . : 172.19.19.177
> 172.19.19.178
> 172.19.19.179
> Server WINS primario . . . . . . . . : 172.19.19.254
> Server WINS secondario . . . . . . . : 172.19.19.200
>
> Daniele
>
>
>

Thank you for posting the ipconfig. Do you have an ipconfig of the WINS
server, too, or is the above machine a WINS server?

For DNS, you should put itself as the first entry, then the others as 2nd
and 3rd.

You say one day it works, the next day it doesn't?

In a mixed scenario, as Meinolf mentioned, you can use a conditional
forwarder. But if NT4 is involved, a WINS partnership will better suite your
needs, otherwise, you will need to create static entries in your WINS server
for the NT4 machine.

I provided some articles, as you'ev asked. I hope you found them helpful.

Ace

>
> Thank you for posting the ipconfig. Do you have an ipconfig of the WINS
> server, too, or is the above machine a WINS server?

No
the wins server is from another company , we haven't any access to that
machine.(but we need to map use their printers"
The administrator is not collaborative. he says "we 've no problem in
our domain".



>
> For DNS, you should put itself as the first entry, then the others as 2nd
> and 3rd.
>
> You say one day it works, the next day it doesn't?

Yes

>
> In a mixed scenario, as Meinolf mentioned, you can use a conditional
> forwarder. But if NT4 is involved, a WINS partnership will better suite your
> needs, otherwise, you will need to create static entries in your WINS server
> for the NT4 machine.

I configured forwarder but doesn't work,
i think i'll try WINS partnership.
>
> I provided some articles, as you'ev asked. I hope you found them helpful.
>
> Ace
>
>
thank you very much

"Daniele" <> wrote in message
news:...
>
>>
>> Thank you for posting the ipconfig. Do you have an ipconfig of the WINS
>> server, too, or is the above machine a WINS server?
>
> No
> the wins server is from another company , we haven't any access to that
> machine.(but we need to map use their printers"
> The administrator is not collaborative. he says "we 've no problem in our
> domain".
>
>
>
>>
>> For DNS, you should put itself as the first entry, then the others as 2nd
>> and 3rd.
>>
>> You say one day it works, the next day it doesn't?
>
> Yes
>
>>
>> In a mixed scenario, as Meinolf mentioned, you can use a conditional
>> forwarder. But if NT4 is involved, a WINS partnership will better suite
>> your needs, otherwise, you will need to create static entries in your
>> WINS server for the NT4 machine.
>
> I configured forwarder but doesn't work,
> i think i'll try WINS partnership.
>>
>> I provided some articles, as you'ev asked. I hope you found them helpful.
>>
>> Ace
> thank you very much



WINS partnership may not work if not trusted. Maybe simply using their WINS
server?

Were these two WINS servers, their servers?
> Server WINS primario . . . . . . . . : 172.19.19.254
> Server WINS secondario . . . . . . . : 172.19.19.200

Ace