I have three servers local, one of which is being retired. The other two are a Bordermanager (with NDS signon authentication to get though the proxy) and a new server that has the main replica on it. When I shut down the old server, it takes almost 2 Minutes for Bordermanager to accept the user credentials! If I bring the old server back up, The same action takes 1 second. Any ideas what could be the cause? I would take the old server out of the tree but I don't want the bordermanager to stop functioning because of that.
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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NDS Authentication slow after turning off retired server
- Thread starter d1onysus
- Start date
salserocito
MIS
The server that will be retired, is it setup to be the Default Server for the Users, both at the Client Level (Preferred Server) as well as the User Object (Details/Environment/Default Server)?
Also, does the retiring server hold any copies of any replicas?
Please advise.
Also, does the retiring server hold any copies of any replicas?
Please advise.
- Thread starter
- #3
On some users machines it may still be the default server, and it does take a little while for those users to login to the network, but I'm NOT using Single Signon, so it shouldn't apply to the bordermanager HTML browser login. The User Objects either are switched over to the new server or there isn't a prefered server listed.
The soon to be retired server did have a read/write copy of the Replica but I demoted it to read only.
The only idea I had is could the Bordermanager server be a replication partner to the retired server? and if so could that effect authentication? and how do I view and/or change this setting?
The soon to be retired server did have a read/write copy of the Replica but I demoted it to read only.
The only idea I had is could the Bordermanager server be a replication partner to the retired server? and if so could that effect authentication? and how do I view and/or change this setting?
You shouldn't just switch a server off - you will need to remove all replicas off it first and then remove it from the tree. It might be that your NDS itself is running slow due to the fact it cannot commumicate and replicate with your switched off server.
Demoting your replica to read only has no effect as your Master server will still want to replicate with it. If it is switched off, your Master cannot communicate with it thus causing your issue.
I would ensure that your other two servers also have replicas on also. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
Demoting your replica to read only has no effect as your Master server will still want to replicate with it. If it is switched off, your Master cannot communicate with it thus causing your issue.
I would ensure that your other two servers also have replicas on also. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
salserocito
MIS
Yep... just as I was gonna say! Hmmm... Deja Vu.
Good Luck!
Good Luck!
- Thread starter
- #6
salserocito
MIS
Yes, removing it gracefully from the NDS Tree by removing DS from the server is the way to go!
Good Luck!
Good Luck!
jacknahman
MIS
I am having the same problem w/ bordermanager html browser logons. I have one bordermanager server and 3 netware5 servers with replicas on them. I gracefully removed one server that had a r/w replica on it and network logons are OK but bordermanager html browser logons can take up to 2 minutes or more. Did you come up with any other resolutions to this issue?
salserocito
MIS
First off, does the BorderManager Server have any Replicas on it?
You should also make sure that the server that removed has been completely flushed in NDS. Go into the Replica Ring on each server and verify that the removed Server no longer exists in the Replica Ring.
Good Luck!
You should also make sure that the server that removed has been completely flushed in NDS. Go into the Replica Ring on each server and verify that the removed Server no longer exists in the Replica Ring.
Good Luck!
jacknahman
MIS
The bordermanager server does have a replica on it.
And I checked the replica ring for each server and the retired server does not show. I removed the server from NDS last Friday so the changes would synchronize over the weekend. I was hoping the html logon delay would disappear once NDS synchronized.
And I checked the replica ring for each server and the retired server does not show. I removed the server from NDS last Friday so the changes would synchronize over the weekend. I was hoping the html logon delay would disappear once NDS synchronized.
salserocito
MIS
I have a question about the HTML Login... What is it used to login to? GroupWise WebAccess? Remote NetWare capability?
Please advise.
Good Luck!
Please advise.
Good Luck!
- Thread starter
- #12
I did not find a solution yet, but it's nice to see that I'm not insane and that someone else in the world has this problem.
Jackstrw- are you using BM 3.5? what SP are you on?
Salserocito- The HTML log in is simply a authentication using their Novell login to access the internet. We limit some users because instead of working they are web surfing. You are able to use a default context, so I made a NET OU, put alias 's in the OU, and if your in that OU then you can sign in. If not, No internet for you!
To workaround the problem, Jackstrw, I just disabled the Authentication. But there has to be a solution. We can try implementing single sign on but then we would have to change every workstation.
Jackstrw- are you using BM 3.5? what SP are you on?
Salserocito- The HTML log in is simply a authentication using their Novell login to access the internet. We limit some users because instead of working they are web surfing. You are able to use a default context, so I made a NET OU, put alias 's in the OU, and if your in that OU then you can sign in. If not, No internet for you!
To workaround the problem, Jackstrw, I just disabled the Authentication. But there has to be a solution. We can try implementing single sign on but then we would have to change every workstation.
- Thread starter
- #14
Nope no RADIUS....On the LAN a user opens there browser, goes to and the user gets redirected to BM logon screen, once they put in their user name and password, bam! They're in.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
- Locked
- Question