I'm not sure Jay seems to think that all machines should be pointing at 1
WINS server. At my last position we had WINS servers at each remote office
with all the clients at that location set to look at their local WINS
server. All WINS servers did push/pull replication with the main WINS
server at HQ. Each WINS server was set to look to itself for WINS (both
primary and secondary).
I never had any problem with deleting the WINS database and starting over.
Just write down any static mappings, blow it away and let it go again. It
will rebuild itself in a matter of a couple hours.
Disclaimer: This is the current user's personal opinion and is not made
on behalf of my employer.
-----Original Message-----
From: Scott Erwin [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 17, 2001 3:15 PM
To: NT System Admin Issues
Subject: RE: End of My Rope with WINS
I was wondering about that. I read somewhere that splitting clients between
WINS servers was good for some kind of fault tolerance. Anything to that?
-----Original Message-----
From: Jay Kulsh [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 17, 2001 3:47 PM
To: NT System Admin Issues
Subject: Re: End of My Rope with WINS
You wrote -
"All clients and other domain controllers are set up using their local wins
server as primary and the remote wins server as secondary. Is this OK?"
According to Roger S and many others, it is not Ok. You should have same
WINS server as primary for all subnets. Secondary server can be local
servers. Primary server would then only push, reducing the chance of any
corruption. (This way WINS configuration approximates DNS configuration.)
Jay
_______
Jay Kulsh
----- Original Message -----
From: "Scott Erwin" <[EMAIL PROTECTED]>
To: "NT System Admin Issues" <[EMAIL PROTECTED]>
Sent: Friday, August 17, 2001 11:39 AM
Subject: End of My Rope with WINS
>
> NT4 Network. I have two buildings, each on their own network connected by
> fiber. Pinging with ip address and netbios name between networks is no
> problem and searching for computers using netbios names works too. There
is
> a WINS server on each network configured as push and pull partners of each
> other. Each WINS server is its own Primary and Secondary. Browsing with
> Network Neighborhood is intermittent. Sometimes Network A sees Network B,
> sometimes it can't (and vice versa). I've never had simultaneous browsing.
I
> have never gotten a WINS error in the event viewer. I do get successful
> push/pull entries.
>
> All clients and other domain controllers are set up using their local wins
> server as primary and the remote wins server as secondary. Is this OK?
>
> All the required entries seem to be there [1C], [1Eh], [OOh], etc...
>
> I don't know what else to check for, and am close to deleting both
databases
> and starting over.
>
>
> Any advice?
> Scott
>
>
>
> http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
>
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
http://www.sunbelt-software.com/ntsysadmin_list_charter.htm
