We had this happen once since we upgraded to 3.1.4 as well. I wasn't
here when it happened, but it sounds kind of like our host got some
incorrect routing information. Could it be that the PortMaster send out
a bogus RIP update? Are you guys that have had this happen running RIP?
Perhaps the thing to do, if it happens again, is to do a traceroute to
the PortMaster from the host that can't talk to it, or check the routing
table on that host.
Chuck Scott, Pres.
Freeway, Inc.
cscott@freeway.net
On Wed, 1 Nov 1995, Joerg SPROCKETS Grau wrote:
> Hi guys,
> Thanx for the prompt replies. Here is the problem with more detail:
>
> I am running radius of my solaris box. I was running 3.1.3. Everything
> was fine. Then suddenly I noticed that nobody was looged on, I checked
> the termlog and sure enough every user got an "invalid login" message.
> Now one user, okay, but EVERY user. I tried to log into the portmaster
> by telneting from my solaris box and got a timed out message. I pinged
> and got a "no response" message. First thing: REBOOT (on/off) -> NOTHING.
> I then used my router terminal to ping
> the IP address, and sure enough it was "alive". I telnet'ed successfully
> into the portmaster from my router terminal. I checked all the settings
> and nothing seemed to be out of the ordinary. I telneted into my unix
> box from the portmaster and had no problems. I could not ping, even
> throgh the telnet session I had established from my portmaster.
>
> The probelms my customers had, I deducted, were that the PM send an
> authentication request to the RADIUS server, which resides on my solaris
> box. The RADIUS server authenticated the users, and then tried to send
> the result back to the portmaster, which for some reason refused the
> answer, and thus didn't let the user log on.
>
> I called the livingston tech support, which upgraded me to 3.1.4 and put
> me in the "urgent queue". Last time I called them I got into some queue
> and they called me back about THREE weeks later.
>
> Anyways, here is how I solved the problem.
>
> I stoped RADIUS.
> I started it again.
> It still didn't work.
> I then took all the IP addresses my machine listens to down (I am hosting
> a bunch of other domains (for www purposes), which is done by making your
> machine listen to different ip numbers...)
> I then tried it and YES, it worked!!
> I then, one by one, up'ed the ip numbers again, checking after each one
> if the ping/telnet'ing still worked, and sure enough, after each it did,
> and it stil does.
>
>
> I don't know what happened and why, but I didn't LIKE it. If anybody has
> any idea why this could have happened, I would REALLY appreciate an
> e-mail about it. As a commercial enterprise my company cannot afford to
> have to be concerned about the functionality of the terminal server.
> This is supposed to be one of the market leaders. This kind of
> un-logical behavior should NOT happen.
>
>
> ---
> Joerg 'SPROCKETS' Grau | grau@negia.net | http://www.negia.net/~grau
>
> "We watched our friends grow up together, and we saw them as they fell.
> Some of them fell into heaven, some of them fell into hell."
>
> the pogues
>
>
>
>
>
>