Using 2.4 kernal--something broke in init script? I was connected and
everything fine and went to next header in news group and connection pooped
out. Tried again, ditto. Tried with Mozilla, ditto. Tried pinging my ISP
fine, others, no go. So, I'm here to send a fax on this old distro 9.1 of
Mandrake, can't get the fax to work on Slack 10.2 'cause it looks for a
config file in /etc which isn't there. I try Connecting to Internet here and
it works, huh?

Help!

--

Bud wrote:

> Using 2.4 kernal--something broke in init script?

Seems unlikely, unless something was changed specifically on your
system. I have Slackware-10.2 systems, with 2.4.x kernel and some with
2.6.x kernel and none have any connectivity problems (not caused by my
own errors).

> I was connected and everything fine and went to next header in news
> group and connection pooped out. Tried again, ditto. Tried with
> Mozilla, ditto.

Something wrong with your ISP's netnews service, perhaps?

> Tried pinging my ISP fine, others, no go.

Your ISP's connection to the Internet is flaky? You have lost your
default route? You have a DNS configuration error? What changed just
before the failure occured?

> So, I'm here to send a fax on this old distro 9.1 of Mandrake, can't
> get the fax to work on Slack 10.2 'cause it looks for a config file in
> /etc which isn't there.

I fail to see the connection between sending a fax and losing your
Internet connection. Can you elaborate?

> I try Connecting to Internet here and it works, huh?

Here where? On the Mandrake system? That means that either a) if the
failure above was caused by ISP's problem, it has been fixed in the
intervening time that you switched from the Slackware system to the
Mandrake system; or b) there may have been a failure on your Slackware
system, caused by some change that was made, but without knowing what
that change was, no one here can help you sort it out. The generic
advice would be something on the order of "try changing it back".

There are c), d) and perhaps even e) possibilities, based on other
possible causes for the failure you saw, but without further
information, it's nearly impossible to speculate on any of them, and
even a) and b) above are nothing more than loose speculation based on
too little information to be able to provide anything even resembling a
diagnosis ...

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

Sylvain Robitaille wrote:
>
> Seems unlikely, unless something was changed specifically on your
> system. I have Slackware-10.2 systems, with 2.4.x kernel and some with
> 2.6.x kernel and none have any connectivity problems (not caused by my
> own errors).

That's what drove me nuts, I did nothing but boot up, connected via esternal
modem, working fine then stopped. Changed nothing from last boot to the
next.

> Something wrong with your ISP's netnews service, perhaps?

Aparently not, works with Mandrake, not Slack.

> Your ISP's connection to the Internet is flaky? You have lost your
> default route? You have a DNS configuration error? What changed just
> before the failure occured?

As I said, just quit.

>> So, I'm here to send a fax on this old distro 9.1 of Mandrake, can't
>> get the fax to work on Slack 10.2 'cause it looks for a config file in
>> /etc which isn't there.
>
> I fail to see the connection between sending a fax and losing your
> Internet connection. Can you elaborate?

Me either, should have left that out.

>> I try Connecting to Internet here and it works, huh?
>
> Here where? On the Mandrake system?

Yep, all is fine, so not my ISP.

>That means that either a) if the
> failure above was caused by ISP's problem, it has been fixed in the
> intervening time that you switched from the Slackware system to the
> Mandrake system; or b) there may have been a failure on your Slackware
> system, caused by some change that was made, but without knowing what
> that change was, no one here can help you sort it out. The generic
> advice would be something on the order of "try changing it back".
>
> There are c), d) and perhaps even e) possibilities, based on other
> possible causes for the failure you saw, but without further
> information, it's nearly impossible to speculate on any of them, and
> even a) and b) above are nothing more than loose speculation based on
> too little information to be able to provide anything even resembling a
> diagnosis ...
>

True, I went back and booted to Slack and no joy, so posting from the old
Mandrake system. I'll try one more time from Slack before I hit the hay.

Thanks for answering anyway.
--

On 08/02/06 23:57, Bud wrote:
> That's what drove me nuts, I did nothing but boot up, connected via esternal
> modem, working fine then stopped. Changed nothing from last boot to the
> next.

Not to be a smart (you know what). I (sarcastically) tell some of my
clients (those that I can get away with it with) "That is the definition of
'Broke', 'It was working, and now it is not.'" The problem becomes, for
us in the know, figuring out:

A) WHAT is broke
B) WHERE is it broke
C) WHEN did it brake
D) WHY / HOW did it brake
E) How do we prevent it from braking again.

> Aparently not, works with Mandrake, not Slack.

You do know that it is indeed broken based on the fact (below) that you
have re-tested it after knowing that the information you have is good.

> As I said, just quit.

I HATE it when that happens. But, that is what gives me a job.

>> I fail to see the connection between sending a fax and losing your
>> Internet connection. Can you elaborate?
>
> Me either, should have left that out.

Faxing? Who's talking about fa ... What are we talking about???

> Yep, all is fine, so not my ISP.

*nod* More evidence that we can not ignore and say that the problem does
not exist. Grumble grumble...

> True, I went back and booted to Slack and no joy, so posting from the old
> Mandrake system. I'll try one more time from Slack before I hit the hay.

More grumbling and some growling at this point. Where is MiniCom when I
need it. Does Slack successfully dial? Do the modems sync and lock? Do
you get an IP from your provider? Is the IP the same on Slack as it is on
Mandrake? Have you tried flushing your firewall to make sure that it is
not interfering? Are you running a firewall?

Just a few questions / things to look in to that will help narrow down and
locate the problem.



Grant. . . .

Taylor, Grant wrote:
>
> Not to be a smart (you know what). I (sarcastically) tell some of my
> clients (those that I can get away with it with) "That is the definition of
> 'Broke', 'It was working, and now it is not.'" The problem becomes, for
> us in the know, figuring out:
>
> A) WHAT is broke
> B) WHERE is it broke
> C) WHEN did it brake
> D) WHY / HOW did it brake
> E) How do we prevent it from braking again.
>
> You do know that it is indeed broken based on the fact (below) that you
> have re-tested it after knowing that the information you have is good.
>
>> As I said, just quit.
>
> I HATE it when that happens. But, that is what gives me a job.
>
>> Yep, all is fine, so not my ISP.
>
> *nod* More evidence that we can not ignore and say that the problem does
> not exist. Grumble grumble...
>
>> True, I went back and booted to Slack and no joy, so posting from the old
>> Mandrake system. I'll try one more time from Slack before I hit the hay.

And no joy, again!

> More grumbling and some growling at this point. Where is MiniCom when I
> need it. Does Slack successfully dial? Do the modems sync and lock? Do
> you get an IP from your provider? Is the IP the same on Slack as it is on
> Mandrake? Have you tried flushing your firewall to make sure that it is
> not interfering? Are you running a firewall?

Yes, modem works fine, connects fine, used both Kppp and ppp-go with stable
connections with an IP address. With Slack I can access the ISP website but
no others.

No firewall, no windoze for a year or so.

> Just a few questions / things to look in to that will help narrow down and
> locate the problem.
>
> Grant. . . .

Thanks Grant, was hoping to get time to do some exploring of the scrips
today. Makes me want to know a lot more than I do but . . . ignorance is not
always bliss.
--

Bud wrote:
> out. Tried again, ditto. Tried with Mozilla, ditto. Tried pinging my ISP
> fine, others, no go. So, I'm here to send a fax on this old distro 9.1 of

As a newbie: maybe it's a DNS problem?

in /etc/resolv.conf add this:
nameserver xxx.xxx.xxx.xxx < ip of your... nameserver ask you ISP or check it with mandrake (somehow..)

I think, if you have DHCP configured, then it's useless to edit the above file, but I don't believe it make any harm :-)

michales wrote:
>
> As a newbie: maybe it's a DNS problem?
>
> in /etc/resolv.conf add this:
> nameserver xxx.xxx.xxx.xxx < ip of your... nameserver ask you ISP or check it with mandrake (somehow..)
>
> I think, if you have DHCP configured, then it's useless to edit the above file, but I don't believe it make any harm :-)

Thanks Michales, I'm using dialup. Wish at times I'd skimp on some things
and pay for DSL but so far I'm willing to wait while pages load and do
something else in another window.

--

Bud wrote:
> michales wrote:
>> As a newbie: maybe it's a DNS problem?
>>
>> in /etc/resolv.conf add this:

and this:
search YourISPdomainname

>> nameserver xxx.xxx.xxx.xxx < ip of your... nameserver ask you ISP or check it with mandrake (somehow..)
>>
>> I think, if you have DHCP configured, then it's useless to edit the above file, but I don't believe it make any harm :-)
>
> Thanks Michales, I'm using dialup. Wish at times I'd skimp on some things
> and pay for DSL but so far I'm willing to wait while pages load and do
> something else in another window.
>

Ok, I have been difficulties with dial-up but it was my fault. I was without DHCP (prefer manually configuration) If memory serves right: my problem was the resolv.conf file I have mentioned above.

Modem connects to Internet, right?

michales wrote:
>
> Ok, I have been difficulties with dial-up but it was my fault. I was without DHCP (prefer manually configuration) If memory serves right: my problem was the resolv.conf file I have mentioned above.
>
> Modem connects to Internet, right?

Oh yes, I can go to my ISP's web site but no where else on the WWW.

--

Bud wrote:

> michales wrote:
>>
>> Ok, I have been difficulties with dial-up but it was my fault. I was
>> without DHCP (prefer manually configuration) If memory serves right: my
>> problem was the resolv.conf file I have mentioned above.
>>
>> Modem connects to Internet, right?
>
> Oh yes, I can go to my ISP's web site but no where else on the WWW.
>
> --

Are the slack system and the mandrake system actually different machines?
Are you getting the same ip address, broadcast address and gateway on Slack
and Mandrake? Do you get the same addresses every time you connect with
Slackware? On Slackware, this information is in /etc/dhcpc/*.info.
Mandrake same place?

--
Old Man