WINS questions.

Hello.

We use for first-time the Wins-services.
2 DCs (win2k) which are also wins-server with each is push/pull
replicatpartner.

I have a few questions:

1. Must the Client are register in Both wins-servers?
Because of the replikation i think must (for fault-toleranz) .
Momentally, the most of them, are only in the first WINS-server
registered.

2. I have for a client varius registrations such [0h] workstation, [03]
messenger,[20h] file server, and again the same Workstation$ as [03]
messager.
How many entrys for a workstation must be there??
The clients DONT shares anything.


Configuration of the clients under TCP/IP properties--WinS--- are Fist
winserver 1DC, and Second winserver 2DC.

Clients are all WinXP prof.

Thanks.

Hello marsias,

WINS is not required in a network that consists entirely of computers running
Windows 2000, Windows XP, Windows Server 2003, or other TCP/IP-based systems,
such as most versions of UNIX, that fully support the use of Domain Name
System (DNS) names.
So why will you use it, DNS in active directory integrated mode is the better
solution for you. Or did you use some older software that requires WINS?


Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Hello.
>
> We use for first-time the Wins-services.
> 2 DCs (win2k) which are also wins-server with each is push/pull
> replicatpartner.
> I have a few questions:
>
> 1. Must the Client are register in Both wins-servers?
> Because of the replikation i think must (for fault-toleranz) .
> Momentally, the most of them, are only in the first WINS-server
> registered.
> 2. I have for a client varius registrations such [0h] workstation,
> [03]
> messenger,[20h] file server, and again the same Workstation$ as [03]
> messager.
> How many entrys for a workstation must be there??
> The clients DONT shares anything.
> Configuration of the clients under TCP/IP properties--WinS--- are Fist
> winserver 1DC, and Second winserver 2DC.
>
> Clients are all WinXP prof.
>
> Thanks.
>

In news:(E-Mail Removed) .com,
Myweb <(E-Mail Removed)> typed:
> Hello marsias,
>
> WINS is not required in a network that consists entirely of computers
> running Windows 2000, Windows XP, Windows Server 2003, or other
> TCP/IP-based systems, such as most versions of UNIX, that fully
> support the use of Domain Name System (DNS) names.
> So why will you use it, DNS in active directory integrated mode is
> the better solution for you. Or did you use some older software that
> requires WINS?
>
> Best regards
>
> Myweb
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.

Hy Myweb,

Thsi is just a little note commenting on netBIOS requirements. Some apps,
such as even the latest version of Outlook with an Exchange account requires
NetBIOS for certain Outlook/Exchange features to work. There is actually a
tech article specfically stating this too. If in a multi-segmented
environment, including if allowing VPN traffic, WINS will be needed to
support netBIOS across the WAN. I'm not sure marsias has more than one
segment or not. I would imagine he does or wouldn't have decided to use
WINS. If he has only one segment, then of course WINS is overkill and not
required.

Ace

Hello.

We have only one sagment, all client are windows XP/2000-LAN . We have
Office XP/Outlook XP(2002) NO Exchange Server and a DFS Volume.

According off users here im forum, i need WINS if i have Outlook before
2003 and a DFS volume!!.
Which i have both.

I am not sure if a really need WINS.

be the way(Ace): I still have the frsyssvol in dcdiag log.

Thanks.

In news:(E-Mail Removed),
marsias <(E-Mail Removed)> typed:
> Hello.
>
> We have only one sagment, all client are windows XP/2000-LAN . We have
> Office XP/Outlook XP(2002) NO Exchange Server and a DFS Volume.
>
> According off users here im forum, i need WINS if i have Outlook
> before 2003 and a DFS volume!!.
> Which i have both.
>
> I am not sure if a really need WINS.
>
> be the way(Ace): I still have the frsyssvol in dcdiag log.
>
> Thanks.

Youa re still having problems with FRS? As I suggested, I really really
recommend calling Microsoft PSS. For $245 USD, they will fix it no matter
HOW LONG it takes them. If I were you, I would do it to insure all errors
are eradicated. If we try to do it thru the newsgroups, it will take too
long between postings and extracting information, etc. I would do it soon,
for if it continues, then one of your domain controllers will be useless
because if it cannot communicate with the other domain controller for more
than 60 days, you may as well rebuild the DC.

As for WINS, WINS offers NetBIOS name resolution. So if you have one segment
and VPN clients, yes you will need WINS. IF not and you only have one
segment, then it's not needed. And yes, Exchange/Outlook requires NetBIOS
communication.

Ace

>
> Youa re still having problems with FRS? As I suggested, I really really
> recommend calling Microsoft PSS. For $245 USD, they will fix it no matter
> HOW LONG it takes them. If I were you, I would do it to insure all errors
> are eradicated. If we try to do it thru the newsgroups, it will take too
> long between postings and extracting information, etc. I would do it soon,
> for if it continues, then one of your domain controllers will be useless
> because if it cannot communicate with the other domain controller for more
> than 60 days, you may as well rebuild the DC.

Hello Ace.

This frssysvol error, i think, exist for a long time .
after i setup the two DCs, i have not change really inportant thinks on
DNS.

I have tested fault-toleranz one both machines with works without problems.

I think the problem is a "small" one, a link, a referenz etc. OR the
command dcdiag reports a error which dont exist !!

ALL others utilities/programs, event-viewer, reports no errors!

According to your links(of microsoft KB=312862) , i have also tested the
ntfrsutl ds server command with no errors/warnings.

> As for WINS, WINS offers NetBIOS name resolution. So if you have one
> segment and VPN clients, yes you will need WINS. IF not and you only have
> one segment, then it's not needed. And yes, Exchange/Outlook requires
> NetBIOS communication.

I think the DFS requires also WINS to work properly.
After i setup the WINS , i see that the clients, all are connected to
"primary" dfs folder first(DC1), which was not the case without WINS.
(clients was connect in random manner on DC1 or DC2 dfs shares before, which
was a Big problem)


nik.

In news:%23B$(E-Mail Removed),
marsias <(E-Mail Removed)> typed:

> Hello Ace.
>
> This frssysvol error, i think, exist for a long time .
> after i setup the two DCs, i have not change really inportant thinks
> on DNS.
>
> I have tested fault-toleranz one both machines with works without
> problems.
> I think the problem is a "small" one, a link, a referenz etc. OR the
> command dcdiag reports a error which dont exist !!
>
> ALL others utilities/programs, event-viewer, reports no errors!
>
> According to your links(of microsoft KB=312862) , i have also tested
> the ntfrsutl ds server command with no errors/warnings.
>
>> As for WINS, WINS offers NetBIOS name resolution. So if you have one
>> segment and VPN clients, yes you will need WINS. IF not and you only
>> have one segment, then it's not needed. And yes, Exchange/Outlook
>> requires NetBIOS communication.
>
> I think the DFS requires also WINS to work properly.
> After i setup the WINS , i see that the clients, all are connected to
> "primary" dfs folder first(DC1), which was not the case without WINS.
> (clients was connect in random manner on DC1 or DC2 dfs shares
> before, which was a Big problem)
>
>
> nik.

Check to see if you have the latest adminpak tools (which gives you dcdiag,
netdiag and numerous other tools). Install the adminpak.msi from and
extracted Windows2003 SP2 source because SP2 dcdiag has new features.:

What's New in Windows Server 2003 Service Pack 2
http://technet2.microsoft.com/window....mspx?mfr=true

DFS works on DNS. Ideally it is to be connected to by this method:
\\ATT-AEDAK.GR
or
\\ATT-AEDAK.GR\dfs\root

Of course you can use the NetBIOS name, which will get resolved to the
domain's NetBIOS name and since it is registered in WINS with one IP, it
will always go to that IP. But it doesn;t require WINS. DNS uses Round Robin
to access the root, which means it will bounce back and forth between all
the replicas. Therefore if you created additional replicas, then that is why
you are seeing that behavior.


Ace

Hello Ace.

> Check to see if you have the latest adminpak tools (which gives you
> dcdiag, netdiag and numerous other tools). Install the adminpak.msi from
> and extracted Windows2003 SP2 source because SP2 dcdiag has new features.:
>
> What's New in Windows Server 2003 Service Pack 2
> http://technet2.microsoft.com/window....mspx?mfr=true

We have win2000SP4 Server. Is this admim.pak also for our system??

I had try a new version from dcdiag.exe for win2000 with the same result.

> \\ATT-AEDAK.GR\dfs\root

This is the methode in which client are connected to dfs.

Under DFS is following:

\\ATT-AEDAK.GR\USERFILES Root Replica(s)
USERFILES \\aedak-server\userfiles
\\backup-server\userfiles
under USERFILES Replica(s)
\\Backup-server\userfiles

As for dcdiag error (frssysvol) , i had search to Internet others users have
also this problem but no one has a resolution for this, neither MICROSOFT.

I have tested the replication of SYSVOL be puting a file on one DC, which
was replicated immediatly to other.

Nik.

In news:(E-Mail Removed),
marsias <(E-Mail Removed)> typed:
> Hello Ace.
>
>> Check to see if you have the latest adminpak tools (which gives you
>> dcdiag, netdiag and numerous other tools). Install the adminpak.msi
>> from and extracted Windows2003 SP2 source because SP2 dcdiag has new
>> features.: What's New in Windows Server 2003 Service Pack 2
>> http://technet2.microsoft.com/window....mspx?mfr=true
>
> We have win2000SP4 Server. Is this admim.pak also for our system??
>
> I had try a new version from dcdiag.exe for win2000 with the same
> result.
>> \\ATT-AEDAK.GR\dfs\root
>
> This is the methode in which client are connected to dfs.
>
> Under DFS is following:
>
> \\ATT-AEDAK.GR\USERFILES Root Replica(s)
> USERFILES \\aedak-server\userfiles
>
> \\backup-server\userfiles under USERFILES
> Replica(s)
> \\Backup-server\userfiles
> As for dcdiag error (frssysvol) , i had search to Internet others
> users have also this problem but no one has a resolution for this,
> neither MICROSOFT.
> I have tested the replication of SYSVOL be puting a file on one DC,
> which was replicated immediatly to other.
>
> Nik.

The adminpak is for 2003. I forgot you have 2000.

The DFS connection method is fine. Thanks for responding to that.

You said Microsoft doesn't have a resolution? Did they tell you that when
you called Microsoft PSS? What else did they say?

Ace