Display servers in DSREPAIR

[tpol...@artesianwater.com]

We have three(3) NW 5.1 SP8 servers, one of which is specified
as "primary" and the other two are "scondary". We are receiving "unable
to communicate errors" on the main console and (-625 reported in dsrpair)
on the two secondary servers and they are both showing each other
as "down" when you "display servers" via dsrepair. The "primary" server
shows them both "up". Time appears to be synchronized on all three(3)
servers. any help would br greatly appreciated. TED

[Anders Gustafsson]

,

> as "primary" and the other two are "scondary".
>

Which is wrong by default With three servers, one should be SINGLE and
the rest SECONDARY.

- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Using VA 5.51 build 315 on Windows 2000 build 2195

[Andrew C Taubman]

625 means that comms is not working between the servers. I can't see how
it is possible that time sync is working therefore.

Load DSrepair on the server holding the Master of the affected
partition. From the first menu run a TimeSync Check and a Report Sync
Status. When finished, exit DSrepair and post the relevant portion of
SYS:SYSTEM/dsrepair.log here, thanks.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.

[Massimo Rosen]

Hi,

tpol...@artesianwater.com wrote:
>
> We have three(3) NW 5.1 SP8 servers, one of which is specified
> as "primary" and the other two are "scondary". We are receiving "unable
> to communicate errors" on the main console and (-625 reported in dsrpair)
> on the two secondary servers and they are both showing each other
> as "down" when you "display servers" via dsrepair.

First, these appear to be two completely unrelated things. I guess with
"primary and secondary" you're referring to your timesync setup. As
Anders said, this is an illegal configuration, and your time will now
*not* be in sync thoughout your whole network, as your primary is
already out of sync. YOu should urgently switch the primary to be a
single to solve that.

*However*, this issue is probably completely unrelated to your DS comms
issue, which a -625 is. Timesync and DS sync use completely different
communication methods. The -625 basically means that the servers issuing
these simply cannot reach the other server(s) succesfully.

This may actually have lots of reasons, starting with real, native comms
problems (bad network, firewall), but could also point to
misconfiguration in either protocols (IP/IPX), or name resolution
methods (servers resolving with wrong addresses for some reason).
The only way how your illegal timesync setup and your DS comms issue
*could* be related at all is if your server IP addresses have changed at
some point in the recent past, and this change did not sync throughout
NDS due to the time on your net not beeing in sync, resulting in the
servers not getting the change trying to contact the other server
through a no longer valid address.

To actually solve your problem, we need *way* more information,
especially the setup of your network both physically and logically.

CU,
--
Massimo Rosen
Novell Support Connection Sysop
No emails please!
http://www.cfc-it.de

[Massimo Rosen]

Andrew,

Andrew C Taubman wrote:
>
> 625 means that comms is not working between the servers. I can't see how
> it is possible that time sync is working therefore.

Very easy. Configured sources with hardcoded IP addresses used for
timesync (works), and bad address info for servers in their eDir records
or through DNS/SLP (breaks eDir sync).

[tpol...@artesianwater.com]

I am sorry, I was using the wrong terminology. Our main server is
configured as "single" and the other two are secondary. The problem
seemed to happen after we installed SP8???

[Anders Gustafsson]

,

> I am sorry, I was using the wrong terminology. Our main server is
> configured as "single" and the other two are secondary. The problem
> seemed to happen after we installed SP8???
>

OK. So can all servers contact each other? You need to get timesync to
work before doing anything else.

[tpol...@artesianwater.com]

It is very wierd. The "single server" reports the other two(2) secondary
servers as "up", and the other servers show the "single" server up, but
don't show each other up in dsrepair, display servers???> ,

[tpol...@artesianwater.com]

Ok, here's the deal. We had to replace two(2) netwotk cables, apparently
the cables that were assigned to the NIC card for IPX were bad. After
replacing the cables, all is well!! Thanks,for your help..TED> ,

[Massimo Rosen]

Hi,

tpol...@artesianwater.com wrote:
>
> Ok, here's the deal. We had to replace two(2) netwotk cables, apparently
> the cables that were assigned to the NIC card for IPX were bad. After
> replacing the cables, all is well!! Thanks,for your help..TED> ,

Aka "native comms issue". Thanks for reporting back.