> Lo and behold, Michael Dillon once said:
> > > out warning, and on an inconsistant basis. We have noticed one other side
> > > effect is that the user logging in fails to get a "host.domain.blah login:"
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > > prompt; rather, they get a " login:" prompt. Any help from those who might
> > ^^^^^^^^^^^^^^^^^^
> > > have an inkeling on what might cause this would be appreciated.
> >
> > Sounds like a DNS failure. Is it possible that the reason nobody can get
> > into the box (even telnet?) is because of a name-server or routing foulup?
> > Have you patiently waited at least 3 minutes to see if you can actually
> > get in via telnet? Then you could examine things like the routing tables...
> When our PM does this, our DNS is still functioning perfectly. I can
> access all of our network facilities from another terminal server, just
> not the portmaster. It won't even respond to a ping, much less a
> telnet. It could be something with the routing, but I have a hard time
> seeing how the routing would affect things when I'm pinging it from a
> machine on the same local ethernet. Anyone else with similar horror
> stories want to come out of the woodwork on this one? :-)
I've mentioned it tons of times, but livingston hasn't been able to
recommend anything to fix it yet. So we live with the occasional lockups.
> -Dave Andersen
> ---
> angio@aros.net
> system administration
Brian Kramer - Owner/Systems Administrator - bjkramer@pluto.njcc.com
New Jersey Computer Connection - Public Access Unix Site - pluto.njcc.com
Voice: 609-896-2799 - Fax: 609-896-2994 - Dialups: 609-896-3191 & 896-2722
Web: http://www.njcc.com/ Telnet/Dialup: pluto.njcc.com login as guest.