Networking Forums

Networking Forums > Computer Networking > Windows Networking > Wins Newbie Question

Reply
Thread Tools Display Modes

Wins Newbie Question

 
 
Thomas R Grassi Jr
Guest
Posts: n/a

 
      03-21-2009, 11:28 PM
I have 2 Windows 2003 R2 Standard DC servers SP2 running WINS DNS and one
DHCP server.

The Wins is my question

I get this error only when one server is down for maint or a restart.

Type: Error
Date: 3/20/2009
Time: 7:14:26 PM
Event: 4102
Source: Wins
Category: None
User: N/A
Computer: TGCS001
Description:
The connection was aborted by the remote WINS. Remote WINS may not be
configured to replicate with the server.

My network is small less than 15 workstations. The second Wins server is
only for redunancy

the replication Partners properties has push/pull
use persistent connection for replication for pull
use persistent connection for replication for push

The same on both wins servers.

Since I am a very small network should I uncheck those options and set a
replication schedule? or leave well enough alone.

I know I get the error becasue the other server is down but it is not down
for very long period so wins should really not get upset so fast.

Any ideas or recommendations

Thanks

Tom


 
Reply With Quote
 
 
 
 
Lanwench [MVP - Exchange]
Guest
Posts: n/a

 
      03-22-2009, 01:44 PM
Thomas R Grassi Jr <(E-Mail Removed)> wrote:
> I have 2 Windows 2003 R2 Standard DC servers SP2 running WINS DNS and
> one DHCP server.
>
> The Wins is my question
>
> I get this error only when one server is down for maint or a restart.
>
> Type: Error
> Date: 3/20/2009
> Time: 7:14:26 PM
> Event: 4102
> Source: Wins
> Category: None
> User: N/A
> Computer: TGCS001
> Description:
> The connection was aborted by the remote WINS. Remote WINS may not be
> configured to replicate with the server.
>
> My network is small less than 15 workstations. The second Wins server
> is only for redunancy
>
> the replication Partners properties has push/pull
> use persistent connection for replication for pull
> use persistent connection for replication for push
>
> The same on both wins servers.
>
> Since I am a very small network should I uncheck those options and
> set a replication schedule? or leave well enough alone.
>
> I know I get the error becasue the other server is down but it is not
> down for very long period so wins should really not get upset so fast.
>
> Any ideas or recommendations
>
> Thanks
>
> Tom


I really don't think you need two WINS servers in a 15-workstation network.
Two DNS servers, sure. But WINS is used for network browsing only and
shouldn't have any affect on the functioning of your network (oh, unless you
have legacy apps that require it). I'd suggest removing the 2nd WINS server
& changing all workstations to point only to the remaining WINS server.
Just my $.02.


 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
pc name conflict and wins question Jason Huang Windows Networking 1 02-13-2008 12:26 PM
WINS Question PFG Windows Networking 0 01-31-2007 10:23 PM
WINS question Tom K Windows Networking 0 10-20-2005 02:05 PM
WINS question em Windows Networking 2 04-05-2005 02:41 AM
WINS question Sam Windows Networking 26 08-09-2004 02:53 AM



1 2 3 4 5 6 7 8 9 10 11