The below email is in reference to some weird problems that a client of
ours has been experiencing while using a Livingston PortMaster Office
Router-2, running ComOS 3.7.1AP.5. Has anyone heard of a similar problem,
or does anyone have an idea as to what may have caused this? Thanks.
--- __o William R. Lorenz <wrl@nacs.net>
--- _-\<,_ New Age Consulting Service, Inc. [http://www.nacs.net]
--- (_)/ (_) Proud of Cleveland - [http://www.cleveland.com]
---------- Forwarded message ----------
I thought I'd give you the latest information on the router problem we've
repeatedly discussed, so that you can be as amused and perhaps baffled as
I am. The short version: the problem has gone away. The longer version
follows.
As you recall, the problem only occurred when I myself was using an
Internet connection. I work from the only NT workstation on our LAN.
Furthermore, the problem only occurred while I was remotely controlling an
NT server across the Internet (whether remote control was done by
pcANYWHERE or vnc). One detail I hadn't mentioned to you, Greg, but that
came out in conversation with Bill, was that on our LAN there is also an
NT server that has direct access to the ORU. It's the only machine other
than the primary Linux server that permanently has an interface of its own
on the Internet.
Until about three weeks ago, all three of the above-mentioned NT machines
were patched to Service Pack 4. At that time, I applied SP5 to all three
of them. Coincidentally, there has not been a router problem since, even
though I've had occasion to do extensive remote control work in long
sessions. I've definitely created many times over the circumstances under
which the PPP connection used to hang.
Now, on the one hand, this doesn't seem to make a lot of sense. That's
why I've waited so long to report the finding, figuring that sooner or
later the damned thing would lock up and demonstrate that the NT service
packs had nothing to do with it. but that hasn't happened. So my current
theory is that NT not only sucks in all the ways that I could have
enumerated in the past, but that I now know it to suck in a new and
fascinating way. Do either of you have any idea what an NT box might have
been doing to cause the router to go brain dead? What is puzzling to me
is that the ORU wasn't configured to listen for any broadcast routing
information, so I don't think anything the NT system(s) thought about
routing should have affected it. Incidentally, the NT server is not the
default route for anything on the LAN. One more detail that might be
significant what percentage of the time when the problem occurred one of
our staff had a PPTP connection to the NT server from the outside, but I
do now that that was the case a fair number of times. Once again, though,
we're still using the NT box for PPTP connections and I'm still doing the
same kind of work across the net that I was doing before.
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>