I dunno whose problem this is, it may be a weird interaction of several
different packages.
On the home network here is a Linux server running RH 5.2 (2.0.36) with
ip-masquerading and diald 0.99. There is also another RH 5.2 box which
is a samba server. In addition there are two Windoze ('95) boxen, one
of which regularly is used to access AOL via its own local modem using
AOL 4.0.
Sometimes (not infrequently) if you're not careful how you operate
the AOL client, it appears to spit out a packet destined for some
unnamed server at AOL (based on searches with nslookup and similar
tools) into the in-house network instead of sending it out over its
own dialup connection. This, of course, causes diald to pick up the
phone thereby disconnecting the direct dialup connection AOL has
established on its local modem.
This commonly happens because of a prompt for password that appears to
come from the SMB subsystem every time one fires up AOL. If you click
the CANCEL button on this dialog you get these stray packets that
cause diald to try to bring up the modem.
One way to "fix" it is to reconfigure the AOL client so it uses a
TCP/IP connection to AOL (thereby forcing it to use diald to bring
up the link for its main connection). But the person who uses the AOL
client for some reason I fail to understand insists on using the local
modem instead.
ideas??
Thanks!
Fred
--
-------------------------------------------------------------------------------
.---- Fred Smith /
( /__ ,__. __ __ / __ : /
/ / / /__) / / /__) .+' Home: [EMAIL PROTECTED]
/ / (__ (___ (__(_ (___ / :__ 781-438-5471
-------------------------------- Jude 1:24,25 ---------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
