Paul,

Sorry, dumb thought.

Are any of the clients pointing to the old domain controller?  Dns?

-Craig

Sent from my iPad

On Aug 26, 2013, at 2:59 PM, Paul Scott <[log in to unmask]> wrote:

> Greetings,
> 
> I am not a unix admin, but I play one on TV... Basically I was nominated because I knew more than anyone else here. We have an old domain controller windows box, that we are trying to take off our network. Our new domain controller is up and working fine.
> 
> BUT, when we take the old domain controller off the network, our 9000 starts having trouble authenticating new sessions. Almost everyone can still get on using ssh, but not everyone. Also, telnet becomes very slow to originate a session. It can take 5 minutes to get a login prompt but once you do, everything works fine. Plug the old domain controller back in, and boom, you have a prompt.
> 
> And once you are on, the old domain controller can be taken off line and there is no effect on your existing session.
> 
> I cannot find anything that should be using ANY external service for authentication other than SAMBA, and it is pointed towards our new domain controller.
> 
> The gateway is NOT the old domain controller.
> 
> What could possibly be contributing to this? The authentication is NOT happening on either of the domain controllers, but something seems to be checking to see if the old one is online before a login prompt is offered. Once the prompt is offered, I can unplug the old domain controller and then login with my user and password no problem.
> 
> Thanks in advance for any insight you might have.
> 
> Paul Scott
> Problem Solved
> 
> 
> 
> 
> *******
> To unsubscribe, click the following link:
> http://raven.utc.edu/cgi-bin/WA.EXE?TICKET=NzM1MTM2IG1yX2xhbGxleUBZQUhPTy5DT00gTElTVE5BTUUgIPvaE1jY%2Fip9&c=SIGNOFF
> *******

*******
To unsubscribe, click the following link:
http://raven.utc.edu/scripts/WA.EXE?SUBED1=HP9000-L
*******