Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

unable to attach to volumes after dsrepair

Status
Not open for further replies.

Wodill

MIS
Joined
Feb 6, 2003
Messages
40
Location
US
I have multiple NetWare 5.1 sp4 and sp5 servers. I have not had the chance to install the latest service packs but I did want to run NDS health checks on the servers over the weekend. I ran dsrepair (unattended) until there were no errors. I thought everything was okay as after I ran it, I was able to connect to all servers. Some time over the weekend; however, no users were able to attach the volumes on the servers. I didn't have any problems with a couple of 6.0 servers and there were two 5.1 servers that I did reboot. All of the others were unable to attach to until I rebooted them also.

What with dsrepair would cause the volumes to be unavailable? There were no errors on any of the servers in question.
 
What errors were you getting? Maybe DSREPAIR was keeping the DS database open on these server(s) and was not allowing users to connect to the server(s), hence the issue?

What version of DS are you running?

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
are the ds version's mixed?

is everything still in sync - ie dsrepair - check sync and also time. i'm not a fan of the unattended repair unless you have issues - dstrace is more informative.

if you go to the volume in console1 - do you get any errors?

it just be a case of updating volumes into ds again
 
I didn't receive any errors on the server console. When users tried to log back into the network, they receive 8804 errors mapping drives to the servers in question.

Yes we are running mixed DS versions as we have two servers at 6.0 sp3 (v10350.19), two servers at 5.1 sp5 (v8.82), six servers at 5.1 sp4 (v8.79)

Everything was in sync when running dsrepair.

DSrepair didn't show that the database was still locked.


 
Bet you any money you can connect if you use the IP Address instead of the server name. Are you running SLP?

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top