Topic: Server won't release modem connection

[scottbrown]

I hate to bother everyone with what is probably a failure of my feeble little mind to comprehend something (probably) simple, but here goes:

I installed e-smith server and gateway on my home network (6 hosts, Windoze98) to replace NT-SBS (A side note on SBS... a great way to kill an otherwise perfectly good computer) The install went as advertised, simple, easy, no problems. Altogether a great release of Linux. Everything works, but I have one problem.

This machine is set to demand dial, which it does with remarkable efficiency. It is so efficient that it dials out immediately upon boot, and keeps the connection open interminably (yes, I set it to time out after 3 minutes of inactivity). The packets initiating dialout are not coming from the stupid Windoze machines. I set the email server to multidrop and never check mail, ddns is not configured, I even turned off the e-smith reporting (I'll trurn it back on whenever I get this resolved, the nice people at e-smith deserve to add me to their statistics at the very least... if I implement the server in my work environment (200 machines, ten servers, seven sites) I'll even buy a support package!) For the time being, I need to get this issue resolved.

Any ideas would be greatly appreciated.

(hardware: 333 AMD K6-2, 96mb ram, internal 56k modem on Com1 which has worked with everything I ever threw at it, including several Linux installs, 100baseTX pci adapter, etc.)

[Charlie Brady]

scottbrown wrote:

> The packets initiating dialout are not coming
> from the stupid Windoze machines.

I'm curious to know how you know that the WIndows machines are not initiating dialout, if you do not know what *is* initiating the dialout..

Look through /var/log/messages for lines containing "Trigger" - diald logs the reason for initiating each call via such a line. It will give you a clue as to what is causing the dialout.

You can find a program called diald-top in my contrib directory under ftp://ftp.e-smith.org/pub/e-smith/contrib. Install the RPM, then run diald-top on the console, and you can see all connections which are keeping the line up.

Regards

Charlie

[scottbrown]

Thanks Charlie, I was headed in that direction.  I'll install the RPM.  It's great to have people like you furthering this cause.

It's easy to know the Windoze crapola machines aren't the culprit when they are physically removed from the network...

For the record, I'm a MCSE newbie to Linux.  I've HAD IT with Microsoft, and were it not for the sweet love between AutoDesk and Microsoft, would have long since dumped all of their stuff.  I can't live without AutoCAD, woe is me.

Charlie Brady wrote:
>
> scottbrown wrote:
>
> > The packets initiating dialout are not coming
> > from the stupid Windoze machines.
>
> I'm curious to know how you know that the WIndows machines
> are not initiating dialout, if you do not know what *is*
> initiating the dialout..
>
> Look through /var/log/messages for lines containing "Trigger"
> - diald logs the reason for initiating each call via such a
> line. It will give you a clue as to what is causing the
> dialout.
>
> You can find a program called diald-top in my contrib
> directory under ftp://ftp.e-smith.org/pub/e-smith/contrib.
> Install the RPM, then run diald-top on the console, and you
> can see all connections which are keeping the line up.
>
> Regards
>
> Charlie